olsrv2 test: handling change in link quality

[Vigneswaran R]

Hello,

I am planning to test OLSRv2 to see how the change in link quality
affects the route calculation.

1. Any suggestion on simulating a degraded link (using tools such as
ethtool, iptables, tc etc)?

I am using qemu-kvm virtual machines with emulated e1000 NICs for
testing. I use iptables to introduce packet loss for testing. However, I
am not sure whether any better way to do this.

2. Below is the list of plugins currently being used (default ones) by
OLSRv2. Anything else to be enabled?

Static plugin: auto_ll4
Static plugin: cfg_compact
Static plugin: eth_listener
Static plugin: ff_dat_metric
Static plugin: layer2info
Static plugin: mpr
Static plugin: neighbor_probing
Static plugin: nhdpinfo
Static plugin: nl80211_listener
Static plugin: olsrv2info

Thank you.

vignesh

[Henning Rogge]

Post by Vigneswaran R
Hello,
I am planning to test OLSRv2 to see how the change in link quality affects
the route calculation.
1. Any suggestion on simulating a degraded link (using tools such as
ethtool, iptables, tc etc)?

The easiest way I found to simulate packet loss on a bridge is a
mixture of iptables (for dropping stuff with the statistic module) and
ebtables (for marking traffic depending on incoming/outgoing
interface).

I have a couple of scripts for this, maybe you want to have a look at them?

Post by Vigneswaran R
I am using qemu-kvm virtual machines with emulated e1000 NICs for testing. I
use iptables to introduce packet loss for testing. However, I am not sure
whether any better way to do this.
2. Below is the list of plugins currently being used (default ones) by
OLSRv2. Anything else to be enabled?
Static plugin: auto_ll4
Static plugin: cfg_compact
Static plugin: eth_listener
Static plugin: ff_dat_metric
Static plugin: layer2info
Static plugin: mpr
Static plugin: neighbor_probing
Static plugin: nhdpinfo
Static plugin: nl80211_listener
Static plugin: olsrv2info

...

After getting some new test data from emulation I would suggest
deactivating the MPR plugin until we get a good hysteresis mechanism
for it.

Henning

[Teco Boot]

I’m using CORE every now and then. Is is an easy to use GUI using standard Linux tools, like netem and network namespaces. There is also the EMANE wireless link emulator.
http://www.nrl.navy.mil/itd/ncs/products/core
http://www.nrl.navy.mil/itd/ncs/products/emane

For Ubuntu and Debian, you are up and running in seconds using "apt-get install core-network”.
Emane takes just a few more minutes.

It would be a nice goal to ship olsrv2 with CORE.

Teco

Post by Henning Rogge

Post by Vigneswaran R
Hello,
I am planning to test OLSRv2 to see how the change in link quality affects
the route calculation.
1. Any suggestion on simulating a degraded link (using tools such as
ethtool, iptables, tc etc)?

The easiest way I found to simulate packet loss on a bridge is a
mixture of iptables (for dropping stuff with the statistic module) and
ebtables (for marking traffic depending on incoming/outgoing
interface).
I have a couple of scripts for this, maybe you want to have a look at them?

Post by Vigneswaran R
I am using qemu-kvm virtual machines with emulated e1000 NICs for testing. I
use iptables to introduce packet loss for testing. However, I am not sure
whether any better way to do this.
2. Below is the list of plugins currently being used (default ones) by
OLSRv2. Anything else to be enabled?
Static plugin: auto_ll4
Static plugin: cfg_compact
Static plugin: eth_listener
Static plugin: ff_dat_metric
Static plugin: layer2info
Static plugin: mpr
Static plugin: neighbor_probing
Static plugin: nhdpinfo
Static plugin: nl80211_listener
Static plugin: olsrv2info

After getting some new test data from emulation I would suggest
deactivating the MPR plugin until we get a good hysteresis mechanism
for it.
Henning
--
Olsr-dev mailing list
https://lists.olsr.org/mailman/listinfo/olsr-dev

...

[Vigneswaran R]

Post by Teco Boot
I’m using CORE every now and then. Is is an easy to use GUI using standard Linux tools, like netem and network namespaces. There is also the EMANE wireless link emulator.
http://www.nrl.navy.mil/itd/ncs/products/core
http://www.nrl.navy.mil/itd/ncs/products/emane
For Ubuntu and Debian, you are up and running in seconds using "apt-get install core-network”.
Emane takes just a few more minutes.

Ok. I will explore them and get back. Thanks.


Vignesh

Post by Teco Boot
It would be a nice goal to ship olsrv2 with CORE.
Teco

Post by Henning Rogge

Post by Vigneswaran R
Hello,
I am planning to test OLSRv2 to see how the change in link quality affects
the route calculation.
1. Any suggestion on simulating a degraded link (using tools such as
ethtool, iptables, tc etc)?

The easiest way I found to simulate packet loss on a bridge is a
mixture of iptables (for dropping stuff with the statistic module) and
ebtables (for marking traffic depending on incoming/outgoing
interface).
I have a couple of scripts for this, maybe you want to have a look at them?

Post by Vigneswaran R
I am using qemu-kvm virtual machines with emulated e1000 NICs for testing. I
use iptables to introduce packet loss for testing. However, I am not sure
whether any better way to do this.
2. Below is the list of plugins currently being used (default ones) by
OLSRv2. Anything else to be enabled?
Static plugin: auto_ll4
Static plugin: cfg_compact
Static plugin: eth_listener
Static plugin: ff_dat_metric
Static plugin: layer2info
Static plugin: mpr
Static plugin: neighbor_probing
Static plugin: nhdpinfo
Static plugin: nl80211_listener
Static plugin: olsrv2info

After getting some new test data from emulation I would suggest
deactivating the MPR plugin until we get a good hysteresis mechanism
for it.
Henning
--
Olsr-dev mailing list
https://lists.olsr.org/mailman/listinfo/olsr-dev

...

[Vigneswaran R]

Post by Henning Rogge

Post by Vigneswaran R
Hello,
I am planning to test OLSRv2 to see how the change in link quality affects
the route calculation.
1. Any suggestion on simulating a degraded link (using tools such as
ethtool, iptables, tc etc)?

The easiest way I found to simulate packet loss on a bridge is a
mixture of iptables (for dropping stuff with the statistic module) and
ebtables (for marking traffic depending on incoming/outgoing
interface).
I have a couple of scripts for this, maybe you want to have a look at them?

...

Yes, please.

Post by Henning Rogge

Post by Vigneswaran R
I am using qemu-kvm virtual machines with emulated e1000 NICs for testing. I
use iptables to introduce packet loss for testing. However, I am not sure
whether any better way to do this.
2. Below is the list of plugins currently being used (default ones) by
OLSRv2. Anything else to be enabled?
Static plugin: auto_ll4
Static plugin: cfg_compact
Static plugin: eth_listener
Static plugin: ff_dat_metric
Static plugin: layer2info
Static plugin: mpr
Static plugin: neighbor_probing
Static plugin: nhdpinfo
Static plugin: nl80211_listener
Static plugin: olsrv2info

After getting some new test data from emulation I would suggest
deactivating the MPR plugin until we get a good hysteresis mechanism
for it.

...

Ok.

Vignesh

[Henning Rogge]

Post by Vigneswaran R

Post by Henning Rogge
I have a couple of scripts for this, maybe you want to have a look at them?

Yes, please.

My emulation environment is that I have three interfaces per virtual
machine for "wlan emulation", which have the names kvm{number}_a,
kvm{number}_b and kvm{number}_c, with {number} enumerating the VMs
starting with 1.

The file "route_basic.sh" is a bunch of helper functions, the file
"route_12_23.sh" is a simple example.

The bash functions calc_multicast_success_rate() and
calc_unicast_success_rate() allow you to calculate the transmission
success rate from on a distance, based on a Ricean Fading model we
fitted to measured data at our institute.

Henning Rogge

[vignesh]

Post by Henning Rogge

Post by Vigneswaran R

Post by Henning Rogge
I have a couple of scripts for this, maybe you want to have a look
at
them?

Yes, please.

My emulation environment is that I have three interfaces per virtual
machine for "wlan emulation", which have the names kvm{number}_a,
kvm{number}_b and kvm{number}_c, with {number} enumerating the VMs
starting with 1.
The file "route_basic.sh" is a bunch of helper functions, the file
"route_12_23.sh" is a simple example.
The bash functions calc_multicast_success_rate() and
calc_unicast_success_rate() allow you to calculate the transmission
success rate from on a distance, based on a Ricean Fading model we
fitted to measured data at our institute.

...

Thanks for the scripts. Let me try them out once I managed to set up
wlan emulation using CORE.

Vignesh

Post by Henning Rogge
Henning Rogge