[Olsr-users] Include all advertised IPs in the routing table

Michele Segata (spam-protected)
Fri Jan 20 16:54:10 CET 2017


Hi everyone,

I have a question regarding the configuration of OLSRv2 in a simple 
network. Consider the following network topology:

  .0.1      .1.1   .1.2     .2.1
0 ------------- 1 ------------- 2

The network is "flat", and all addresses belong to the 10.0.0.0/8 
network. We are trying some experiments using mininet and OLSRv2 with a 
very basic OLSR configuration which is the following:

[olsrv2]
       originator    -127.0.0.1/8
       originator    -::/0
       originator    default_accept
[interface]
       bindto        -127.0.0.1/8
       bindto        -::/0
       bindto        default_accept

The configuration is taken from the OLSR wiki to enable only IP4. In 
addition, each node enables OLSR on all its interfaces (but the 
loopback) using

[interface=<interface name>]

By running the mininet emulation, everything works almost as expected. 
After some seconds, the routing tables are populated. For example, this 
is the routing table for node 0

Kernel IP routing table
Destination  Gateway   Genmask         Flags Metric Iface
10.0.0.0     *         255.0.0.0       U     0      h0_0-eth1
10.0.1.1     10.0.1.1  255.255.255.255 UGH   2      h0_0-eth1
10.0.2.1     10.0.1.1  255.255.255.255 UGH   2      h0_0-eth1

and this is the routing table for node 2

Kernel IP routing table
Destination  Gateway   Genmask         Flags Metric Iface
10.0.0.0     *         255.0.0.0       U     0      h2_2-eth1
10.0.0.1     10.0.1.2  255.255.255.255 UGH   2      h2_2-eth1
10.0.1.1     10.0.1.2  255.255.255.255 UGH   2      h2_2-eth1

I said that everything is working "almost" as expected because I was 
expecting the routing tables of nodes 0 and 2 to include the IP address 
10.0.1.2/32 as a possible destination, but this does not happen.
I checked whether node 1 is including both IPs in its messages, and it 
does, so it seems like OLSR decides not to include that address in the 
routing table. The questions are:
1) why does this happen?
2) how can I tell OLSR to include all IPs when populating the routing 
tables?

Thanks in advance
Cheers,
Michele

-- 
Michele Segata, PhD
Department of Information Engineering and Computer Science
University of Trento, Italy
https://ans.disi.unitn.it/~segata



More information about the Olsr-users mailing list