From owner-freebsd-current Mon Jan 15 11:41:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA02992 for current-outgoing; Mon, 15 Jan 1996 11:41:16 -0800 (PST) Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA02987 for ; Mon, 15 Jan 1996 11:41:14 -0800 (PST) Received: (from vince@localhost) by apollo.COSC.GOV (8.7.3/8.6.9) id LAA05496; Mon, 15 Jan 1996 11:39:50 -0800 (PST) Date: Mon, 15 Jan 1996 11:39:49 -0800 (PST) From: -Vince- To: Andras Olah cc: current@FreeBSD.org, Adam Hawks Subject: Re: finger problem going from 2.1R to -current In-Reply-To: <1763.821695163@curie.cs.utwente.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Mon, 15 Jan 1996, Andras Olah wrote: > I'm almost sure that the problems related to finger from current > machines is caused by the use of T/TCP. Apparently some (buggy or > at least non-conformant) TCP stacks have problems with T/TCP. > > The short term solution is: `sysctl -w net.inet.tcp.rfc1644=0'. On > the other hand, it would be very useful if you could send me a > tcpdump trace of the failing conversation when using T/TCP and if > you know the type of the system you're connecting to. My rfc1644 and rc1323 is already set to 0 since we have a Cisco router so that isn't the problem. How do I do a tcpdump trace? The thing is this only happens on any machine running IBM's AIX... Cheers, -Vince- vince@COSC.GOV - GUS Mailing Lists Admin - http://www.COSC.GOV/~vince UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan/Priscilla Chan Fan Club Mailing Lists Admin