<br>
<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">No problem (English is not my native language and perhaps I'm only silly<br>- or dumb - right now): You put two LinkSys (or PCs or whatever you
<br>have) running OLSRD as your "dedicated border routers" inbetween the<br>rest of the mesh network and your uplink. And these have - in the most<br>simple/extreme case - exactly two interfaces (these maybe "only"
<br>ethernet interfaces but anyone will do):<br>-) one to your uplink<br>-) one to the next OLSR router in the mesh network</blockquote><div><br>
yes the network is like shown below:<br>
<br>
<br>
<a href="http://10.33.176.1">10.33.176.1</a>
<a href="http://192.168.50.53">192.168.50.53</a>
<a href="http://192.168.50.54">192.168.50.54</a>
<a href="http://10.103.0.224">10.103.0.224</a><br>
UplinkA <------> Linksys(vodka3) < - - - - - - > LinksysB(vodka4)<----------->UplinkB<br>
linkA
linkB<br>
<br>
CONFIGURATION BEFORE ANYTHING IS STARTED<br>
--------------------------------------------------------------------------------<br>
VODKA3:<br>
Destination
Gateway
Genmask Flags Metric
Ref Use Iface<br>
<a href="http://10.33.176.0">10.33.176.0</a>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://255.255.255.0">255.255.255.0</a> U
0
0 0 vlan1<br>
<a href="http://192.168.50.0">192.168.50.0</a>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://255.255.255.0">255.255.255.0</a> U
0
0 0 eth1<br>
<a href="http://192.168.66.0">192.168.66.0</a>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://255.255.255.0">255.255.255.0</a> U
0
0 0 vlan0<br>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://10.33.176.1">10.33.176.1</a>
<a href="http://0.0.0.0">0.0.0.0</a>
UG 0
0 0 vlan1<br>
<br>
olsrd.conf (snippet):<br>
Hna4 {<br>
<a href="http://0.0.0.0">0.0.0.0</a> <a href="http://0.0.0.0">0.0.0.0</a><br>
}<br>
<br>
LoadPlugin "olsrd_dyn_gw.so.0.4"<br>
{<br>
PlParam
"Ping"
"<a href="http://10.193.244.15">10.193.244.15</a>" #this is reachable via VLAN1 or def gateway<br>
}<br>
<br>
VODKA4<br>
root@vodka4:~# route -n<br>
Kernel IP routing table<br>
Destination
Gateway
Genmask Flags Metric
Ref Use Iface<br>
<a href="http://192.168.50.0">192.168.50.0</a>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://255.255.255.0">255.255.255.0</a> U
0
0 0 eth1<br>
<a href="http://10.103.0.0">10.103.0.0</a>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://255.255.255.0">255.255.255.0</a> U
0
0 0 vlan1<br>
<a href="http://192.168.66.0">192.168.66.0</a>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://255.255.255.0">255.255.255.0</a> U
0
0 0 vlan0<br>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://10.103.0.224">10.103.0.224</a>
<a href="http://0.0.0.0">0.0.0.0</a>
UG 0
0 0 vlan1<br>
<br>
olsrd.conf (snippet):<br>
Hna4 {<br>
<a href="http://0.0.0.0">0.0.0.0</a> <a href="http://0.0.0.0">0.0.0.0</a><br>
}<br>
<br>
LoadPlugin "olsrd_dyn_gw.so.0.4"<br>
{<br>
PlParam "Ping" "<a href="http://10.103.0.224">10.103.0.224</a>"<br>
}<br>
<br>
<br>
ROUTE TABLES WHEN OLSRD STARTED ON VODKA3 and VODKA4<br>
---------------------------------------------------------------------------------------------------------<br>
VODKA3:<br>
root@vodka3:~# route -n<br>
Kernel IP routing table<br>
Destination
Gateway
Genmask Flags Metric
Ref Use Iface<br>
<a href="http://192.168.50.54">192.168.50.54</a>
<a href="http://0.0.0.0">0.0.0.0</a> <a href="http://255.255.255.255">255.255.255.255</a>
UH 1
0 0 eth1<br>
<a href="http://10.33.176.0">10.33.176.0</a>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://255.255.255.0">255.255.255.0</a> U
0
0 0 vlan1<br>
<a href="http://192.168.50.0">192.168.50.0</a>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://255.255.255.0">255.255.255.0</a> U
0
0 0 eth1<br>
<a href="http://192.168.66.0">192.168.66.0</a>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://255.255.255.0">255.255.255.0</a> U
0
0 0 vlan0<br>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://10.33.176.1">10.33.176.1</a>
<a href="http://0.0.0.0">0.0.0.0</a>
UG 0
0 0 vlan1 (#Def route)<br>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://192.168.50.54">192.168.50.54</a>
<a href="http://0.0.0.0">0.0.0.0</a>
UG 1
0 0 eth1 (#OLSR added route)<br>
<br>
<br>
VODKA4:<br>
root@vodka4:~# route -n<br>
Kernel IP routing table<br>
Destination
Gateway
Genmask Flags Metric
Ref Use Iface<br>
<a href="http://192.168.50.53">192.168.50.53</a>
<a href="http://0.0.0.0">0.0.0.0</a> <a href="http://255.255.255.255">255.255.255.255</a>
UH 1
0 0 eth1<br>
<a href="http://192.168.50.0">192.168.50.0</a>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://255.255.255.0">255.255.255.0</a> U
0
0 0 eth1<br>
<a href="http://10.103.0.0">10.103.0.0</a>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://255.255.255.0">255.255.255.0</a> U
0
0 0 vlan1<br>
<a href="http://192.168.66.0">192.168.66.0</a>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://255.255.255.0">255.255.255.0</a> U
0
0 0 vlan0<br>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://10.103.0.224">10.103.0.224</a>
<a href="http://0.0.0.0">0.0.0.0</a>
UG 0
0 0 vlan1 (#Def route)<br>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://192.168.50.53">192.168.50.53</a>
<a href="http://0.0.0.0">0.0.0.0</a>
UG 1
0 0 eth1 (#olsr added route)<br>
<br>
WHEN I PING <a href="http://GOOGLE.COM">GOOGLE.COM</a> FROM VODKA3<br>
---------------------------------------------------------------------<br>
VODKA3<br>
root@vodka3:~# ping <a href="http://www.google.com">www.google.com</a><br>
PING <a href="http://www.l.google.com">www.l.google.com</a> (<a href="http://72.14.221.103">72.14.221.103</a>): 56 data bytes<br>
64 bytes from <a href="http://72.14.221.103">72.14.221.103</a>: icmp_seq=0 ttl=238 time=176.2 ms<br>
64 bytes from <a href="http://72.14.221.103">72.14.221.103</a>: icmp_seq=1 ttl=238 time=169.7 ms<br>
64 bytes from <a href="http://72.14.221.103">72.14.221.103</a>: icmp_seq=2 ttl=238 time=170.8 ms<br>
64 bytes from <a href="http://72.14.221.103">72.14.221.103</a>: icmp_seq=3 ttl=238 time=171.3 ms<br>
64 bytes from <a href="http://72.14.221.103">72.14.221.103</a>: icmp_seq=4 ttl=238 time=169.5 ms<br>
64 bytes from <a href="http://72.14.221.103">72.14.221.103</a>: icmp_seq=5 ttl=238 time=170.6 ms<br>
<br>
VODKA4<br>
root@vodka4:~# ping <a href="http://www.google.com">www.google.com</a><br>
PING <a href="http://www.l.google.com">www.l.google.com</a> (<a href="http://66.102.7.99">66.102.7.99</a>): 56 data bytes<br>
64 bytes from <a href="http://66.102.7.99">66.102.7.99</a>: icmp_seq=0 ttl=248 time=10.8 ms<br>
64 bytes from <a href="http://66.102.7.99">66.102.7.99</a>: icmp_seq=1 ttl=248 time=10.8 ms<br>
64 bytes from <a href="http://66.102.7.99">66.102.7.99</a>: icmp_seq=2 ttl=248 time=10.6 ms<br>
64 bytes from <a href="http://66.102.7.99">66.102.7.99</a>: icmp_seq=3 ttl=248 time=10.7 ms<br>
64 bytes from <a href="http://66.102.7.99">66.102.7.99</a>: icmp_seq=4 ttl=248 time=11.1 ms<br>
64 bytes from <a href="http://66.102.7.99">66.102.7.99</a>: icmp_seq=5 ttl=248 time=15.8 ms<br>
<br>
<br>
ROUTE TABLES WHEN I REMOVE THE LINKA<br>
-----------------------------------------------------------------------<br>
VODKA3<br>
root@vodka3:~# route -n<br>
Kernel IP routing table<br>
Destination
Gateway
Genmask Flags Metric
Ref Use Iface<br>
<a href="http://192.168.50.54">192.168.50.54</a>
<a href="http://0.0.0.0">0.0.0.0</a> <a href="http://255.255.255.255">255.255.255.255</a>
UH 1
0 0 eth1<br>
<a href="http://10.33.176.0">10.33.176.0</a>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://255.255.255.0">255.255.255.0</a> U
0
0 0 vlan1<br>
<a href="http://192.168.50.0">192.168.50.0</a>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://255.255.255.0">255.255.255.0</a> U
0
0 0 eth1<br>
<a href="http://192.168.66.0">192.168.66.0</a>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://255.255.255.0">255.255.255.0</a> U
0
0 0 vlan0<br>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://10.33.176.1">10.33.176.1</a>
<a href="http://0.0.0.0">0.0.0.0</a>
UG 0
0 0 vlan1 (#Def route STILL
THERE!!)<br>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://192.168.50.54">192.168.50.54</a>
<a href="http://0.0.0.0">0.0.0.0</a>
UG 1
0 0 eth1<br>
<br>
VODKA4<br>
root@vodka4:~# route -n<br>
Kernel IP routing table<br>
Destination
Gateway
Genmask Flags Metric
Ref Use Iface<br>
<a href="http://192.168.50.53">192.168.50.53</a>
<a href="http://0.0.0.0">0.0.0.0</a> <a href="http://255.255.255.255">255.255.255.255</a>
UH 1
0 0 eth1<br>
<a href="http://192.168.50.0">192.168.50.0</a>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://255.255.255.0">255.255.255.0</a> U
0
0 0 eth1<br>
<a href="http://10.103.0.0">10.103.0.0</a>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://255.255.255.0">255.255.255.0</a> U
0
0 0 vlan1<br>
<a href="http://192.168.66.0">192.168.66.0</a>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://255.255.255.0">255.255.255.0</a> U
0
0 0 vlan0<br>
<a href="http://0.0.0.0">0.0.0.0</a>
<a href="http://10.103.0.224">10.103.0.224</a>
<a href="http://0.0.0.0">0.0.0.0</a>
UG 0
0 0 vlan1<br>
(#OLSR added route gets removed. correct behavior)<br>
<br>
BUT NOW IF I TRY TO PING <a href="http://GOOGLE.COM">GOOGLE.COM</a><br>
-------------------------------------------------------------------<br>
VODKA3<br>
root@vodka3:~# ping <a href="http://www.google.com">www.google.com</a> <br>
### No response (nameservice failure, im not running nameservice daemon
so it does not matter.. anyway, so i hit ctrl-c and tried pinging the
IP address instead.<br>
<br>
root@vodka3:~# ping <a href="http://72.14.221.103">72.14.221.103</a><br>
PING <a href="http://72.14.221.103">72.14.221.103</a> (<a href="http://72.14.221.103">72.14.221.103</a>): 56 data bytes<br>
<br>
--- <a href="http://72.14.221.103">72.14.221.103</a> ping statistics ---<br>
11 packets transmitted, 0 packets received, 100% packet loss<br>
<br>
VODKA4<br>
root@vodka4:~# ping <a href="http://www.google.com">www.google.com</a><br>
PING <a href="http://www.l.google.com">www.l.google.com</a> (<a href="http://66.102.7.99">66.102.7.99</a>): 56 data bytes<br>
64 bytes from <a href="http://66.102.7.99">66.102.7.99</a>: icmp_seq=0 ttl=248 time=13.5 ms<br>
64 bytes from <a href="http://66.102.7.99">66.102.7.99</a>: icmp_seq=1 ttl=248 time=14.4 ms<br>
64 bytes from <a href="http://66.102.7.99">66.102.7.99</a>: icmp_seq=2 ttl=248 time=11.2 ms<br>
64 bytes from <a href="http://66.102.7.99">66.102.7.99</a>: icmp_seq=3 ttl=248 time=11.1 ms<br>
64 bytes from <a href="http://66.102.7.99">66.102.7.99</a>: icmp_seq=4 ttl=248 time=23.3 ms<br>
<br>
<br>
ISSUE<br>
-----------<br>
Just as you stated below, the default route in Vodka3 should have been
removed by the olsrd dyn-gw plugin but it does not get removed.<br>
<br>
Thanks,<br>
Rajesh.<br>
<br>
<br>
<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">[...]<br>> The other solution (see Andreas email) is to add (low<br>> priority) host
<br>> routes to known-outside ping targets - the ones which are used<br>> to decide<br>> if we have an uplink or not.<br>><br>> ********** this does not help. The issue is with the static route
<br>> that gets added when the uplink is discovered. Once its discovered and<br>> the static default route gets added, no amount of dancing with olsrd<br>> or the dyn-gw parameters will be useful.<br><br>The low priority host routes are to be added statically and - thus - are
<br>not touched/chaned/removed by OLSRD.<br>So it should work like:<br>- Everything is up and running - the static low prio static host routes<br> and default route are in place. `ping checks` work (and no one cares<br>
which route is actually responsible).
<br>- The uplink fails because the ping's fail (e.g. someone pulls the<br> cable). OLSRDs dyn_gw plugin removes the default route. Naturally this<br> change propagates through the mesh network.<br>- If the cable is plugged in again, the ping's will work again since
<br> we have these static low prio static host routes. Via the dyn_gw<br> plugin we get a default route again which is also propagated through<br> OLSRD.<br>And the static low prio host routes do not interfere with the OLSR
<br>because OLSRD propagates only routes learned via OLSR or HNA-announcte<br>(or configured).<br>Or do I miss something?<br><br> Bernd<br>--<br>Firmix
Software
GmbH
<a href="http://www.firmix.at/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.firmix.at/</a><br>mobil: +43 664
4416156
fax: +43 1 7890849-55<br> Embedded Linux Development and Services<br><br><br>_______________________________________________<br>olsr-users mailing list<br><a href="mailto:olsr-users@olsr.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
olsr-users@olsr.org
</a><br><a href="https://www.olsr.org/mailman/listinfo/olsr-users" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">https://www.olsr.org/mailman/listinfo/olsr-users</a><br></blockquote></div><br>