From owner-freebsd-hackers Thu Sep 19 22:29:29 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA24392 for hackers-outgoing; Thu, 19 Sep 1996 22:29:29 -0700 (PDT) Received: from nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA24363 for ; Thu, 19 Sep 1996 22:29:24 -0700 (PDT) Received: from localhost (localhost.efn.org [127.0.0.1]) by nike.efn.org (8.7.5/8.7.3) with SMTP id WAA28163; Thu, 19 Sep 1996 22:29:46 -0700 (PDT) Date: Thu, 19 Sep 1996 22:29:45 -0700 (PDT) From: John-Mark Gurney Reply-To: John-Mark Gurney To: Scanner cc: freebsd-hackers@freebsd.org Subject: Re: TCP extensions breaking TCP. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 19 Sep 1996, Scanner wrote: > On Thu, 19 Sep 1996, Joe McGuckin wrote: > > > > > I've seen the enabled TCP extensions hang with SCO. > > More than likely its because the vendor's are not implementing the > extensions right and/or not sticking to the RFC's. Theres a way to prove > this from a FreeBSD box running 2.1+ . I beliece 2.1 is when T/TCP went > in. It can be shown at least in one OS's implementation that it is not > implemented right. The easy way to tell is to finger the machine thats > having problems most of the time if the extensions are not implemented > right or are broke, the finger will freak out and close before any info is > gained. wow... thanks for pointing out about the finger problem... I couldn't figure out why I couldn't finger any of my favorite hosts (i.e. resnet.uoregon.edu 2.1.5-RELEASE, garcia.efn.org SunOS 4.1.3, and dogbert.efn.org 2.1.0-RELEASE)... as soon as I disabled extensions I suddenly am able to finger them... plus I know for a fact that the extensions are turned on for resnet.uoregon.edu... anything I can do to fix the problem besides turning 'em off... I'm on a 2.2-0323-SNAP (soon to be 0801)... and behind slirp which could be my problem but before 0323 snap when I had 2.1.0 or 2.0.5 it worked fine... thanks for the info.. ttyl.. John-Mark gurney_j@efn.org http://resnet.uoregon.edu/~gurney_j/ Modem/FAX: (541) 683-6954 (FreeBSD Box) Live in Peace, destroy Micro$oft, support free software, run FreeBSD (unix)