From owner-freebsd-current Mon Jan 15 14:02:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA12825 for current-outgoing; Mon, 15 Jan 1996 14:02:34 -0800 (PST) Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA12819 for ; Mon, 15 Jan 1996 14:02:30 -0800 (PST) Received: (from vince@localhost) by apollo.COSC.GOV (8.7.3/8.6.9) id OAA11226; Mon, 15 Jan 1996 14:02:28 -0800 (PST) Date: Mon, 15 Jan 1996 14:02:27 -0800 (PST) From: -Vince- To: Andras Olah cc: "Garrett A. Wollman" , current@FreeBSD.ORG Subject: Re: finger problem going from 2.1R to -current In-Reply-To: <3126.821743163@curie.cs.utwente.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG Precedence: bulk On Mon, 15 Jan 1996, Andras Olah wrote: > On Mon, 15 Jan 1996 13:07:41 PST, -Vince- wrote: > > On Mon, 15 Jan 1996, Garrett A. Wollman wrote: > > > What does having a Cisco router have to do with the question? Unless > > > you're suggesting that Ciscos have the same bug is Xyplex terminal > > > servers do... > > > > Cisco has RFC1323 and RFC1644 broken according to Justin... > > I don't think so because my SLIP line goes through a cisco terminal > server and it has no problems with either TCP extensions. The only > thing I noticed so far that the cisco doesn't compress the TCP packets > which have TCP options even if they don't change (i.e. T/TCP on but > RFC1323 extensions off). Hmmm, I thought if RFC1323 didn't work, RFC1644 doesn't either. Cheers, -Vince- vince@COSC.GOV - GUS Mailing Lists Admin - http://www.COSC.GOV/~vince UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan/Priscilla Chan Fan Club Mailing Lists Admin