On Tuesday 19 August 2014 15:42:36 Simon Wunderlich wrote:
From: Simon Wunderlich simon@open-mesh.com
There are network setups where the current bridge loop avoidance can't detect bridge loops. The minimal setup affected would consist of two LANs and two separate meshes, connected in a ring like that:
A...(mesh1)...B | | (LAN1) (LAN2) | | C...(mesh2)...D
Since both the meshes and backbones are separate, the bridge loop avoidance has not enough information to detect and avoid the loop in this case. Even if these scenarios can't be fixed easily, these kind of loops can be detected.
This patch implements a periodic check (running every 60 seconds for now) which sends a broadcast frame with a random MAC address on each backbone VLAN. If a broadcast frame with the same MAC address is received shortly after on the mesh, we know that there must be a loop and report that incident as well as throw an uevent to let others handle that problem.
Signed-off-by: Simon Wunderlich simon@open-mesh.com
It looks like this patch doesn't apply anymore. Can you please resent it or mark it correctly in patchwork [1].
Thanks, Sven