From owner-freebsd-net@FreeBSD.ORG Tue Feb 28 12:12:51 2006 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44A6A16A420 for ; Tue, 28 Feb 2006 12:12:51 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6692243D46 for ; Tue, 28 Feb 2006 12:12:49 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A6834.dip.t-dialin.net [84.154.104.52]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id k1SCClpO097519; Tue, 28 Feb 2006 13:12:48 +0100 (CET) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id k1SCCfWq009592; Tue, 28 Feb 2006 13:12:41 +0100 (CET) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost.jhs.private [127.0.0.1]) by fire.jhs.private (8.13.1/8.13.1) with ESMTP id k1SCFdqM094182; Tue, 28 Feb 2006 13:15:39 +0100 (CET) (envelope-from jhs@fire.jhs.private) Message-Id: <200602281215.k1SCFdqM094182@fire.jhs.private> To: Mike Silbersack In-Reply-To: Message from Mike Silbersack of "Mon, 27 Feb 2006 22:27:52 CST." <20060227222544.F11734@odysseus.silby.com> Date: Tue, 28 Feb 2006 13:15:39 +0100 From: "Julian H. Stacey" Cc: jhs@berklix.com, Bernd Kopriva , net@freebsd.org Subject: Re: TCP_COMPAT_42 support X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2006 12:12:51 -0000 Mike Silbersack wrote: > On Mon, 27 Feb 2006, Julian Stacey wrote: > > Anyone know if modern FreeBSD still supports TCP_COMPAT_42 ? > TCP_COMPAT_42 just tweaked how we generated TCP initial sequence numbers. > The lack of it should not be impacting your ability to connect to machines > of any vintage. > Mike "Silby" Silbersack Thanks Mike, Well I fixed a local problem of parity on my FreeBSD end, by changing to XTerm*eightBitInput: False XTerm*eightBitOutput: False xrdb -merge ~/.Xdefaults But rlogins & telnets to the 4.2BSD Symmetric still die after exiting first command &/or time out within first minute. (& no timeout I can see on rlogind on 4.2 end, but rlogins from 4.2 to FreeBSD run OK ! It used to work, I wonder what presumably I changed ! -- Julian Stacey. Consultant Unix Net & Sys. Eng., Munich. http://berklix.com Mail in Ascii, HTML=spam. Ihr Rauch = meine allergischen Kopfschmerzen.