Repository : ssh://git@open-mesh.org/doc
On branches: backup-redmine/2017-07-13,master
commit 1e7bba1e9437a03919292c658fce1745b338191f Author: Marek Lindner mareklindner@neomailbox.ch Date: Tue Oct 25 18:44:22 2011 +0000
doc: batman-adv/Bridge-loop-avoidance-II
1e7bba1e9437a03919292c658fce1745b338191f batman-adv/Bridge-loop-avoidance-II.textile | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/batman-adv/Bridge-loop-avoidance-II.textile b/batman-adv/Bridge-loop-avoidance-II.textile index 48cbf7b2..7a9e41a2 100644 --- a/batman-adv/Bridge-loop-avoidance-II.textile +++ b/batman-adv/Bridge-loop-avoidance-II.textile @@ -36,8 +36,7 @@ Backbone gateways can also "unclaim" their own clients. After doing this, the cl
h2. Details and Cases:
-The concept will be explained by discussing the different cases: unicast and broadcast frames, both for the LAN->mesh and mesh->LAN case. Loop cases are considered too: LAN->mesh->LAN -and mesh->LAN->mesh. Furthermore, roaming is discussed when a client changes from the LAN to another mesh node and back. +The concept will be explained by discussing the different cases: unicast and broadcast frames, both for the LAN->mesh and mesh->LAN case. Loop cases are considered too: LAN->mesh->LAN and mesh->LAN->mesh. Furthermore, roaming (when a client changes from the LAN to another mesh node and back) is discussed.
h3. Broadcast, mesh->LAN: