Date: Wed, 22 Dec 1999 14:12:08 -0600 From: Jonathan Lemon <jlemon@americantv.com> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: 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: <19991222141208.07062@right.PCS> In-Reply-To: <199912221937.LAA10414@apollo.backplane.com>; from Matthew Dillon on Dec 12, 1999 at 11:37:42AM -0800 References: <16589.945810831@critter.freebsd.dk> <199912212123.NAA02780@apollo.backplane.com> <19991222200017.A25228@patho.gen.nz> <v04220802b486491ca1af@[195.238.1.121]> <199912221937.LAA10414@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 12, 1999 at 11:37:42AM -0800, Matthew Dillon wrote: > I finally tracked it down. The loss is occuring in the link between > two of my switches. The link goes across my apartment - about 60 feet of > Cat-5 cable. That should be well within spec (you are supposed to be > able to do 100 meters) but it causes packet loss. The switches > autonegotiate full-duplex for the link (and I verified that it's actually > running at full duplex), but that's where the packet loss occurs. Very > weird. > > I was finally able to fix it by dropping in a 10BaseT hub to force the > switches to negotiate 10BaseT across the link. > > Maybe my cable is damaged or something. I'll run a second cable to see > if that's the problem or whether. > > The second switch is a LinkSys. I have a D-Link near my servers and a > LinkSys near my workstation. Another thing I to keep in mind, is that sometimes the switch is bad. I had a Netgear FS509 switch here that would eat packets transmitted through the GigE port under certain conditions. Netgear shipped me a new one, and I've been happy with it, until the same problem started happening again this morning. Perhaps in this case, it's a bad fiber cable, I'll have to do some more testing to track it down. -- Jonathan 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?19991222141208.07062>