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

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

commit 3e5413ae5f02699ca51a1dfea79849d62f439a42 Author: Simon Wunderlich sw@simonwunderlich.de Date: Thu Oct 27 19:29:04 2011 +0000

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

3e5413ae5f02699ca51a1dfea79849d62f439a42 batman-adv/Bridge-loop-avoidance-II.textile | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/batman-adv/Bridge-loop-avoidance-II.textile b/batman-adv/Bridge-loop-avoidance-II.textile index d50462dc..eca026d3 100644 --- a/batman-adv/Bridge-loop-avoidance-II.textile +++ b/batman-adv/Bridge-loop-avoidance-II.textile @@ -48,9 +48,9 @@ The concept will be explained by discussing the different cases: unicast and bro h3. Broadcast, mesh->backbone:

!mesh_LAN.dia.png! -If the originator of the broadcast is not known (not in the originator table), drop it. +If the originator of the broadcast is not known (not in the originator table), don't forward it into the backbone.

-If the originator of the broadcast is another backbone gateway from the same backbone, drop it. +If the originator of the broadcast is another backbone gateway from the same backbone, don't forward.

If a backbone gateway has already claimed the client, only the responsible backbone gateway will deliver the frame to the backbone/LAN. Other backbone gateways will discard the packet.

@@ -81,21 +81,21 @@ h3. Unicast, backbone->mesh:

Nothing fancy should happen here, as a switch should do the right thing. If the client is not claimed, the frame is simply sent into the mesh.

-However, when using hubs (or broken switches), also unicast packets might loop. Therefore, if the client (source of the Ethernet frame) is claimed by any backbone gateway, drop it. +However, when using hubs (or broken switches), also unicast packets might loop. Therefore, if the client (source of the Ethernet frame) is claimed by any backbone gateway, don't forward.

h3. mesh->backbone->mesh loop:

!mesh_LAN_mesh.dia.png!

-A broadcast frame is only sent to backbone by the (yet to be) responsible backbone gateway. Back from the backbone to the mesh, all not responsible backbone gateways will drop the frame. The responsible backbone gateway should not receive it on normal switched networks. +A broadcast frame is only sent to backbone by the (yet to be) responsible backbone gateway. Back from the backbone to the mesh, all not responsible backbone gateways will not forward the frame. The responsible backbone gateway should not receive it on normal switched networks.

-To avoid loops for hubs, unicast packets are dropped from backbone to mesh if the client is claimed. +To avoid loops for hubs, unicast packets are not forwarded from backbone to mesh if the client is claimed.

h3. backbone->mesh->backbone loop:

!LAN_mesh_LAN.dia.png!

-Although a broadcast frame is sent into the mesh, it won't loop back into the backbone as a backbone gateway will drop it if was sent from another backbone gateway (from the same backbone). +Although a broadcast frame is sent into the mesh, it won't loop back into the backbone as a backbone gateway will not forward it if was sent from another backbone gateway (from the same backbone).

h3. backbone->mesh Roaming: