From owner-freebsd-current Thu Dec 23 23:20: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 8EAD715198; Thu, 23 Dec 1999 23:20:04 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA10161; Thu, 23 Dec 1999 23:20:03 -0800 (PST) (envelope-from dillon) Date: Thu, 23 Dec 1999 23:20:03 -0800 (PST) From: Matthew Dillon Message-Id: <199912240720.XAA10161@apollo.backplane.com> To: "B. Scott Michel" Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: TCP Oddities followup References: <199912232255.OAA00872@mordred.cs.ucla.edu> <3862DBF3.B0EC432B@cs.ucla.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Scott Michel wrote: :> - 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. : :The host appears to be doing retransmissions but nothing goes out :on the wire. : :> - This really is a TCP or interface bug because NFS connections don't :> freeze using UDP. : :It's not just NFS. I can duplicate this behavior with scp and :cvsup (things that do bulk data transfer.) : : :-scooter Try doing a ping on the host with the pn0 interface to another machine. See if the packets it thinks it is sending get transmitted after a bunch of ping packets have accumulated. somethign like 'ping -i 0.03 remotehost' so it writes a lot of packets out. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message