On Tue, 13 May 2014 16:39:14 -0700
Santiago Garcia Mantinan <ma...@debian.org> wrote:

> Hi!
> 
> Doing more tests on this I came to the conclusion that the problem we found
> when creating the bridge with iproute must be a bug on iproute when creating
> a bridge while setting a MAC.
> 
> If I create a bridge using:
> 
> # ip link add br2 address fc:cc:cc:cc:cc:cc type bridge
> 
> I end up with a wrong bridge id:
> 
> # brctl showstp br2
> br2
>  bridge id              8000.000000000000
>  designated root        8000.000000000000
>  root port                 0                    path cost                  0
>  max age                  20.00                 bridge max age            
> 20.00
>  hello time                2.00                 bridge hello time          
> 2.00
>  forward delay            15.00                 bridge forward delay      
> 15.00
>  ageing time             300.00
>  hello timer               0.00                 tcn timer                  
> 0.00
>  topology change timer     0.00                 gc timer                   
> 0.00
>  flags                  
> 
> If I later add a port to this bridge it seems the bridge doesn't work and
> the bridge id continues to be the same.
> 
> I have however identified what seems to be a workaround for this but it
> seems to kill the solution for lukas setup, the workaround consists of
> creating the bridge with a forced MAC and after the interface is up change
> it to another MAC, then the bridge id is changed to match the MAC address
> (fixes real hardware setup) but the dummy bridge scenario (Lukas setup)
> seems to break (interface keeps the ipv6 address but goes to state DOWN).
> Lukas, can you test this and see if it really breaks your setup?
> 
> I'm going to release a new version of the package with the general solution
> and ping the iproute guys to take a look into this.
> 
> Regards.

Fixed upstream

commit 30313a3d5794472c3548d7288e306a5492030370
Author: Toshiaki Makita <makita.toshi...@lab.ntt.co.jp>
Date:   Fri Apr 25 17:01:18 2014 +0900

    bridge: Handle IFLA_ADDRESS correctly when creating bridge device
    
    When bridge device is created with IFLA_ADDRESS, we are not calling
    br_stp_change_bridge_id(), which leads to incorrect local fdb
    management and bridge id calculation, and prevents us from receiving
    frames on the bridge device.
    
    Reported-by: Tom Gundersen <t...@jklm.no>
    Signed-off-by: Toshiaki Makita <makita.toshi...@lab.ntt.co.jp>
    Signed-off-by: David S. Miller <da...@davemloft.net>


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to