From owner-freebsd-bugs Mon Apr 3 13:19:40 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA17995 for bugs-outgoing; Mon, 3 Apr 1995 13:19:40 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id NAA17989; Mon, 3 Apr 1995 13:19:37 -0700 Received: by halloran-eldar.lcs.mit.edu; id AA22793; Mon, 3 Apr 1995 16:19:17 -0400 Date: Mon, 3 Apr 1995 16:19:17 -0400 From: Garrett Wollman Message-Id: <9504032019.AA22793@halloran-eldar.lcs.mit.edu> To: "Jordan K. Hubbard" Cc: gibbs@estienne.cs.berkeley.edu, freebsd-bugs@freefall.cdrom.com Subject: Re: misc/292: rfc1323 and rfc1644 support can confuse terminal servers w/SLIP In-Reply-To: <10282.796780895@freefall.cdrom.com> References: <199504012330.PAA09488@freefall.cdrom.com> <10282.796780895@freefall.cdrom.com> Sender: bugs-owner@FreeBSD.org Precedence: bulk < 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 -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant