Date: Wed, 12 Jan 2011 11:52:08 +0300 From: Lev Serebryakov <lev@serebryakov.spb.ru> To: Bernd Walter <ticso@cicely7.cicely.de> Cc: freebsd-net@freebsd.org, Artyom Viklenko <artem@aws-net.org.ua>, ticso@cicely.de Subject: Re: Juniper e3k with ports limitied to 100Mbit and re NICs on MSI MoBo: problems with duplex negotiation (Hetzner host provider discard FreeBSD support due this bug) Message-ID: <165642603.20110112115208@serebryakov.spb.ru> In-Reply-To: <20110111220314.GZ39356@cicely7.cicely.de> References: <1512738982.20110111124729@serebryakov.spb.ru> <20110111163825.GF7511@numachi.com> <76226157.20110111222913@serebryakov.spb.ru> <4D2CB1F5.6080106@aws-net.org.ua> <98602823.20110111225049@serebryakov.spb.ru> <20110111220314.GZ39356@cicely7.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Bernd. You wrote 12 =FF=ED=E2=E0=F0=FF 2011 =E3., 1:03:14: > I'm not surprised that it doesn't work with autonegotian if autonegotian > is disabled. > If Linux does full-duplex without autonegotiation then _they_ do it wrong > and Hetzner shouldn't rely on wrong behavour. As far as I understand, Linux does full-duplex without autonegotiation because it is say to do full-duplex (like FreeBSD's "ifconfig re0 media 100baseTX mediaopt full-duplex"). Is it violation of standard too -- manual configuration of FD? > However since you seem to have access it might be interesting to know the > exact network device and debug why hard setting is broken. As far as I understand, again, it is not broken, but disabled, because cause problems on some devices... --=20 // Black Lion AKA Lev Serebryakov <lev@serebryakov.spb.ru>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?165642603.20110112115208>