From owner-freebsd-stable Thu Dec 23 18:35:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mailman.cs.ucla.edu (Mailman.CS.UCLA.EDU [131.179.128.30]) by hub.freebsd.org (Postfix) with ESMTP id 0725714C56; Thu, 23 Dec 1999 18:35:32 -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 SAA22597; Thu, 23 Dec 1999 18:36:18 -0800 (PST) Received: from cs.ucla.edu (localhost.cs.ucla.edu [127.0.0.1]) by mordred.cs.ucla.edu (8.9.3/UCLACS-5.0) with ESMTP id SAA01818; Thu, 23 Dec 1999 18:35:31 -0800 (PST) Message-ID: <3862DBF3.B0EC432B@cs.ucla.edu> Date: Thu, 23 Dec 1999 18:35:31 -0800 From: "B. Scott Michel" Organization: UCLA Computer Chaos X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: TCP Oddities followup References: <199912232255.OAA00872@mordred.cs.ucla.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message