From owner-freebsd-questions  Tue Jan 28 09:35:10 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA25943
          for questions-outgoing; Tue, 28 Jan 1997 09:35:10 -0800 (PST)
Received: from misery.sdf.com (misery.sdf.com [204.244.210.193])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA25934;
          Tue, 28 Jan 1997 09:35:05 -0800 (PST)
Received: from misery.sdf.com [204.244.213.33] 
	by misery.sdf.com with smtp (Exim 1.59 #1)
	id 0vp9h3-0000Ds-00; Tue, 28 Jan 1997 01:19:05 -0800
Date: Tue, 28 Jan 1997 01:19:05 -0800 (PST)
From: Tom Samplonius <tom@sdf.com>
To: Steve <shovey@buffnet.net>
cc: Robert Chalmers <robert@nanguo.chalmers.com.au>,
        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.BSI.3.95.970128090149.28924O-100000@buffnet11.buffnet.net>
Message-ID: <Pine.NEB.3.94.970128011415.240A-100000@misery.sdf.com>
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, Steve wrote:

> > The only constant is the Annex. However, why does it pass _most_ traffic,
> > if it is the fault of the Annex, and only fail on some.? 
> > 
> > If FreeBSD is
> > going to be so fussy about its tcp/ip flow, shouldn't it be reworked.
> > The world is still full of less than leading edge hardware! Some of it
> > brand new...
> 
> I had similar problems using annexes as term servers with user - and have
> posted numerous times that this problem only exists with freebsd  - sco,
> linux, etc doesnt have trouble - only every time I post it I get bashed
> about the head and lectured on freebsd having perfect tcp/ip and
> everything else in the world having faulty tcp/ip.
> 
> So good luck to you sir!

  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.

Tom