Date: Sun, 10 Mar 1996 13:10:39 -0800 From: Paul Traina <pst@shockwave.com> To: Andrew Foster <adf@fl.net.au> Cc: Andras Olah <olah@cs.utwente.nl>, current@FreeBSD.org Subject: Re: finger and 2.2-960303-SNAP Message-ID: <199603102110.NAA09940@precipice.shockwave.com> In-Reply-To: Your message of "Mon, 11 Mar 1996 06:23:01 -1000." <2.2.32.19960311162301.00a4bcf4@mail.fl.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Old finger does not have the code in it to invoke t/tcp. Garrett did it to finger specificly so we had a good chance of finding broken tcp implementations in a non-critical fashion. It really is T/TCP behavior that isn't working, this is exactly the pattern. From: Andrew Foster <adf@fl.net.au> Subject: Re: finger and 2.2-960303-SNAP >Your peer (annex1.fl.net.au) has a broken TCP implementation and >gets confused by the <SYN,data,FIN> T/TCP packets. Your options: > >1. Get Xylogics fix their TCP stack (preferred ;-). >2. Disable tcp_extensions in /etc/sysconfig. Actually, it's enough >to do `sysctl -w net.inet.tcp.rfc1644=0' if you don't want to lose >the other TCP extensions. > >Andras > >P.S: You can look up the T/TCP homepage for information about T/TCP >including a list of TCP stacks having problem with T/TCP. > http://www.noao.edu/~rstevens/ttcp.html And yet the old finger works fine, as does fingering from most other hosts I've tried. Thanks, Andrew ----------- Andrew Foster Sydney, Australia
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603102110.NAA09940>