Date: Wed, 1 May 2002 23:49:02 +0200 (CEST) From: Sten <sten@blinkenlights.nl> To: Guido Kollerie <gkoller@chello.nl> Cc: Danny Braniss <danny@cs.huji.ac.il>, <current@FreeBSD.org>, <freebsd-stable@FreeBSD.org> Subject: Re: 3Com 3c905C-TX Message-ID: <Pine.LNX.4.44-Blink.0205012340220.2142-100000@deepthought.blinkenlights.nl> In-Reply-To: <20020501202806.GA256@node14e65.a2000.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 1 May 2002, Guido Kollerie wrote: <snip> > > Unfortunately the switch is unmanaged hence I am not able to > explicitely set the switch to 100 Mbits full-duplex. Using > ifconfig to set the nic to 10baseT/UTP and then back to 100baseTX > full-duplex doesn't help. Only a reboot will bring the NIC back > to 100 Mbits full duplex mode. Please note that due to vagaries in the auto-negotiation spec 3com and cisco dont work well together. And 3coms ( on linux atleast ) have the added bonus of sometimes deciding to change speed/duplex just for the heck of it. The only way to use them reliably is to force both the card and the switch. We came to the conclusion that fxp's are a nicer option. IMHO just creating a reliable and clearly defined auto-negotiation protocol will do more for ethernet speed than gigabit ethernet :). -- Sten Spans "What does one do with ones money, when there is no more empty rackspace ?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.44-Blink.0205012340220.2142-100000>