From: Bart De Schuymer <bdschuym@pandora.be>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter@vger.kernel.org
Subject: Re: Forced lladdr change with bridge - or not?
Date: Sun, 22 Aug 2010 18:55:03 +0200 [thread overview]
Message-ID: <4C715667.9070008@pandora.be> (raw)
In-Reply-To: <alpine.LSU.2.01.1008221812200.22261@obet.zrqbmnf.qr>
Jan Engelhardt schreef:
> Hi,
>
>
>
> # tunctl -p -t tap1
> Set 'tap1' persistent and owned by uid 0
> # tunctl -p -t tap2
> Set 'tap2' persistent and owned by uid 0
> # ip a
> 196: tap1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 500
> link/ether 9a:17:c4:65:e9:76 brd ff:ff:ff:ff:ff:ff
> 197: tap2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 500
> link/ether ce:61:28:5a:b7:93 brd ff:ff:ff:ff:ff:ff
> # brctl addbr br0
> # brctl addif br0 tap1
> # brctl addif br0 tap2
> # ip a
> 196: tap1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 500
> link/ether 9a:17:c4:65:e9:76 brd ff:ff:ff:ff:ff:ff
> 197: tap2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 500
> link/ether ce:61:28:5a:b7:93 brd ff:ff:ff:ff:ff:ff
> 198: br0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
> link/ether 9a:17:c4:65:e9:76 brd ff:ff:ff:ff:ff:ff
>
> Is this behavior normal that the lladdrs of all but the first brport
> remain unchanged? If so, what is the purpose of changing the lladdr on
> the first brport?
>
>
I don't understand your question, but the Linux bridge code assigns the
MAC address of its first-added port to the virtual bridge device.
Best regards,
Bart
--
Bart De Schuymer
www.artinalgorithms.be
next prev parent reply other threads:[~2010-08-22 16:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-22 16:12 Forced lladdr change with bridge - or not? Jan Engelhardt
2010-08-22 16:55 ` Bart De Schuymer [this message]
2010-08-22 17:28 ` Jan Engelhardt
2010-08-22 20:53 ` Pascal Hambourg
2010-08-22 21:24 ` Jan Engelhardt
2010-08-23 8:21 ` Pascal Hambourg
2010-08-23 11:23 ` Jan Engelhardt
[not found] <835126759.1436781282547490956.JavaMail.root@tendai.telenet-ops.be>
2010-08-23 7:14 ` bdschuym
2010-08-23 8:13 ` Pascal Hambourg
2010-08-24 11:21 ` Pascal Hambourg
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=4C715667.9070008@pandora.be \
--to=bdschuym@pandora.be \
--cc=jengelh@medozas.de \
--cc=netfilter@vger.kernel.org \
/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