[Olsr-dev] problem with olsr-0.5.6 branch: old links remain in the topology

L. Aaron Kaplan (spam-protected)
Tue Feb 3 00:21:38 CET 2009


I still found something in 0.5.6:

Same setup again: linksys ==, freebsd ==, openbsd ==
let them run, then kill openBSDs olsrd.

now the routing table on the linksys is fine:

(spam-protected):~# ifconfig eth1
[Install freifunk-openwrt-compat for /sbin/ifconfig]
+ exec ip addr show label eth1
3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc prio qlen 1000
     link/ether 00:0f:66:90:3f:57 brd ff:ff:ff:ff:ff:ff
     inet brd scope global eth1
(spam-protected):~# ip route show dev eth1  scope link  metric 1
213.XX.XX.0/24 dev vlan1  proto kernel  scope link  src 213.XX.XX.XX dev eth1  proto kernel  scope link  src dev br0  proto kernel  scope link  src
default via 213.XX.XX.1 dev vlan1

You see no route to .100.188 (openbsd) anymore .
But when you take a look at the freebsd node you will find that now  
with the patch
it actually does not have the route to openbsd anymore but nevertheless
the kernel routing table still contains that link (via the linksys)

--- 17:31:32.624001 -------------------------------------------------  

Source IP addr  Dest IP addr          LQ        ETX 1.000/0.925    1.080   0.925/1.000    1.080

(here it is gone from olsrd output / topology table)

[(spam-protected) ~]$ sudo netstat -rn
Routing tables

Destination        Gateway            Flags    Refs      Use  Netif  
default        UG          0        4    em0          UH          0       53    lo0   link#1             UC          0        0    em0    UGH         2        1    em0 =>
           very wrong and suspicious ;-) .100.188 is dead   link#1             UC          0        0    em0    00:23:6c:8d:58:c0  UHLW        1     8724    em0     
187      UGH         1        1    em0

the kernel routing table still holds this entry. And this entry  
remains forever, even though .100.188 is not reachable via .100.1  

I hope this sheds some light into the bug.
Let me know what I can test tomorrow.


More information about the Olsr-dev mailing list