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: <12883.1177709449@death>
Date:	Fri, 27 Apr 2007 14:30:49 -0700
From:	Jay Vosburgh <fubar@...ibm.com>
To:	"Tim Durack" <tdurack@...il.com>
cc:	"Francois Romieu" <romieu@...zoreil.com>, netdev@...r.kernel.org
Subject: Re: r8169 ethernet bonding problems 

Tim Durack <tdurack@...il.com> wrote:

[...]
>Bond comes up, cannot ping unless I manually force promisc on both member links:
>
>ip link set dev eth1 promisc on
>ip link set dev eth2 promisc off

	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 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.

	-J

---
	-Jay Vosburgh, IBM Linux Technology Center, fubar@...ibm.com
-
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