Date: Mon, 3 Apr 95 16:26:01 MDT From: terry@cs.weber.edu (Terry Lambert) To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Cc: jkh@freefall.cdrom.com, gibbs@estienne.cs.berkeley.edu, freebsd-bugs@freefall.cdrom.com Subject: Re: misc/292: rfc1323 and rfc1644 support can confuse terminal servers w/SLIP Message-ID: <9504032226.AA09297@cs.weber.edu> In-Reply-To: <9504032019.AA22793@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Apr 3, 95 04:19:17 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> I think it's not unreasonable to do: > > # > # Some broken implementations can't handle the RFC 1323 and RFC 1644 > # TCP options. If TCP connections randomly hang, try enabling this, > # and bug the vendor of the losing equipment. > # > if [ "x$disable_tcp_extensions" == "xYES" ]; then > sysctl -nw net.inet.tcp.rfc1323=0 > sysctl -nw net.inet.tcp.rfc1644=0 > fi Maybe go even further? Something like changing: > if [ "x$disable_tcp_extensions" == "xYES" ]; then to: > if [ "x$enable_tcp_extensions" != "xYES" ]; then In other words, default it off? I don't know which is more likely to result in "typically works without user intervention", though... Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9504032226.AA09297>