[Olsr-users] route discovery perform not that well | loosing routes

Michael Rack (spam-protected)
Sun Oct 16 16:26:25 CEST 2011


Hi List!

I have a very strange problem i like to discuss with you.

My current setup:

(A) is a Router in Nürnberg
     * vpn = 192.168.0.1/32 brd 255.255.255.255
     HNA = 0.0.0.0/0

(B) is a Router in a other City and is connected to (A) via VPN
     * vpn = 192.168.1.1/32 brd 255.255.255.255
     * link1 = 192.168.1.1/32 brd 255.255.255.255
     * link3 = 192.168.1.1/32 brd 255.255.255.255
     * local = 192.168.1.1/24 brd 192.168.1.255
     HNA = 192.168.1.0/24

(C) is a Router that can see (B) and (D)
     * link1 = 192.168.2.1/32 brd 255.255.255.255
     * link2 = 192.168.2.1/32 brd 255.255.255.255
     * local = 192.168.2.1/24 brd 192.168.2.255
     HNA = 192.168.2.0/24

(D) is a Router that can see (B) and (C)
     * link2 = 192.168.3.1/32 brd 255.255.255.255
     * link3 = 192.168.3.1/32 brd 255.255.255.255
     * local = 192.168.3.1/24 brd 192.168.3.255
     HNA = 192.168.3.0/24

Graphical view:

                     /-- link1 -- (C)
                    /              |
(A) -- vpn -- (B) -             link2
                    \              |
                     \-- link3 -- (D)

the routing will work as expected. There is no problem. But sometimes 
when i manually take a link (link3 B <-> D) down for administrative 
reasons (iptables -A INPUT -i link3 -p udp --sport 698 -j DROP && 
iptables -A OUTPUT -o link3 -p udp --dport 698 -j DROP) then (A) is 
loosing the route to (D).

Node (D) reach all other nodes (B and C) and know about the 0.0.0.0/0 
HNA from (A), but (A) have no route back to (D). Remove the 
iptable-rules (A) get the route back to (D). Install the iptable-rule 
again, (A) is not able to reach (D). But (B) and (C) can reach (D) 
without problems.

I restarted OLSR on Node (D) and then the problem got bigger! (A) does 
not reach (D) anymore! After 15 Minutes without getting the route to (D) 
i restarted OLSR on Node (B) - after 5 seconds, the route to (D) was back!

I archived this behavior a few times, also on links that have no second 
link "A -> B -> C -> D" when C or D restarted the OLSRD process.

Does anyone know, whats the problem?

PS: i am running olsr v0.6.0.

Liebe Grüße aus Freilassing,

Michael Rack
RSM Freilassing
-- 
RSM Freilassing                 Tel.: +49 8654 607110
Nocksteinstr. 13                Fax.: +49 8654 670438
D-83395 Freilassing            www.rsm-freilassing.de

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: router-d.txt
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20111016/bde37b83/attachment.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: router-a.txt
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20111016/bde37b83/attachment-0001.txt>


More information about the Olsr-users mailing list