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