From owner-freebsd-bugs  Mon Apr  3 15:32:36 1995
Return-Path: bugs-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA21376 for bugs-outgoing; Mon, 3 Apr 1995 15:32:36 -0700
Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA21370; Mon, 3 Apr 1995 15:32:34 -0700
Received: by cs.weber.edu (4.1/SMI-4.1.1)
	id AA09297; Mon, 3 Apr 95 16:26:02 MDT
From: terry@cs.weber.edu (Terry Lambert)
Message-Id: <9504032226.AA09297@cs.weber.edu>
Subject: Re: misc/292: rfc1323 and rfc1644 support can confuse terminal servers w/SLIP
To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman)
Date: Mon, 3 Apr 95 16:26:01 MDT
Cc: jkh@freefall.cdrom.com, gibbs@estienne.cs.berkeley.edu,
        freebsd-bugs@freefall.cdrom.com
In-Reply-To: <9504032019.AA22793@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Apr 3, 95 04:19:17 pm
X-Mailer: ELM [version 2.4dev PL52]
Sender: bugs-owner@FreeBSD.org
Precedence: bulk

> 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.