From owner-freebsd-hackers Wed Jan 29 09:29:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA11122 for hackers-outgoing; Wed, 29 Jan 1997 09:29:23 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA11112 for ; Wed, 29 Jan 1997 09:29:20 -0800 (PST) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id JAA26014; Wed, 29 Jan 1997 09:29:16 -0800 (PST) Message-Id: <199701291729.JAA26014@austin.polstra.com> To: dg@root.com Subject: Re: RFC 1323 default settings (was Re: progress report on connection problems) Newsgroups: polstra.freebsd.hackers In-Reply-To: <199701290000.QAA17825@root.com> References: <199701290000.QAA17825@root.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Date: Wed, 29 Jan 1997 09:29:16 -0800 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Actually, the main reason it is on is for the other half of RFC 1323 which > specifies the "time stamp" extensions for better round-trip time estimates. > Unfortunately, I agree with you, however, that RFC 1323 extensions should be > disabled by default. The RFC 1644 extensions (T/TCP), however, should remain > enabled by default. This will only break "finger", and is useful for keeping > vendors TCP stacks compliant. Are you saying that the RFC 1644 extensions have no effect unless the application explicitly elects to use them? I was hoping that would be the case, but it doesn't seem to be. I have an old Lexmark printer hanging off my ethernet. If I turn on RFC 1644 (leaving RFC 1323 turned off), the first communication to the printer kills it so dead that I have to power cycle it to bring it back to life. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth