From owner-freebsd-current Tue Sep 8 10:37:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11081 for freebsd-current-outgoing; Tue, 8 Sep 1998 10:37:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA11076 for ; Tue, 8 Sep 1998 10:37:10 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zGRhC-0000FB-00; Tue, 8 Sep 1998 10:36:51 -0700 Date: Tue, 8 Sep 1998 10:36:49 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Terry Lambert cc: dg@root.com, freebsd-current@FreeBSD.ORG Subject: Re: Should FreeBSD-3.0 ship with RFC 1644 (T/TCP) turned off by In-Reply-To: <199809081644.JAA27443@usr07.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 8 Sep 1998, Terry Lambert wrote: > > 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. This just doesn't happen. If you are seeing some problems, they aren't with the Portmaster, but some other network devices, or with your network configuration. > Terry Lambert > terry@lambert.org > --- Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message