From owner-freebsd-questions  Tue Jan 28 14:45:15 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA16018
          for questions-outgoing; Tue, 28 Jan 1997 14:45:15 -0800 (PST)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA16008;
          Tue, 28 Jan 1997 14:45:07 -0800 (PST)
Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id JAA10980; Wed, 29 Jan 1997 09:50:41 +1100 (EST)
Date: Wed, 29 Jan 1997 09:50:40 +1100 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: Tom Samplonius <tom@sdf.com>
cc: bsd <freebsd-questions@freebsd.org>, FreeBSD ISP <freebsd-isp@freebsd.org>,
        hackers@freebsd.org
Subject: Re: progress report on connection problems
In-Reply-To: <Pine.NEB.3.94.970128011415.240A-100000@misery.sdf.com>
Message-ID: <Pine.BSF.3.91.970129094909.13981x-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



On Tue, 28 Jan 1997, Tom Samplonius wrote:

> 
>   FreeBSD implements T/TCP.  You can disable this via by turning
> tcp_extensions off.  SCO, Linux do not implement T/TCP, which is to their
> disadvantage.  T/TCP gives you big wins if opening and closing a lot of
> TCP connections.
> 
>   Broken boxes like the Annex don't like T/TCP (it is broken, because if
> the Annex properly implemented IP/TCP, it wouldn't have a problem).  Newer
> software releases for the Annex fix this problem.
> 
>   I'm not aware of any equipment that doesn't like T/TCP that couldn't be
> fixed with a software upgrade.

We are not using T/TCP.  That is RFC 1644.  T/TCP may well be broken in 
Annexes, but it is RFC 1323 extensions which cause the current grief.

regards,

Danny