From owner-freebsd-hackers Sat Feb 3 13:39:37 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA03123 for hackers-outgoing; Sat, 3 Feb 1996 13:39:37 -0800 (PST) Received: from zap.io.org (root@zap.io.org [198.133.36.81]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA03105 for ; Sat, 3 Feb 1996 13:39:31 -0800 (PST) Received: (from taob@localhost) by zap.io.org (8.6.12/8.6.12) id QAA06708; Sat, 3 Feb 1996 16:38:01 -0500 Date: Sat, 3 Feb 1996 16:38:01 -0500 (EST) From: Brian Tao To: David Greenman cc: hackers@FreeBSD.ORG Subject: Re: Why RFC1323 is disabled on freefall and freebsd.cdrom.com ? In-Reply-To: <199601291004.CAA29539@Root.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG Precedence: bulk On Mon, 29 Jan 1996, David Greenman wrote: > > It is disabled on both machines because they are public FTP/WWW servers, > and RFC1323 (and other TCP extensions) don't work for all people. What are the symptoms of it "not working"? TCP extensions are enabled on all the FreeBSD servers here (currently two shell servers, a Web server and the FTP/IRC server) and I haven't noticed anything unusual connecting to them through a 28.8k dialup line on a Livingston PM-2e terminal server. What should I be looking out for? -- Brian Tao (BT300, taob@io.org) Systems Administrator, Internex Online Inc. "Though this be madness, yet there is method in't"