#749 closed (fixed)
AVILA: STP is not working fine
| Reported by: | samueldg | Owned by: | somebody |
|---|---|---|---|
| Keywords: | Cc: |
Description
Simple example:
ROOTBRIDGE -- AVILA0 -- AVILA1
Enable STP in all devices. Put en ROOTBRIDGE a low bridge prio (50, for example).
Execute in AVILA0 and AVILA1 brctl showstp br0 and see that only AVILA0 recognizes the ROOTBRIDGE.
Change History (7)
comment:1 Changed 4 years ago by samueldg
comment:2 Changed 4 years ago by BrainSlayer
then point be to these patches. i never heard of these and we also had no problems with stp yet in our tests
comment:3 Changed 4 years ago by samueldg
I read about it in kernels Changelogs, don't know where they are or if really they will correct this problem.
About the problem, the avilas where linked using WDS-STA and WDS-AP.
comment:4 Changed 4 years ago by samueldg
Another problem, perhaps with relationship with this.
If you force the interfaces into the bridge (using web page), the weights are not correctly assigned to them. For example you put 40 on ipx0, when you save and apply (or reestart the device) that weights are not assigned (or is not correctly passed to brctl in a permanent mode).
The configuration is not complex, you configure a device with all wifi interfaces bridged (web page option). This assign, by default, all the interfaces to br0. This is correct.
The problem is: How you can put (pemanently) the br0 prio and br0 ports weights? I tried to assign manually (using the bridging options in web) the ports to br0 and this don't work.
I know that I can configure the firewall script with brctl commands, but I think there is some work to finish the bridging mode.
Under my view, bridging need to be finished these points:
1) The problems with STP (as described below).
2) Options to allow put into the default bridge (br0) the configurable parameters (priority and ports weigths).
comment:5 Changed 4 years ago by BrainSlayer
- Resolution set to fixed
- Status changed from new to closed
stp is fixed now for wireless bridges. the other problem has a easy solution. simply recreate the br0 config with setup->networking
comment:6 Changed 4 years ago by samueldg
Thanks. Appears to be working in 20081206 build. We are testing now if works fine with broadcom devices too.
I remember some bridge patches over recent kernels, perhaps that does the trick.