Re: Forced lladdr change with bridge - or not?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 ?
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux