Date: Wed, 22 Dec 1999 20:24:37 -0800 (PST) From: Julian Elischer <julian@whistle.com> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: "B. Scott Michel" <scottm@CS.UCLA.EDU>, Jonathan Lemon <jlemon@americantv.com>, Brad Knowles <brad@shub-internet.org>, Joe Abley <jabley@patho.gen.nz>, Poul-Henning Kamp <phk@critter.freebsd.dk>, Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, freebsd-current@FreeBSD.ORG Subject: Re: Odd TCP glitches in new currents Message-ID: <Pine.BSF.4.10.9912222023410.50586-100000@current1.whistle.com> In-Reply-To: <199912230412.UAA15384@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9912222023410.50586-100000>