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 Message-ID: <Pine.NEB.3.94.970128011415.240A-100000@misery.sdf.com> In-Reply-To: <Pine.BSI.3.95.970128090149.28924O-100000@buffnet11.buffnet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.94.970128011415.240A-100000>