From owner-freebsd-current  Mon Jan 15 00:40:37 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA27935
          for current-outgoing; Mon, 15 Jan 1996 00:40:37 -0800 (PST)
Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA27930
          for <current@FreeBSD.org>; Mon, 15 Jan 1996 00:40:33 -0800 (PST)
Received: from myrtilos.cs.utwente.nl by utrhcs.cs.utwente.nl (SMI-8.6/csrelayMX-SVR4_1.2/RBINF)
	id JAA13087; Mon, 15 Jan 1996 09:39:28 +0100
Received: from curie.cs.utwente.nl by myrtilos.cs.utwente.nl (SMI-8.6/csrelay-Sol1.4/RB)
	id JAA20996; Mon, 15 Jan 1996 09:39:24 +0100
Received: from localhost by curie.cs.utwente.nl (SMI-8.6/SMI-SVR4)
	id JAA01764; Mon, 15 Jan 1996 09:39:24 +0100
To: current@FreeBSD.org
cc: 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 "Sat, 13 Jan 1996 16:05:15 EST."
             <199601132105.QAA00363@pent.vnet.net> 
Date: Mon, 15 Jan 1996 09:39:23 +0100
Message-ID: <1763.821695163@curie.cs.utwente.nl>
From: Andras Olah <olah@cs.utwente.nl>
Sender: owner-current@FreeBSD.org
Precedence: bulk

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