From owner-freebsd-current  Mon Jan 15 12:56:51 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA07839
          for current-outgoing; Mon, 15 Jan 1996 12:56:51 -0800 (PST)
Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA07832
          for <freebsd-current@freebsd.org>; Mon, 15 Jan 1996 12:56:48 -0800 (PST)
Received: (from vince@localhost) by apollo.COSC.GOV (8.7.3/8.6.9) id MAA08423; Mon, 15 Jan 1996 12:56:47 -0800 (PST)
Date: Mon, 15 Jan 1996 12:56:47 -0800 (PST)
From: -Vince- <vince@apollo.COSC.GOV>
To: Robert Sanders <rsanders@mindspring.com>
cc: freebsd-current@freebsd.org
Subject: Re: finger problem going from 2.1R to -current 
In-Reply-To: <199601152017.PAA28876@interbev.mindspring.com>
Message-ID: <Pine.BSF.3.91.960115125532.20064d-100000@apollo.COSC.GOV>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
Precedence: bulk

On Mon, 15 Jan 1996, Robert Sanders wrote:

> On Mon, 15 Jan 1996 04:14:01 EST, Andras Olah <olah@cs.utwente.nl> said:
> 
> > machines is caused by the use of T/TCP.  Apparently some (buggy or
> > at least non-conformant) TCP stacks have problems with T/TCP.
> 
> AIX and Linux both have problems with it.  Solaris copes fine.

	I never noticed the Linux one until you mentioned it...  But wonder
why both AIX and Linux has problems with it...

> > 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.
> 
> It's short, so I'll just post it here.  Both rfc1323 and rfc1644 are
> set to 0 on my machine.
> 
> 15:13:10.980335 hrothgar.1081 > widow.finger: SFP 100905540:100905550(10) win 17520 <mss 1460> (DF)
> 15:13:16.608004 hrothgar.1081 > widow.finger: SFP 100905540:100905550(10) win 17520 <mss 1460> (DF)
> 15:13:40.608362 hrothgar.1081 > widow.finger: SFP 100905540:100905550(10) win 17520 <mss 1460> (DF)
> 
> AIX 4.1.2 doesn't seem to like packets with SYN and FIN that also
> include data.

	Probably...

> For those of you that want to work around the problem, changing all
> occurrences of MSG_EOF in src/usr.bin/finger/net.c to 0 should do it.

	Maybe this can be committed to the tree...

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