From: Jay Vosburgh <fubar@us.ibm.com>
To: "Tim Durack" <tdurack@gmail.com>
Cc: "Francois Romieu" <romieu@fr.zoreil.com>, netdev@vger.kernel.org
Subject: Re: r8169 ethernet bonding problems
Date: Fri, 27 Apr 2007 14:30:49 -0700 [thread overview]
Message-ID: <12883.1177709449@death> (raw)
In-Reply-To: <9e246b4d0704271353g105ecd62j4f35a6e9027ad590@mail.gmail.com>
Tim Durack <tdurack@gmail.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@us.ibm.com
next prev parent reply other threads:[~2007-04-27 21:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9e246b4d0704180552q16b05017wd0d7041c3ce04f46@mail.gmail.com>
[not found] ` <20070418181333.GA2261@electric-eye.fr.zoreil.com>
2007-04-27 20:53 ` r8169 ethernet bonding problems Tim Durack
2007-04-27 21:30 ` Jay Vosburgh [this message]
2007-04-27 21:44 ` Tim Durack
2007-04-27 22:09 ` Francois Romieu
2007-04-27 22:58 ` Francois Romieu
2007-04-30 14:39 ` Tim Durack
2007-04-30 15:32 ` Tim Durack
2007-04-30 15:38 ` Tim Durack
2007-05-01 20:17 ` Tim Durack
2007-05-01 20:47 ` Francois Romieu
2007-05-01 20:59 ` Tim Durack
2007-05-01 21:17 ` Francois Romieu
2007-05-02 17:38 ` Tim Durack
2007-05-02 18:03 ` Tim Durack
2007-06-18 22:59 ` Francois Romieu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12883.1177709449@death \
--to=fubar@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=tdurack@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.