From owner-freebsd-current Wed Dec 22 20:24:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id A2F0B14DD3 for ; Wed, 22 Dec 1999 20:24:54 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id UAA25069; Wed, 22 Dec 1999 20:24:38 -0800 (PST) Date: Wed, 22 Dec 1999 20:24:37 -0800 (PST) From: Julian Elischer To: Matthew Dillon Cc: "B. Scott Michel" , Jonathan Lemon , Brad Knowles , Joe Abley , Poul-Henning Kamp , Garrett Wollman , freebsd-current@FreeBSD.ORG Subject: Re: Odd TCP glitches in new currents In-Reply-To: <199912230412.UAA15384@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG make sure you test odd packet lengths. (as in "not even") there are occasional bugs that turn up with that sort of thing. On Wed, 22 Dec 1999, Matthew Dillon wrote: > I am clueless as to what is going on. It seems to only happen with TCP > connections. I wrote a UDP-based packet loss test program that sends > UDP packets at varying rates and sizes in both directions and figures > out where the loss is occuring, and I get nada. In fact, while its > running in the background I am *still* getting TCP stutters and tcpdump > still shows one machine sending a packet that the other machine never > gets! I have no friggin clue as to why TCP packets fail when UDP packets > don't. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message