From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Bart De Schuymer <bdschuym@pandora.be>, netfilter@vger.kernel.org
Subject: Re: Forced lladdr change with bridge - or not?
Date: Mon, 23 Aug 2010 10:21:24 +0200 [thread overview]
Message-ID: <4C722F84.1080606@plouf.fr.eu.org> (raw)
In-Reply-To: <alpine.LSU.2.01.1008222321290.21206@obet.zrqbmnf.qr>
Jan Engelhardt a écrit :
> On Sunday 2010-08-22 22:53, Pascal Hambourg wrote:
>>>
>>>> I don't understand your question,
>> Me neither : according to your output, the MAC address of neither port
>> has changed.
>
> Well.. rerun `ip a` before enslaving tap to br and you see.
Sorry to insist heavily, but I still don't get your point.
You wrote :
> 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?
from which I understand that tap1's MAC address changed when it was
added to the bridge. But comparing tap1's MAC address from your own "ip
a" output before it is added to the bridge :
> 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
and after :
> 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
it appears to me that it didn't change.
Did I misunderstand something ?
next prev parent reply other threads:[~2010-08-23 8:21 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
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 [this message]
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=4C722F84.1080606@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.org \
--cc=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