From owner-freebsd-current Sat Sep 5 22:54:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA01879 for freebsd-current-outgoing; Sat, 5 Sep 1998 22:54:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA01874 for ; Sat, 5 Sep 1998 22:54:37 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id WAA10205; Sat, 5 Sep 1998 22:51:26 -0700 (PDT) Message-Id: <199809060551.WAA10205@implode.root.com> To: Tom cc: freebsd-current@FreeBSD.ORG Subject: Re: Should FreeBSD-3.0 ship with RFC 1644 (T/TCP) turned off by In-reply-to: Your message of "Sat, 05 Sep 1998 10:28:28 PDT." From: David Greenman Reply-To: dg@root.com Date: Sat, 05 Sep 1998 22:51:26 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >On Sat, 5 Sep 1998, Terry Lambert wrote: > >> The problem is not the options, per se, but the fact that some >> systems failed to mplement correct option negotiation, per >> RFC 793, for previously non-existant options. >> >> Livingston Portmasters were one known offender. >... >> Thus you would actualy puke bad equipment into non-operability. >... > > 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. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message