Date: Thu, 11 May 1995 12:09:46 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> 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: <199505111909.MAA10840@gndrsh.aac.dev.com> 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
> > <<On Sat, 01 Apr 1995 16:01:35 -0800, "Jordan K. Hubbard" <jkh@freefall.cdrom.com> said: > > > Maybe these need to be switched on and off inside netstart using > > sysconfig variables? Suggestions? > > 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 I have now implemented something similiar to this, those who had problems here please test out the new /etc/netstart and /etc/sysconfig files. You will have to set ``tcp_extensions=NO'' in /etc/sysconfig if your site has problem with the extensions. The default is YES. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505111909.MAA10840>