Date: Mon, 15 Jan 1996 15:17:30 -0500 From: Robert Sanders <rsanders@mindspring.com> To: freebsd-current@freebsd.org Subject: Re: finger problem going from 2.1R to -current Message-ID: <199601152017.PAA28876@interbev.mindspring.com> In-Reply-To: Andras Olah's message of Mon, 15 Jan 1996 04:14:01 EST References: <1763.821695163@curie.cs.utwente.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 15 Jan 1996 04:14:01 EST, Andras Olah <olah@cs.utwente.nl> 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 <mss 1460> (DF) 15:13:16.608004 hrothgar.1081 > widow.finger: SFP 100905540:100905550(10) win 17520 <mss 1460> (DF) 15:13:40.608362 hrothgar.1081 > widow.finger: SFP 100905540:100905550(10) win 17520 <mss 1460> (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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601152017.PAA28876>