netdev - Re: r8169 ethernet bonding problems

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: <9e246b4d0705021038q458ab32r1c4f7431e7bd0f1@mail.gmail.com>
Date:	Wed, 2 May 2007 13:38:20 -0400
From:	"Tim Durack" <tdurack@...il.com>
To:	"Francois Romieu" <romieu@...zoreil.com>
Cc:	netdev@...r.kernel.org
Subject: Re: r8169 ethernet bonding problems

> > Yup. Works fine. The randomly changing interface order is proving to
> > be a challenge!
>
> udev should be your friend to do a BUS/ID based rename.

True, but so far I have to force link addrs, force promisc mode, and
now add a udev work-around ;-|

Strange thing is, when the interfaces get initialised as eth0/1/2 in
order, they all have the correct macs. When they appear out of order
(eth5/1/2, eth5/6/1 etc), at least one or more of the macs are messed
up.

Once yesterday I saw them initialise in order, with correct macs. Have
not been able to repeat or figure out if there is some way of
triggering this correct behaviour.

Any more driver patches I can beta test?

Tim:>
-
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