Battlemesh logo
  • Comments
  • Edit
  • Menu
    • Navigation
    • RecentChanges
    • FindPage
    • Local Site Map
    • Help
    • HelpContents
    • HelpOnMoinWikiSyntax
    • Display
    • Attachments
    • Info
    • Raw Text
    • Print View
    • Edit
    • Load
    • Save
    • Edit SideBar
  • Login

Navigation

  • RecentChanges
  • FindPage
  • PastEvents
  • ContactUs
  • HelpContents
Revision 1 as of 2012-02-29 22:08:03
  • BattleMeshV5
  • Tests

BattleMeshV5 Tests

Contents

  1. BattleMeshV5 Tests
    1. General Rules
    2. Tests
      1. The ZooBab Test
      2. Be Quick or Be Stable Test
      3. Convergence Time Test
        1. Part 1
        2. Part 2
      4. Don't Cross the Streams Test

General Rules

  • routing protocol configuration shall be the same for every test
  • routing protocols are tested in turn (i.e. not altogether)
  • cpu and memory consumption will be tracked during each test
  • no points, just results and a final analysis

Tests

The ZooBab Test

Be Quick or Be Stable Test

Convergence Time Test

To be performed on the whole mesh and repeated 3x for each protocol

Part 1

  1. traceroute from one end (node A) to the other (node B) of the mesh until the path is stable

  2. find a critical node N in the path so that

    1. has good quality links with its neighbors (possibly more than one)
    2. if shut down the network does not split
  3. start a ping from A to B

  4. turn off N

  5. count the number of pings from the first lost ping to the first subsequent successful ping

Part 2

  1. start a continuous traceroute (e.g. mtr) from node A to node B

  2. turn back on node N and start a stopwatch

  3. measure the time needed to get the node N (back) into the traceroute

Don't Cross the Streams Test

  • MoinMoin Powered
  • Python Powered
  • GPL licensed
  • Valid HTML 4.01