Hi Andreas,<br><br>Thanks for the detail explanation again. I tried this:<br><br>Case 1:<br>------------<br>* Added a host route to a server thats on the uplink to NodeA <br>* Asked the dyn-gw config to ping that address.<br>
* Olsrd Configuration:<br><snip><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>"<br>}<br><br><snip><br><br>* Route config:<br>Destination Gateway Genmask Flags Metric Ref Use Iface<br><a href="http://10.193.244.15">
10.193.244.15</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 0 0 0 Vlan1<br>(no default routes.. i.e. no routes for <a href="http://0.0.0.0">
0.0.0.0</a>)<br><br>*** So here is the disparity. HNA says that <a href="http://0.0.0.0">0.0.0.0</a> can be reached through this node. While there is no route configuration for this route.<br>*** So if I start olsrd with the above configuration then I get this error
<br>HNA[00000000/00000000] is invalid<br>HNA[00000000/00000000] is invalid<br>HNA[00000000/00000000] is invalid<br>\<br><br>Case2:<br>----------<br>* Now say I add a <a href="http://0.0.0.0">0.0.0.0</a> route so that route table looks like:
<br>Destination Gateway Genmask Flags Metric Ref Use Iface<br>
<a href="http://10.193.244.15">10.193.244.15</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 0 0 0 Vlan1<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> <a href="http://0.0.0.0">0.0.0.0</a> U 0 0 0 Vlan1<br><br>* And change the olsrd.conf to<br><snip>
<br>
Hna4 {<br>## Removed <a href="http://0.0.0.0">0.0.0.0</a> <a href="http://0.0.0.0">0.0.0.0</a> from here.<br>
}<br>
<br>
LoadPlugin "olsrd_dyn_gw.so.0.4"<br>
{<br>
PlParam "HNA" "<a href="http://0.0.0.0">0.0.0.0</a>"<br>
PlParam "Ping" "<a href="http://10.193.244.15">10.193.244.15</a>"<br>
}<br><br>OLSRD fails as i get the error:<br>Fatal error in pligin parameter "HNA"/"<a href="http://0.0.0.0">0.0.0.0</a>"<br>(This happens whether i have the <a href="http://0.0.0.0">0.0.0.0</a> in the route table or not)
<br><br>Conclusion:<br>-----------------<br>Suggestion of having a host route fails. Maybe due to a bug in the olsr code.<br><br>Please advice.<br>Thanks,<br>Rajesh.<br><br><br>
<br><br><br><div><span class="gmail_quote">On 1/12/07, <b class="gmail_sendername">Andreas Tønnesen</b> <<a href="mailto:andreto@olsr.org">andreto@olsr.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Rajesh Narayanan wrote:<br>> But here is the conclusion I have come to (maybe because of my own<br>> limited knowledge). I dont think any other hack other than removing<br>> the default route is going to work, since that is at the core of the
<br>> issue. The default route takes precedence so one will have to delete<br>> the default route.<br>><br>> But since its been deleted, it needs to be added back so as to check<br>> if its working after some time and test the ping via the default
<br>> route. If it works, then great; if not, then it needs to be deleted again.<br><br>I don't think you understood Bernds explanation. The idea is:<br>- Set up a static _host_ route to the ping destination trough the uplink
<br>interface.<br>- Now let dyn_gw dynamically add/remote the default route based on the<br>pings.<br>- The pings will _always_ be routed through the host route so there is<br>no need<br>for any hacks(like re-adding the default route or doing some sort of
<br>IP-routing bypass).<br><br>It should give you just what you want.<br><br><br>My other option(which Bernd also explained) is to have _dedicated_<br>gateways. That means<br>you have gateways that _only_ act as gateways. That means they do not
<br>themselves depend<br>on Internet connectivity. This is what the plugin was originally created<br>for. The boxes<br>that ran this plugin were pure gateways dedicated to providing Internet<br>access and if they<br>lost their link they should stop announcing themselves as a GW and just
<br>wait to recover.<br>The node it self never needs to have a "backup" Internet route trough<br>the olsrd domain<br>since it's ONLY purpose is to serve Internet connectivity not to connect<br>to Internet<br>
themselves.<br><br>- Andreas<br><br>_______________________________________________<br>olsr-users mailing list<br><a href="mailto:olsr-users@olsr.org">olsr-users@olsr.org</a><br><a href="https://www.olsr.org/mailman/listinfo/olsr-users">
https://www.olsr.org/mailman/listinfo/olsr-users</a><br></blockquote></div><br>