From owner-freebsd-current  Thu Dec 23 14:55:16 1999
Delivered-To: freebsd-current@freebsd.org
Received: from mailman.cs.ucla.edu (Mailman.CS.UCLA.EDU [131.179.128.30])
	by hub.freebsd.org (Postfix) with ESMTP
	id E0D2514F49; Thu, 23 Dec 1999 14:55:13 -0800 (PST)
	(envelope-from scottm@CS.UCLA.EDU)
Received: from mordred.cs.ucla.edu (mordred.cs.ucla.edu [131.179.192.128])
	by mailman.cs.ucla.edu (8.9.1/UCLACS-5.0) with ESMTP id OAA29549;
	Thu, 23 Dec 1999 14:55:59 -0800 (PST)
Received: (from scottm@localhost)
	by mordred.cs.ucla.edu (8.9.3/UCLACS-5.0) id OAA00872;
	Thu, 23 Dec 1999 14:55:13 -0800 (PST)
Date: Thu, 23 Dec 1999 14:55:13 -0800 (PST)
From: Scott Michel <scottm@CS.UCLA.EDU>
Message-Id: <199912232255.OAA00872@mordred.cs.ucla.edu>
To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org
Subject: TCP Oddities followup
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

As I'd recently posted on -current, I've been noticing TCP oddities in
3.3 and 3.4. I've got a pn card (NetGear FA310tx) and a few new things
to report:

- Invariably, a TCP connection will freeze with something in the send
  queue. Connections don't freeze even if there's something in the
  receive queue.

- tcpdump-ing the pn0 interface shows that the host thinks that it's
  sending data. tcpdump-ing elsewhere in the network shows that pn0
  isn't actually transmitting anything into the wire.

- This really is a TCP or interface bug because NFS connections don't
  freeze using UDP.

- Other TCP connections continue to operate (like a cvsup in the
  background)

I haven't stared at the if_pn.c code all that closely but I'm willing
to entertain debugging suggestions.


-scooter


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message