From owner-freebsd-questions Thu Feb 17 13:22:57 2000 Delivered-To: freebsd-questions@freebsd.org Received: from benge.graphics.cornell.edu (benge.graphics.cornell.edu [128.84.247.43]) by hub.freebsd.org (Postfix) with ESMTP id 1FF5637B779 for ; Thu, 17 Feb 2000 13:22:49 -0800 (PST) (envelope-from mkc@benge.graphics.cornell.edu) Received: from benge.graphics.cornell.edu (mkc@localhost) by benge.graphics.cornell.edu (8.9.3/8.9.3) with ESMTP id QAA76858; Thu, 17 Feb 2000 16:22:43 -0500 (EST) (envelope-from mkc@benge.graphics.cornell.edu) Message-Id: <200002172122.QAA76858@benge.graphics.cornell.edu> To: Bill Sanborn Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Interesting network situation. Owners of Linksys hubs may want to read In-Reply-To: Message from Bill Sanborn of "Thu, 17 Feb 2000 12:36:47 PST." <38AC5BDF.62B19D34@uswest.net> Date: Thu, 17 Feb 2000 16:22:43 -0500 From: Mitch Collinsworth Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What would be specific to FreeBSD that would cause the hub to go >ick? The MTU is set to 1500 on both stations, and only TCP/IP is running >on the OSR2 PC. The hub also verifies that both PCs have negotiated >100Mb connections. I've forced the xl0 device to a 100baseTX connection, >so I don't think it is autonegotiating itself to death. Another oddity >is that when I'm transferring files from FBSD to the Windows station, >using the hub, the collision light goes berserk. This seems like cruddy >firmware to me. > > If anyone has any ideas I would be really interested in reading >them. If I were to guess I'd say your NIC is getting set to full duplex. Hubs are half-duplex only. (You can't do full-duplex in a collision domain.) -Mitch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message