From owner-freebsd-net@FreeBSD.ORG  Tue Feb 28 04:27:56 2006
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
X-Original-To: net@freebsd.org
Delivered-To: freebsd-net@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9EBA416A420
	for <net@freebsd.org>; Tue, 28 Feb 2006 04:27:56 +0000 (GMT)
	(envelope-from silby@silby.com)
Received: from relay03.pair.com (relay03.pair.com [209.68.5.17])
	by mx1.FreeBSD.org (Postfix) with SMTP id 48CF243D6D
	for <net@freebsd.org>; Tue, 28 Feb 2006 04:27:56 +0000 (GMT)
	(envelope-from silby@silby.com)
Received: (qmail 23515 invoked from network); 28 Feb 2006 04:27:55 -0000
Received: from unknown (HELO localhost) (unknown)
	by unknown with SMTP; 28 Feb 2006 04:27:55 -0000
X-pair-Authenticated: 209.68.2.70
Date: Mon, 27 Feb 2006 22:27:52 -0600 (CST)
From: Mike Silbersack <silby@silby.com>
To: Julian Stacey <jhs@berklix.org>
In-Reply-To: <200602272030.k1RKU5HL083862@fire.jhs.private>
Message-ID: <20060227222544.F11734@odysseus.silby.com>
References: <200602272030.k1RKU5HL083862@fire.jhs.private>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Bernd Kopriva <bernd@kopriva.de>, net@freebsd.org
Subject: Re: TCP_COMPAT_42 support
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2006 04:27:56 -0000


On Mon, 27 Feb 2006, Julian Stacey wrote:

> Anyone know if modern FreeBSD still supports TCP_COMPAT_42 ?

TCP_COMPAT_42 just tweaked how we generated TCP initial sequence numbers. 
The lack of it should not be impacting your ability to connect to machines 
of any vintage.

Mike "Silby" Silbersack