netdev - Re: [PATCH net-next 0/8] bnx2x: Minor link related fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1283366622.5874.1.camel@lb-tlvb-eilong.il.broadcom.com>
Date:	Wed, 1 Sep 2010 21:43:42 +0300
From:	"Eilon Greenstein" <eilong@...adcom.com>
To:	"David Miller" <davem@...emloft.net>
cc:	"Yaniv Rosner" <yaniv.rosner@...adcom.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next 0/8] bnx2x: Minor link related fixes

On Wed, 2010-09-01 at 10:45 -0700, David Miller wrote:
> Can you explain why 10mbit/100mbit links have to use forced link mode
> and do not use autonegotiation by default?  I could understand for
> 10mbit but 100mbit too?
> 
Our understanding of the requirements is that if the user selects force
speed of 1G or higher, it is recommended to use autonegotiation with
only that speed advertized. However, when the user selects force speed
of 10M or 100M, assuming the other side is actually forcing the speed,
using autonegotiation will fail and fall back to parallel detect and
that will establish link in HD mode (as required) while the other side
is likely to be using FD this will cause duplex mismatch and many
errors, so it is best to keep 10M/100M truly forced to support older
link partners.

I hope it makes sense,
Eilon



--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html