From owner-freebsd-current Mon Jan 15 12:17:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA05366 for current-outgoing; Mon, 15 Jan 1996 12:17:36 -0800 (PST) Received: from interbev.mindspring.com (interbev.mindspring.com [204.180.142.2]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA05361 for ; Mon, 15 Jan 1996 12:17:33 -0800 (PST) Received: (from rsanders@localhost) by interbev.mindspring.com (8.7.Beta.13/8.7.Beta.2) id PAA28876; Mon, 15 Jan 1996 15:17:30 -0500 Date: Mon, 15 Jan 1996 15:17:30 -0500 From: Robert Sanders Message-Id: <199601152017.PAA28876@interbev.mindspring.com> To: freebsd-current@freebsd.org In-reply-to: Andras Olah's message of Mon, 15 Jan 1996 04:14:01 EST Subject: Re: finger problem going from 2.1R to -current References: <1763.821695163@curie.cs.utwente.nl> Sender: owner-current@freebsd.org Precedence: bulk On Mon, 15 Jan 1996 04:14:01 EST, Andras Olah said: > machines is caused by the use of T/TCP. Apparently some (buggy or > at least non-conformant) TCP stacks have problems with T/TCP. AIX and Linux both have problems with it. Solaris copes fine. > 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. It's short, so I'll just post it here. Both rfc1323 and rfc1644 are set to 0 on my machine. 15:13:10.980335 hrothgar.1081 > widow.finger: SFP 100905540:100905550(10) win 17520 (DF) 15:13:16.608004 hrothgar.1081 > widow.finger: SFP 100905540:100905550(10) win 17520 (DF) 15:13:40.608362 hrothgar.1081 > widow.finger: SFP 100905540:100905550(10) win 17520 (DF) AIX 4.1.2 doesn't seem to like packets with SYN and FIN that also include data. For those of you that want to work around the problem, changing all occurrences of MSG_EOF in src/usr.bin/finger/net.c to 0 should do it. -- Robert