Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 11 Jan 2011 21:39:33 +0200
From:      Artyom Viklenko <artem@aws-net.org.ua>
To:        freebsd-net@freebsd.org
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:  <4D2CB1F5.6080106@aws-net.org.ua>
In-Reply-To: <76226157.20110111222913@serebryakov.spb.ru>
References:  <1512738982.20110111124729@serebryakov.spb.ru>	<20110111163825.GF7511@numachi.com> <76226157.20110111222913@serebryakov.spb.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
11.01.2011 21:29, Lev Serebryakov пишет:
> Hello, Brian.
> You wrote 11 января 2011 г., 19:38:25:
>
>
>>>    Very large and famous (due to very attractive prices) hosting
>>>   provider Hetzner.de discards FreeBSD support on dedicated servers,
>>>   because these servers can niot negotiate 100Mbit/DUPLEX when
>>>   switches' ports are limited to 100Mbit (1Gbit connection costs
>>>   additional money) only under FreeBSD. Linux works fine.
>> How are the switches being forced to 100/full?
>    I don't know, I never work with Juniper e3k switches (And any other
>   Juniper products at all).
>
>    All I know, that older Juniper Switches in not-so-new DCs of same
> provider doesn't have this problem, and, on other hand, Linux and
> Windows 2008 don't have problems with new ones too.
>
>> If they're doing so by disabling autonegotiation, then that's where
>> some grief may come from.
>   Linux work with autonegotiation, as I can see (It is outpuit from
>   Rescue Linux system on SAME my server, where FreeBSD shows
>   half-duplex even if forced to full-duplex):
>
> root@rescue ~ # mii-tool -v eth0
> eth0: 100 Mbit, full duplex, link ok
>    product info: vendor 00:07:32, model 17 rev 2
>    basic mode:   100 Mbit, full duplex
>    basic status: link ok
>    capabilities: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
>    advertising:  100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control


>    link partner: 100baseTx-HD
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Looks very strange for me... 'HD' means half-duplex?

May be linux driver defaults to full-duplex if autoneg fails?..


> root@rescue ~ # ethtool eth0
> Settings for eth0:
>          Supported ports: [ TP MII ]
>          Supported link modes:   10baseT/Half 10baseT/Full
>                                  100baseT/Half 100baseT/Full
>                                  1000baseT/Half 1000baseT/Full
>          Supports auto-negotiation: Yes
>          Advertised link modes:  10baseT/Half 10baseT/Full
>                                  100baseT/Half 100baseT/Full
>                                  1000baseT/Half 1000baseT/Full
>          Advertised auto-negotiation: No
>          Speed: 100Mb/s
>          Duplex: Full
>          Port: MII
>          PHYAD: 0
>          Transceiver: internal
>          Auto-negotiation: off
>          Supports Wake-on: pumbg
>          Wake-on: g
>          Current message level: 0x00000033 (51)
>          Link detected: yes
> root@rescue ~ #
>
>   So, it seems, that autonegotiation is disabled, but it works for
> Linux, and manual setting of media and mediaopt doesn't help FreeBSD.
>
>   Also, please note, that when port is in 1Gib mode (which can be buyed
>   for additional money, which I can not afford) FreeBSD works fine.
>


-- 
             Sincerely yours,
                                Artyom Viklenko.
-------------------------------------------------------
artem@aws-net.org.ua | http://www.aws-net.org.ua/~artem
artem@viklenko.net   | JID: artem@jabber.aws-net.org.ua
FreeBSD: The Power to Serve   -  http://www.freebsd.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D2CB1F5.6080106>