From owner-freebsd-hackers Tue Jul 4 20:25:53 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id UAA29920 for hackers-outgoing; Tue, 4 Jul 1995 20:25:53 -0700 Received: from misery.sdf.com (misery.sdf.com [204.191.196.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id UAA29908 ; Tue, 4 Jul 1995 20:25:12 -0700 Received: (from tom@localhost) by misery.sdf.com (8.7.Beta.7/8.7.Beta.7) id UAA08651; Tue, 4 Jul 1995 20:26:57 -0700 (PDT) Date: Tue, 4 Jul 1995 20:26:51 -0700 (PDT) From: Tom Samplonius To: "Justin T. Gibbs" cc: "Christoph P. Kukulies" , freebsd-hackers@freefall.cdrom.com Subject: Re: 0622 installation woes (/nfs not found) In-Reply-To: <199507050247.TAA28306@freefall.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@FreeBSD.org Precedence: bulk On Tue, 4 Jul 1995, Justin T. Gibbs wrote: > I guess I wasn't clear on the problem. The problem is if the distribution > is sitting on another FreeBSD machine, rfc1323 and rfc1644 will be negotiated. > Many annexen and other terminal servers cannot handle these packetts, so > any tcp session will fail to a host that supports the advanced tcp options. Are you saying that Annex terminal servers fail to handle TCP packets with rfc1323 and rfc1644 options on connections passing through the terminal server, or on connections to the terminal server? In otherwords, FreeBSD --> Annex --> FreeBSD, or FreeBSD --> Annex. If it is the first option, why is the terminal server looking at TCP options when it is acting as an IP router? Tom