Repository : ssh://git@open-mesh.org/doc
On branches: backup-redmine/2017-07-13,master
commit 1e8577f92db95a2757426c4336cd2523b42ac7a2 Author: Simon Wunderlich sw@simonwunderlich.de Date: Thu Oct 27 18:00:36 2011 +0000
doc: batman-adv/Bridge-loop-avoidance-II: (re)move test cases to another page
1e8577f92db95a2757426c4336cd2523b42ac7a2 batman-adv/Bridge-loop-avoidance-II.textile | 62 ----------------------------- 1 file changed, 62 deletions(-)
diff --git a/batman-adv/Bridge-loop-avoidance-II.textile b/batman-adv/Bridge-loop-avoidance-II.textile index 9ac7ae91..0b0d646f 100644 --- a/batman-adv/Bridge-loop-avoidance-II.textile +++ b/batman-adv/Bridge-loop-avoidance-II.textile @@ -205,68 +205,6 @@ If the client is not claimed by any backbone gateway, every backbone gateway sha
(Note that it might be neccesary to connect the checksums to sequence numbers to allow intentionally sent duplicate payload broadcasts)
-h2. Test Cases - -h3. Roaming from backbone to mesh - -!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. - -Ping the internet gateway or a mesh node continuously and see if the connection is recovered. - -h3. Roaming from mesh to backbone - -!Test_roaming_mesh_LAN.dia.png! - -The client is connected to a mesh node first and then roams the backbone. - -Ping the internet gateway or a mesh node continuously and see if the connection is recovered. - -h3. A client switches its gateway (due to loss of link/better TQ) - -!Test_gateway_selection.dia.png! - -Continuously ping the internet gateway from the client, and change the quality of the currently selected node (e.g. adding packet loss). - -h3. Limited Horizon tests - -!Test_limited_horizon.dia.png! - -In this test, the first node A can't reach the last one C due to a limited horizon (the OGMs of A don't reach the OGMs of C and vice versa). - - * Test 1: Client 1 and Client 2 should be able to ping the internet gateway. There are are no bridge loops. - * Test 2: Client 1 and Client 2 should be able to ping each other. - -+note+: Test 2 can only be performed when the batman interface (or one of its VLANs) is used as a batman hard interface. The support for this requires are separate patch. - -h3. VLAN support - -The clients are connected to local VLANs which are used on top of BATMAN. All claim frames should then have a VLAN tag. - -h3. Two LANs connected by one mesh - -!Test_2xLAN.dia.png! - -Two LANs are connected by one mesh. The backbone gateways of each LAN should find each other and claim only packets from each LAN. -Every node should be able to reach every other node. - -h3. Two meshes connected by one LAN - -!Test_2xmesh.dia.png! - -Two meshes are connected to one LAN. The backbone gateways of each mesh should find themselves and share their claims, but should disregard claims for backbone gateways they are not part of (only possible with the backbone gateway grouping optimization) -Every node should be able to reach every other node. - -+note:+ this patch requires the group forming patch to be included. - -h2. Open Implementation issues - - * update README and sysfs description - * add support for soft interface OGM propagation - * test all test cases (so far, only basic tests and 2x mesh, 2x LAN) - * send to ml, add review points - h2. Further ideas
h3. from discussion on 2011-06-08: