[Olsr-users] OLSR v0.5.6-r7 incompatible to v0.5.5 ??
Tue Dec 8 18:34:00 CET 2009
Now i have seen a total strange problem.
The route will discovered on "bond0". For 2 seconds, i can see the
correct routing descission on "bond0", but then it will be replaced by
The CORE-Router runs OLSR v0.5.5 with HNA 0.0.0.0/0 and act as a VPN-Server.
All machines are connected to the VPN on the CORE-Server, over a normal
DSL-Connection to route official routable IP-Addresses.
Few machines are cross-connected via wireless for wan-backup reasons, if
the DSL-Connection fails.
The machine is first propagate all routes via "bond0" and replace the
route informations after a few seconds with "lan".
The LAN-Interface needs 3 HOPS to reach the CORE-Server.
The BOND0-Interface reach CORE-Server without an HOP (1-HOP neighbour)
Anything goes very wrong here?
I don't use Hysterics, i don't use LinkQuality. Because, my machines are
always static and won't move.
Liebe Grüße aus Freilassing,
RSM Freilassing Tel.: +49 8654 607110
Nocksteinstr. 13 Fax.: +49 8654 670438
D-83395 Freilassing www.rsm-freilassing.de
Am 08.12.2009 18:16, schrieb Michael Rack:
> Dear list,
> i have lot of machines (x86, mipsel) that runs OLSR v0.5.5. Sometimes i
> have discovery problemes, after a machine has restarted. The routelookup
> need up to 30 minutes.
> Now i like to upgrade to OLSR v0.5.6-r7, but after starting OLSR, no
> route will discovered anymore.
> My Settings:
>> DebugLevel 0
>> IpVersion 4
>> FIBMetric "flat"
>> ClearScreen yes
>> xxx.xxx.14.112 255.255.255.240
>> 172.16.1.224 255.255.255.224
>> RtTable 100
>> RtTableDefault 253
>> AllowNoInt no
>> TosValue 16
>> Willingness 0
>> LinkQualityLevel 0
>> UseHysteresis no
>> Pollrate 0.05
>> NicChgsPollInt 3.0
>> TcRedundancy 2
>> MprCoverage 2
>> Interface "lan" "bond0"
>> HelloInterval 2.0
>> HelloValidityTime 6.0
>> TcInterval 5.0
>> TcValidityTime 15.0
>> MidInterval 5.0
>> MidValidityTime 15.0
>> HnaInterval 5.0
>> HnaValidityTime 15.0
>> Interface "bond0"
>> Ip4Broadcast 255.255.255.255
>> Interface "lan"
>> Ip4Broadcast xxx.xxx.14.127
> With v0.5.5, this configuration works as expected.
> In v0.5.6-r7 OLSR find only routes via "lan" but not via "bond0".
> "bond0" is a VPN-Interface over a DSL-Connection. The Broadcast is
> 255.255.255.255 because all VPN-Clients have only one host-address
> without Network-Address CDIR /32 to safe ip-addresses.
> On "tcpdump" i can see messages going through the VPN in and out.
> Can anyone tell me, what goes wrong here?
> Liebe Grüße aus Freilassing,
> Michael Rack
> RSM Freilassing
More information about the Olsr-users