From: Stephen Hemminger <shemminger@vyatta.com>
To: Rolf Fokkens <rolf.fokkens@wanadoo.nl>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Why should static MAC address match one of the port MAC addresses - bug?
Date: Sun, 26 Dec 2010 10:31:27 -0800 [thread overview]
Message-ID: <20101226103127.05cbd1c5@nehalam> (raw)
In-Reply-To: <4D1779B6.9050305@wanadoo.nl>
On Sun, 26 Dec 2010 18:21:58 +0100
Rolf Fokkens <rolf.fokkens@wanadoo.nl> wrote:
> In this particular situation it's not possible to do so as all
> interfaces are tap interfaces, with random generated MAC addresses.
> Changing the tap interface's MAC address results in this:
>
> [root@home01 ~]# ifconfig tap0 hw ether BA:B7:73:58:E6:E2
> SIOCSIFHWADDR: Device or resource busy
> [root@home01 ~]#
>
> So that doen't work. I found a trick however: I added a dummy ethernet
> interface to the bridge, of which i can specify the MAC address, It
> works fine, but in syslog there's the following message:
>
> Dec 26 17:45:21 home01 kernel: [ 29.316480] br0: new device dummy0
> does not support netpoll (disabling)
>
> This means that the bridge won't use/support netpoll at all, which may
> mean there's an impact on performance. I'm not sure. I can imagine that
> a netpoll interface for a dummy interface shouldn't be hard to implement.
>
The message means you can't use kdump/netconsole/kgdb over
that bridge device.
prev parent reply other threads:[~2010-12-26 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-19 22:26 [Bridge] Why should static MAC address match one of the port MAC addresses - bug? Rolf Fokkens
2010-12-20 18:37 ` Stephen Hemminger
2010-12-20 20:03 ` Rolf Fokkens
2010-12-20 23:15 ` Stephen Hemminger
2010-12-26 17:21 ` Rolf Fokkens
2010-12-26 18:31 ` Stephen Hemminger [this message]
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=20101226103127.05cbd1c5@nehalam \
--to=shemminger@vyatta.com \
--cc=bridge@lists.linux-foundation.org \
--cc=rolf.fokkens@wanadoo.nl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox