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]

Date:	Fri, 27 Apr 2007 17:44:22 -0400
From:	"Tim Durack" <tdurack@...il.com>
To:	"Jay Vosburgh" <fubar@...ibm.com>
Cc:	"Francois Romieu" <romieu@...zoreil.com>, netdev@...r.kernel.org
Subject: Re: r8169 ethernet bonding problems

> >ip link set dev eth1 promisc on
> >ip link set dev eth2 promisc off

typo, "ip link set dev eth2 promisc on" of course

>
>        From looking at the source code for r8169, but it appears that
> the r8169 driver only reads the device MAC address at probe time, and
> doesn't propogate changes to the MAC out to the device.  That might
> explain the "promisc" problem if the device also does MAC filtering.  Am
> I missing something in the driver?

I have applied all patches from the set, including:

0012-r8169-mac-address-change-support.patch

which I assume adds the ability to reprogram MAC filtering.

Behaviour indicates the MAC filter doesn't get reprogrammed though.

>        I don't actually have one of these to test with, I'm just
> looking at the source and observing that dev_addr is only ever
> referenced in the probe function, and that's only to read in the MAC
> from the device.

You're not missing much, believe me :-|

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