From owner-freebsd-current Wed Dec 22 12:12:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 177CF14DDF for ; Wed, 22 Dec 1999 12:12:36 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id OAA29766; Wed, 22 Dec 1999 14:12:10 -0600 (CST) Received: (from jlemon@localhost) by right.PCS (8.8.5/8.6.4) id OAA23321; Wed, 22 Dec 1999 14:12:09 -0600 (CST) Message-ID: <19991222141208.07062@right.PCS> Date: Wed, 22 Dec 1999 14:12:08 -0600 From: Jonathan Lemon To: Matthew Dillon Cc: Brad Knowles , Joe Abley , Poul-Henning Kamp , Garrett Wollman , freebsd-current@FreeBSD.ORG Subject: Re: Odd TCP glitches in new currents References: <16589.945810831@critter.freebsd.dk> <199912212123.NAA02780@apollo.backplane.com> <19991222200017.A25228@patho.gen.nz> <199912221937.LAA10414@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <199912221937.LAA10414@apollo.backplane.com>; from Matthew Dillon on Dec 12, 1999 at 11:37:42AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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