From owner-freebsd-current  Mon Jan 22 14:10:29 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA20421
          for current-outgoing; Mon, 22 Jan 1996 14:10:29 -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 OAA20390
          Mon, 22 Jan 1996 14:10:17 -0800 (PST)
Received: from localhost.shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.3/8.7.3) with SMTP id OAA06366; Mon, 22 Jan 1996 14:09:22 -0800 (PST)
Message-Id: <199601222209.OAA06366@precipice.shockwave.com>
To: Andras Olah <olah@cs.utwente.nl>, wollman@freebsd.org
cc: current@freebsd.org, Adam Hawks <root@pent.vnet.net>,
        -Vince- <vince@apollo.COSC.GOV>
Subject: Re: finger problem going from 2.1R to -current 
In-reply-to: Your message of "Mon, 15 Jan 1996 09:39:23 +0100."
             <1763.821695163@curie.cs.utwente.nl> 
Date: Mon, 22 Jan 1996 14:09:21 -0800
From: Paul Traina <pst@shockwave.com>
Sender: owner-current@freebsd.org
Precedence: bulk


  From: Andras Olah <olah@cs.utwente.nl>
  Subject: Re: finger problem going from 2.1R to -current 
  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.
  
  Andras

That is not sufficient, we STILL need to patch the code to not send out
christmas tree syn packets when ttcp is disabled.  We're still doing it
as of 2 weeks ago.

Garret?

Paul

p.s. I am about 2 weeks out of date and catching up on e-mail, so don't
     take this as a flame if it's already been done.