Date: Mon, 15 Jan 1996 11:39:49 -0800 (PST) From: -Vince- <vince@apollo.COSC.GOV> To: Andras Olah <olah@cs.utwente.nl> Cc: current@FreeBSD.org, Adam Hawks <root@pent.vnet.net> Subject: Re: finger problem going from 2.1R to -current Message-ID: <Pine.BSF.3.91.960115113835.20064f@apollo.COSC.GOV> In-Reply-To: <1763.821695163@curie.cs.utwente.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.960115113835.20064f>