Repository : ssh://git@open-mesh.org/doc
On branches: backup-redmine/2019-09-17,master
commit 958fb93cec9009b6f31048f289acad42c947e257 Author: Sven Eckelmann sven@narfation.org Date: Tue Sep 17 10:21:48 2019 +0000
doc: batman-adv/Bridge-loop-avoidance-Testcases
958fb93cec9009b6f31048f289acad42c947e257 batman-adv/Bridge-loop-avoidance-Testcases.textile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/batman-adv/Bridge-loop-avoidance-Testcases.textile b/batman-adv/Bridge-loop-avoidance-Testcases.textile index 8d01f6d..2edc8fb 100644 --- a/batman-adv/Bridge-loop-avoidance-Testcases.textile +++ b/batman-adv/Bridge-loop-avoidance-Testcases.textile @@ -33,8 +33,8 @@ h3. Limited Horizon tests
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. +* 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.
+note1+: Test 2 will only work if BATMAN runs over the backbone, e.g. by calling "batctl if add br0". +note2+: Limited horizon may be easily simulated by increasing the hop_penalty, e.g. "batctl meshif bat0 hop_penalty 230" will have a 3 hop range in a network without packet loss.