Repository : ssh://git@open-mesh.org/doc
On branches: backup-redmine/2017-07-13,master
commit 5714bbf9d4eaa03cd33dc9209b2d9798b79eb18c Author: Marek Lindner mareklindner@neomailbox.ch Date: Tue Oct 25 18:42:58 2011 +0000
doc: batman-adv/Bridge-loop-avoidance-II
5714bbf9d4eaa03cd33dc9209b2d9798b79eb18c batman-adv/Bridge-loop-avoidance-II.textile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/batman-adv/Bridge-loop-avoidance-II.textile b/batman-adv/Bridge-loop-avoidance-II.textile index 61cd9f2d..48cbf7b2 100644 --- a/batman-adv/Bridge-loop-avoidance-II.textile +++ b/batman-adv/Bridge-loop-avoidance-II.textile @@ -23,9 +23,9 @@ h2. Goals:
h2. Key Concepts:
-h3. Claims: +h3. Claiming clients:
-Only one backbone gateway (out of possibly many gateways) should serve a client from the mesh for the LAN. This is announced by sending "claim frames" on the soft-interface bat0. A "claim frames" contains a MAC address the backbone gateway feels responsible for. Each backbone gateway will save a claim list of other backbone gateways. By doing this, it can: +Only one backbone gateway (out of possibly many gateways) should forward traffic from a non-mesh client (coming via the mesh) to the LAN. Every backbone gateway announces the mac addresses of the non-mesh clients it feels responsible for in the form of "claim frames" on the soft-interface bat0. Each backbone gateway will save a claim list of other backbone gateways. By doing this, it can:
* see which clients are already tracked (claimed) * see which other backbone gateways exist in the LAN