Why not refresh ipv6 local link address of a bridge when a new interface added to the bridge?

Why not refresh ipv6 local link address of a bridge when a new interface added to the bridge?

[Eric Xiong]

Hi all:
Sorry for disturb! when adding a interface to bridge, maybe the bridge
mac address will be changed. the bridge code don't invoke
call_netdevice_notifiers to notify ipv6 code to refresh local link
address. I don't know why. Thanks for your help!

BRs.

Re: Why not refresh ipv6 local link address of a bridge when a new interface added to the bridge?

[Stephen Hemminger]

On Tue, 20 Sep 2011 10:39:31 +0800
Eric Xiong <bottomofstack@gmail.com> wrote:

> Hi all:
> Sorry for disturb! when adding a interface to bridge, maybe the bridge
> mac address will be changed. the bridge code don't invoke
> call_netdevice_notifiers to notify ipv6 code to refresh local link
> address. I don't know why. Thanks for your help!
> 
> BRs.

This change went in for v3.1


    Bridge: Always send NETDEV_CHANGEADDR up on br MAC change.
    
    This ensures the neighbor entries associated with the bridge
    dev are flushed, also invalidating the associated cached L2 headers.
    
    This means we br_add_if/br_del_if ports to implement hand-over and
    not wind up with bridge packets going out with stale MAC.
    
    This means we can also change MAC of port device and also not wind
    up with bridge packets going out with stale MAC.
    
    This builds on Stephen Hemminger's patch, also handling the br_del_if
    case and the port MAC change case.
    
    Cc: Stephen Hemminger <shemminger@vyatta.com>
    Signed-off-by: Andrei Warkentin <andreiw@motorola.com>
    Acked-by: Stephen Hemminger <shemminger@vyatta.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>