Repository : ssh://git@open-mesh.org/doc

On branches: backup-redmine/2017-07-13,master

commit 0d110ed2760963cd6e4716b2031d007b1e98d822 Author: Simon Wunderlich sw@simonwunderlich.de Date: Mon Oct 24 21:32:54 2011 +0000

doc: batman-adv/Bridge-loop-avoidance-II

0d110ed2760963cd6e4716b2031d007b1e98d822 batman-adv/Bridge-loop-avoidance-II.textile | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/batman-adv/Bridge-loop-avoidance-II.textile b/batman-adv/Bridge-loop-avoidance-II.textile index a93741d7..2d8786b3 100644 --- a/batman-adv/Bridge-loop-avoidance-II.textile +++ b/batman-adv/Bridge-loop-avoidance-II.textile @@ -93,13 +93,13 @@ Although a broadcast frame is sent into the mesh, it won't loop back into the LA

h3. LAN->mesh Roaming:

-(TODO: illustration) +!Test_roaming_LAN_mesh.dia.png!

This is the easy case: Sooner or later, a claim will be added for the roamed client.

h3. mesh->LAN Roaming:

-(TODO: illustration) +!Test_roaming_mesh_LAN.dia.png!

We assume that the client was already claimed by a backbone gateway before, otherwise there is nothing to consider.

@@ -210,7 +210,7 @@ h2. Test Cases

h3. Roaming from backbone to mesh

-!test_roaming_LAN_mesh.dia.png! +!Test_roaming_LAN_mesh.dia.png!

The client is connected to the backbone first and then roams to a mesh node which is not connected to the backbone.

@@ -218,7 +218,7 @@ Ping the internet gateway or a mesh node continuously and see if the connection

h3. Roaming from mesh to backbone

-!test_roaming_mesh_LAN.dia.png! +!Test_roaming_mesh_LAN.dia.png!

The client is connected to a meshnode first and then roams the backbone.