[Olsr-users] OLSRD routing table problem.
Philip Hugg
(spam-protected)
Tue Oct 4 14:00:43 CEST 2011
Hello all,
I'm currently running olsrd on 3 nodes on an emulator (CoreEmu). The
nodes are labelled as N1(10.0.0.1), N11(10.0.0.11), and N21(10.0.0.21).
When I hit the start button on the emulator, the 3 nodes virtually start
at the same time in the order N1, N11, and N21. At this point the 3 nodes
converge to a 1-hop all informed network.
The problem I'm seeing is sometimes N21 ( and sometimes N11) has routing
table entry that is not consistent with it's olsr neighbor table.
Below is the output from n21 after it has converged and has stabilized
(about 5 minutes into the emulation).
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1-[(spam-protected) n21.conf]# echo all | nc localhost 2006
2-HTTP/1.0 200 OK
3-Content-type: text/plain
4-
5-Table: Links
6-Local IPRemote IPHyst.LQNLQCost
7-10.0.0.2110.0.0.10.000.0000.000INFINITE
8-10.0.0.2110.0.0.110.000.0000.000INFINITE
9-
10- Table: Neighbors
11- IP addressSYMMPRMPRSWill.2 Hop Neighbors
12- 10.0.0.11YESNONO31
13- 10.0.0.1YESNONO31
14-
15- Table: Topology
16- Dest. IPLast hop IPLQNLQCost
17- 10.0.0.1110.0.0.10.0390.0000.000
18- 10.0.0.2110.0.0.10.0040.5250.000
19- 10.0.0.110.0.0.110.0390.0000.000
20- 10.0.0.2110.0.0.110.0040.5250.000
21- 10.0.0.110.0.0.210.0000.0000.000
22- 10.0.0.1110.0.0.210.0000.0000.000
23-
24- Table: HNA
25- DestinationGateway
26-
27- Table: MID
28- IP addressAliases
29-
30- Table: Routes
31- DestinationGateway IPMetricETXInterface
32- 10.0.0.1/3210.0.0.110.000eth0
33- 10.0.0.11/3210.0.0.120.000eth0
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
As you can see from this output, the ETX extension is not running. I
don't need the ETX functionality since the Emulator's wireless is basic
on/off
(ON when in-range and OFF when out-of-range). Also, I need RFC
compliance at this time.
If you look at line 33 'Routes table', the entry indicates that
10.0.0.11 is reachable via 10.0.0.1 with a metric of 2.
However, if you look above at the Neighbors table (lines 12 and 13). The
neighbor 10.0.0.11 exists (line 12) and also
neighbor 10.0.0.1 is not an MPR for this node (line 13).
--->How can this be? <--
In my case, I restarted the emulation 5 times and this behaviour
occurred 3 times. Mostly happens on N21,
and sometimes N11 and N21 are affected, however N1 is always correct.
The olsrd version is 0.6.1. The settings in olsrd.conf for the 3 nodes are:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
LinkQualityLevel0
ClearScreenyes
TcRedundancy2
InterfaceDefaults {
Ip4Broadcast255.255.255.255
}
Interface "eth0"
{
HelloInterval 2.0
HelloValidityTime6.0
TcInterval5.0
TcValidityTime15.0
}
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Your help would be greatly appreciated!
Thanks,
Phil Hugg.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20111004/87d677c5/attachment.html>
More information about the Olsr-users
mailing list