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)
Artyom Viklenko
artem at aws-net.org.ua
Tue Jan 11 19:57:20 UTC 2011
11.01.2011 21:48, Bjoern A. Zeeb пишет:
> On Tue, 11 Jan 2011, Artyom Viklenko wrote:
>
>> 11.01.2011 21:29, Lev Serebryakov ?????:
>>>
>>> root at 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?..
>
> That's probably just because it cannot tell what the peer really uses
> (autoneg disabled) and prints the sane fall-back but I don't know the code.
>
Is it possible to see status from corresponding port on Juniper switch?
Config part for this port on the switch would be also very interesting.
--
Sincerely yours,
Artyom Viklenko.
-------------------------------------------------------
artem at aws-net.org.ua | http://www.aws-net.org.ua/~artem
artem at viklenko.net | JID: artem at jabber.aws-net.org.ua
FreeBSD: The Power to Serve - http://www.freebsd.org
More information about the freebsd-net
mailing list