BattleMeshV6 Tests

This page describes the planned tests for BattleMeshV6. For the actually performed tests, please see AcutalTests.

General Rules

Tests

Basic Stats

Be Quick or Be Stable Test

To be performed on a subset of the nodes.

 +----+
 | L1 |-----(A) : : : : : : (B)
 +----+      :       r1      |
             :               |
             :               |
             : r2            |
             :               |
             :               |       +----+
            (C)-------------(D)------| L2 |
                                     +----+

Steps

5x for each protocol

  1. perform a continuous traceroute (mtr or whatever) from L1 to L2
  2. load the network with UDP (iperf or whatever) from L1 to L2
  3. start a 11 minutes download from L2 to L1
  4. see how many times (if any) the route flaps in 11 minutes
  5. see if the routing protocol prefers the slow or the fast route

Goals

Check the stability of the routing protocol, and if the metric is effective.

References

The Channel Surfer Test

To be performed on a subset of the nodes.

 +----+
 | L1 |-----(A)
 +----+      :
           x :
             :       x
            (B) : : : : : : ( )     +----+
            ( ) : : : : : : (C)-----| L2 |
                     y              +----+

Steps

only 1x for each protocol

  1. perform a continuous traceroute (mtr or whatever) from L1 to L2
  2. load the network with TCP (iperf) from L1 to L2 for 21 minutes
  3. sleep until the end of the iperf stream
  4. see for which fraction of the time the routing protocol chooses the best route (L1->A->B->C->E->L2)

  5. see the amount of transferred bytes

Goal

See if the routing protocol prefers the channel-changing route, by design or by just because is the best path.

Convergence Time Test

To be performed on the whole mesh.

           .~.~.~.~.~.~.~.~.~.~.~.       
 +----+   (                       ) : (GW1)-+
 | L1 | :(                         )        |   
 +----+   (                       )         |   +----+
         (                         )        +---+ L2 |
          (                       )         |   +----+
         (                         )        |
          (                       ) : (GW2)-+
         (        MESH CLOUD       )     
          .~.~.~.~.~.~.~.~.~.~.~.~.

Steps

repeat 3x for each protocol

  1. traceroute from L1 to L2 and verify that the path goes through GW1

  2. start pinging from L1 to L2

  3. start a continuous traceroute (mtr or whatever) from L1 to L2

  4. turn off GW1

  5. count the number of pings from the first lost ping to the first subsequent successful ping
  6. after 2 minutes from its turning off, turn back on GW1 and start a stopwatch

  7. measure the time needed to the network to use GW1 again

Goal

Just convergence time.

Don't Cross the Streams Test

To be performed on the whole mesh

 +----+            .~.~.~.~.~.~.~.~.~.~.~.            +----+
 | L1 |-----(A) : (                       ) : (C)-----| L3 |
 +----+          (                         )          +----+
                  (                       )
                 (          MESH           )
                  (         CLOUD         )
 +----+          (                         )          +----+
 | L4 |-----(D) : (                       ) : (B)-----| L2 |
 +----+          (                         )          +----+
                  .~.~.~.~.~.~.~.~.~.~.~.~.

Steps

only 1x for each protocol

  1. start, at the same time:
    1. a 21 minutes TCP stream between L1 and L2
    2. a 21 minutes TCP stream between L3 and L4
  2. sleep for 21 minutes
  3. measure the total number of bytes transferred

Goal

See if the routing protocol can choose the paths for the two streams that maximizes throughput.

References

Contacts / Discussion

BattleMeshV6/PlannedTests (last edited 2014-05-14 15:51:25 by Clauz)