Repository : ssh://git@open-mesh.org/doc
On branches: backup-redmine/2017-07-13,master
commit 35d10d885d5f92c917114089dd03bfed8f71e8b4 Author: Simon Wunderlich sw@simonwunderlich.de Date: Tue Oct 4 00:28:45 2011 +0000
doc: batman-adv/Bridge-loop-avoidance-II
35d10d885d5f92c917114089dd03bfed8f71e8b4 batman-adv/Bridge-loop-avoidance-II.textile | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/batman-adv/Bridge-loop-avoidance-II.textile b/batman-adv/Bridge-loop-avoidance-II.textile index d1a73fc7..23a126e6 100644 --- a/batman-adv/Bridge-loop-avoidance-II.textile +++ b/batman-adv/Bridge-loop-avoidance-II.textile @@ -35,7 +35,8 @@ and mesh->LAN->mesh. Furthermore, roaming is discussed when a client changes fro h3. Broadcast, mesh->LAN:
If the originator of the broadcast is not known (not in the originator table), drop it. -If the originator of the broadcast is another gateway from the same LAN, drop it immediately. + +If the originator of the broadcast is another gateway from the same LAN, drop it.
If a gateway has already claimed the client, only the resposible gateway will deliver the frame to the bridge. Other gateways will discard the packet.