From owner-freebsd-net Mon Jan 18 22:21:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22733 for freebsd-net-outgoing; Mon, 18 Jan 1999 22:21:52 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22725 for ; Mon, 18 Jan 1999 22:21:50 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id BAA17774; Tue, 19 Jan 1999 01:21:01 -0500 (EST) Date: Tue, 19 Jan 1999 01:21:01 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: David Greenman cc: Erik Moe , freebsd-net@FreeBSD.ORG Subject: Re: FreeBSD and RFC 1644 In-Reply-To: <199901182326.PAA29997@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org FWIW, concentric is in a colo with us here, and guess what the dial equipment is? Bay 5399's. This is loosely based on that cranky old Annex code (Bay bought Xylogics, fine purveyors of crappy stacks some years ago) that used to make my life hell. Anyhow, you'd think they'd fixed it by now wouldn't you. As far as I can tell concentric is an all Bay shop. Look out ;) Charles --- Charles Sprickman spork@super-g.com --- "...there's no idea that's so good you can't ruin it with a few well-placed idiots." On Mon, 18 Jan 1999, David Greenman wrote: > >My main interest in this problem at this point is simply curiosity. I > >have glanced through rfc 1644 looking for answers, but if they are > >there, they simply don't smack me in the face. I can accept the fact > >that my service provider may have their network configured in such a way > >that it breaks the combination of FreeBSD and rfc 1644, but can someone > >out there tell me why this combination might break? > > Some terminal servers are known to not grok TCP options correctly - those > from Annex come to mind, but I recall that there were others. Anyway, if all > the packets with TCP options get dropped or mangled, then it should be pretty > obvious why it doesn't work. :-) > > -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message