Skip to content
No description, website, or topics provided.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
batman5_pkg
battlemesh-map
config-uap
config-wdr
firmware0.1
firmware0.2
firmware0.3
firmware0.3_controller
lede-config-wdr4300
old-launch
olsrv2_pkg
report
scripts
tests
.gitignore
LICENSE
README.asciidoc
controller
launch_new_protocol.sh
opkg_deploy
ping_testbed
pingall
reboot_testbed
routers
stop_routing
test1_data2cvs.sh
test1_ip_pairs.txt
test1_ip_pairs_generate.sh
test1_run.sh
test_ips
uap-pro
update_config_uap
update_config_wdr
update_wireless_wdr
wdr4300
wdr4300-1-4
wdr4300-batman

README.asciidoc

Reproducing battlemesh V10 like experiments

Define management and test network

Spread routers to create an interesting network topology for your tests, make sure you can reach all of them through the management network.

Note
For easier debugging have two separate testbeds: a big one "production" and a
small one for debugging. Everytime one protocol finds a bug or some extra
configuration are required, the devs will use the small one, without locking
the production one.
Note

Use cables at least for management network so it just works, Power-line could be useful too.

How to reproduce tests

  • Connect one of your interfaces to the management network

  • Verify you have proper connectivity to testbed nodes

  • For each routing protocol run the test ex: cd tests/failure_recovery/; ./test_iperf_fiveflows.sh OLSRv1

  • After the test fish parse the collected data ex: cd tests/failure_recovery/parser_scripts; ./parse_all_iperf_fiveflows.sh

  • Generate the grafs ex: cd tests/failure_recovery/gnuplot; gnuplot plot_iperf_fiveflows.gnuplot

  • Contemplate the beaty in tests/failure_recovery/graphs/

You can’t perform that action at this time.