On Tue, 13 Nov 2007 13:59:08 +0100
"IO te" <armbigendian@gmail.com> wrote:
> Hi,
> today we've tested the bridge-utils (kernel 2.6.15) STP in the
> following scenario using the madwifi 0.9.3.2:
>
> AP ch. 36 Sta
> |----------------------|
> BR1 | | BR2
> |----------------------|
> Sta ch. 40 AP
>
> Unfortunately it doesn't work because every port of both the boards
> remains in forwarding state.
>
> We were expecting that one of the four ports would move to the blocking
state.
> Obviously one of the two board is elected as root by STP and has both
> ports in forwarding state, the problem is on the other one.
>
> Anyway, these are the configurations:
>
> Board 1:
>
> wlanconfig ath0 create wlandev wifi0 wlanmode ap
> iwpriv ath0 mode 1
> iwconfig ath0 essid tratta1 channel 36
> iwpriv ath0 wds 1
> ifconfig ath0 0.0.0.0 up
> wlanconfig ath1 create wlandev wifi1 wlanmode sta nosbeacon
> iwpriv ath1 mode 1
> iwconfig ath1 essid tratta2
> iwpriv ath1 wds 1
> ifconfig ath1 0.0.0.0 up
> brctl addbr br0
> brctl addif br0 ath0
> brctl addif br0 ath1
> ifconfig br0 11.0.0.1/24 up
> brctl stp br0 on
>
> Board 2:
>
> wlanconfig ath0 create wlandev wifi0 wlanmode ap
> iwpriv ath0 mode 1
> iwconfig ath0 essid tratta2 channel 40
> ifconfig ath0 0.0.0.0 up
> wlanconfig ath1 create wlandev wifi1 wlanmode sta nosbeacon
> iwpriv ath1 mode 1
> iwconfig ath1 essid tratta1
> iwpriv ath1 wds 1
> ifconfig ath1 0.0.0.0 up
> brctl addbr br0
> brctl addif br0 ath0
> brctl addif br0 ath1
> ifconfig br0 11.0.0.2/24 up
> brctl stp br0 on
>
> The interfaces associate in the right way, but this is the result of
> the command brctl showstp br0:
>
> Board 1:
>
> # brctl showstp br0
> br0
> bridge id 8000.00026f408483
> designated root 8000.00026f408483
> 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.35 tcn timer
0.00
> topology change timer 0.00 gc timer
0.07
> flags
>
>
> ath0 (0)
> port id 0000 state
forwarding
> designated root 8000.00026f408483 path cost
100
> designated bridge 8000.00026f408483 message age timer
0.00
> designated port 8001 forward delay timer
0.00
> designated cost 0 hold timer
0.34
> flags
>
> ath1 (0)
> port id 0000 state
forwarding
> designated root 8000.00026f408483 path cost
100
> designated bridge 8000.00026f408483 message age timer
0.00
> designated port 8002 forward delay timer
0.00
> designated cost 0 hold timer
0.00
> flags
>
> Board 2:
>
> # brctl showstp br0
> br0
> bridge id 8000.00156d539d8d
> designated root 8000.00026f408483
> root port 1 path cost
100
> 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 100.00
> hello timer 0.00 tcn timer
0.00
> topology change timer 0.00 gc timer
0.08
> flags
>
>
> ath0 (0)
> port id 0000 state
forwarding
> designated root 8000.00026f408483 path cost
100
> designated bridge 8000.00026f408483 message age timer
19.70
> designated port 8002 forward delay timer
0.00
> designated cost 0 hold timer
0.00
> flags
>
> ath1 (0)
> port id 0000 state
forwarding
> designated root 8000.00026f408483 path cost
100
> designated bridge 8000.00156d539d8d message age timer
0.00
> designated port 8002 forward delay timer
0.00
> designated cost 100 hold timer
0.69
> flags
>
>
> Thanks in advance for all your help
>
> Andrea, Massimiliano and Riccardo
> _______________________________________________
> Bridge mailing list
> Bridge@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/bridge
Are the multicast spanning tree packets making it from bridge to bridge?
You probably want to enable stp first.
--
Stephen Hemminger <shemminger@linux-foundation.org>