Date: Tue, 8 Sep 1998 16:44:18 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: tom@uniserve.com (Tom) Cc: tlambert@primenet.com, dg@root.com, freebsd-current@FreeBSD.ORG Subject: Re: Should FreeBSD-3.0 ship with RFC 1644 (T/TCP) turned off by Message-ID: <199809081644.JAA27443@usr07.primenet.com> In-Reply-To: <Pine.BSF.3.96.980906113956.14431A-100000@shell.uniserve.ca> from "Tom" at Sep 6, 98 11:41:23 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > Ugh... really? I use Livingston Portmaster's and FreeBSD heavily. > > > > > > > > Be aware that (depending on the model) Portmasters have had a long > > > >history, and some sites are still running 4 year old firmware on them. > > > >Always get the ComOS version. > > > > > > Terry's assertion about the Livingston being broken is the first I've > > > seen. Previously all of the reports of brokeness were with Annex terminal > > > servers. > > > > You should subscribe to the portmaste-users list. > > I'm on it. > > > Basically, if you are running old code, you are at risk. > > What is old code? Code with the bug. 8-). > You stated before that all Portmasters were affected. Not *all* Portmasters, *old* Portmasters. > I've never heard that _any_ version of ComOS has problems with TCP > extensions is affected actually. 1) Load an old version of the firmware. 2) Enable TCP extensions in FreeBSD. 3) Attempt to contact hosts connected through the Portmaster. I believe Annex (D?) terminal servers also had problems. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809081644.JAA27443>