From: Simon Wunderlich simon@open-mesh.com
When changing configuration on top of batman-adv, for example in firmwares, there are two cases which appeared to be problematic and causing initial temporary loops when starting batman-adv.
* when activating batman-adv with vlans and bridges, it may take longer than 30 seconds to start up the bridges. If the grace period is over by that time, the BLA grace period may already be over. Therefore increase the grace period to 60 seconds. * When changing the network configuration, e.g. adding or removing wired interface in a bridge, it may be useful to re-start the grace period. Therefore the bridge loop avoidance state is dropped when BLA is turned off, so turning off/on bla can be used to restart the grace period.
These two fixes addressed the problems we had in our setups.
The patches are based on top of the current master (since its technically more a feature than a fix), plus the kerneldoc fix sent last week.
Cheers, Simon
Simon Wunderlich (2): batman-adv: purge bridge loop avoidance when its disabled batman-adv: increase BLA wait periods to 6
net/batman-adv/bridge_loop_avoidance.c | 20 ++++++++++++++++++++ net/batman-adv/bridge_loop_avoidance.h | 1 + net/batman-adv/main.h | 2 +- net/batman-adv/sysfs.c | 4 +++- 4 files changed, 25 insertions(+), 2 deletions(-)