A collection of test scenarios. Execute run.py as user root in the sub folders to run the tests. The tests all expect the routing protocols to be installed. Otherwise modifiy the scripts. Be aware that the general execution time can take from 5 minutes up to some hours.
The tests will create a bunch of *.csv files with comma separated values. Use ./plot.sh to create image graphs. You will need the gnuplot program installed for that.
The mesh routing programs batman-adv and babel are used to estimate the amount of nodes the host system can simulate. A good starting point to see to what number of nodes to limit the other tests. Otherwise the system performance will dictate the results.
This test does not run no network or any routing protocol. It runs a theoretical setup to create data.
Test how long it takes for a routing daemon to route after start.
Assume that there is a small count of gateways/sinks in the network that many nodes want to use. Measures the traffic (overhead).
A dynamic test that pings random nodes while they all move around randomly at fixed speed and form new connections. Data for animations of node movements is also generated.
Similar to Mobility1, but the nodes move around at increasing speeds.
Test on topologies from the Freifunk data set with cable and WiFi connections. Measure connectivity and traffic.
Test connectivity on a simple satellite network.
Test connectivity and traffic on a more complex satellite network.
A more realistic test with packet loss and transmission delay.
Get the traffic per link that a routing protocol generates under minimal load on different network sizes and topologies.
Send a ping from each node towards a single sink and measure traffic.
Send a ping from a single sink node towards each other node and measure traffic.