Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 18 Jan 1999 15:25:59 -0800
From:      David Greenman <dg@root.com>
To:        Erik Moe <ehm@concentric.net>
Cc:        freebsd-net@FreeBSD.ORG
Subject:   Re: FreeBSD and RFC 1644 
Message-ID:  <199901182326.PAA29997@implode.root.com>
In-Reply-To: Your message of "Mon, 18 Jan 1999 15:30:12 CST." <36A3A7E4.8CE869A@concentric.net> 

next in thread | previous in thread | raw e-mail | index | archive | help
>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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901182326.PAA29997>