From owner-freebsd-current Tue Sep 8 09:44:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01231 for freebsd-current-outgoing; Tue, 8 Sep 1998 09:44:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01225 for ; Tue, 8 Sep 1998 09:44:41 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id JAA20958; Tue, 8 Sep 1998 09:44:33 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp04.primenet.com, id smtpd020897; Tue Sep 8 09:44:22 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id JAA27443; Tue, 8 Sep 1998 09:44:18 -0700 (MST) From: Terry Lambert Message-Id: <199809081644.JAA27443@usr07.primenet.com> Subject: Re: Should FreeBSD-3.0 ship with RFC 1644 (T/TCP) turned off by To: tom@uniserve.com (Tom) Date: Tue, 8 Sep 1998 16:44:18 +0000 (GMT) Cc: tlambert@primenet.com, dg@root.com, freebsd-current@FreeBSD.ORG In-Reply-To: from "Tom" at Sep 6, 98 11:41:23 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > 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