From owner-freebsd-current Sun Mar 10 13:11:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA19699 for current-outgoing; Sun, 10 Mar 1996 13:11:59 -0800 (PST) Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA19688 for ; Sun, 10 Mar 1996 13:11:55 -0800 (PST) Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.4/8.7.3) with SMTP id NAA09940; Sun, 10 Mar 1996 13:10:39 -0800 (PST) Message-Id: <199603102110.NAA09940@precipice.shockwave.com> To: Andrew Foster cc: Andras Olah , current@FreeBSD.org Subject: Re: finger and 2.2-960303-SNAP In-reply-to: Your message of "Mon, 11 Mar 1996 06:23:01 -1000." <2.2.32.19960311162301.00a4bcf4@mail.fl.net.au> Date: Sun, 10 Mar 1996 13:10:39 -0800 From: Paul Traina Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk 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 Subject: Re: finger and 2.2-960303-SNAP >Your peer (annex1.fl.net.au) has a broken TCP implementation and >gets confused by the 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