Hi Tim,<br><br>Not sure if this is going to work, I'll try it when I get to work tomorrow though. But need to try the script first.<br><br>But here is the conclusion I have come to (maybe because of my own limited knowledge). I
dont think any other hack other than removing the default route is
going to work, since that is at the core of the issue. The default route
takes precedence so one will have to delete the default route.
<br><br>But since its been deleted, it needs to be added back so as to check if its working after some time and test the ping via the default route. If it works,
then great; if not, then it needs to be deleted again.<br><br>Its a
nasty hack, but thats the nature of routing unless and until we do
something else. I'm running out of ideas quite fast though and I
need to prototype this asap :-( .<br><br>Thanks,<br><span class="sg">Rajesh.</span><br><br><div><span class="gmail_quote">On 1/11/07, <b class="gmail_sendername">Tim Martin</b> <<a href="mailto:tmartin159@mchsi.com">
tmartin159@mchsi.com</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;">
<div bgcolor="#ffffff" text="#000000">
Here's a bad hack I was thinking of, but I use pfSense as my OLSR
dynamic gateway and I'm not sure if this is possible with your setup.<br>
<br>
Set node A to ping a specific address. On node B block any access to
that same address. So if node A goes out then the ping won't go
through node B and falsely announce node A as a working gateway. Of
course, do the same with a different ping address on node B which is
blocked by node A.<br>
<br>
Also, I think that if you can use pfSense <a href="http://www.pfsense.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">www.pfsense.com</a> you can set
it to have dual WANS and it has OLSR built into it. This might be a
better solution for your network.<br>
<br>
Tim<br>
<br>
<br>
Rajesh Narayanan wrote:
<blockquote cite="http://mid8e843e380701111432h9a0dfe6x2e3d59fc4f157f04@mail.gmail.com" type="cite"><div><span class="e" id="q_110143c5afed9ae4_1"><br>
<br>
<div><span class="gmail_quote">On 1/11/07, <b class="gmail_sendername">Bernd Petrovitsch</b> <<a href="mailto:bernd@firmix.at" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">bernd@firmix.at
</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;">On
Thu, 2007-01-11 at 12:25 -0800, Rajesh Narayanan wrote:<br>
> :-)<br>
><br>
> This is precisely the question that I have been myself thinking
since<br>
> yesterday. I thought of going back to routing fundamentals to see
if
<br>
> there is a good answer. So far I have not been able to think of<br>
<br>
Actually Andreas delivered the two possibilities in his answer. One is<br>
below and the other is: Take dedicated nodes for this.</blockquote>
<div><br>
************ sorry if im starting to sound silly :-), but I didnt
understand this one.<br>
</div>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> anything
except a 'not so clean hack' that would sound soemthing like
<br>
> this:<br>
><br>
> 1. Write a script to ping (dyn-gw already does this) on the default<br>
> WAN interface.<br>
> 2. If Pings succeed dont do anything<br>
> 3. If ping fails then delete the default route.
<br>
> - This is the part you were talking about. HOW DO I RECOVER??<br>
> - Since if I delete the route then the pings are not going out
of<br>
> this interface anyways.<br>
<br>
The other solution (see Andreas email) is to add (low priority) host
<br>
routes to known-outside ping targets - the ones which are used to decide<br>
if we have an uplink or not.</blockquote>
<div><br>
********** this does not help. The issue is with the static route
that gets added when the uplink is discovered. Once its discovered and
the static default route gets added, no amount of dancing with olsrd or
the dyn-gw parameters will be useful.<br>
<br>
</div>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">>
4. The hack is as follows:<br>
> - every 5 mins add the default route.
<br>
> - test ping through that interface<br>
> - if successful then leave it<br>
> - else, delete the default route again.<br>
><br>
> I know this is BAAAAAAAAAAAD, but all I want is that I should use
the
<br>
<br>
I (also) have some bad feelings about this:<br>
IMHO this is not very robust (e.g. what happens if olsrd exits somewhere<br>
in between - it could be a `kill -9` from the outside). Since OLSRD runs<br>
on embedded hardware, no user action can be expected (let alone
<br>
enforced) so it must work fully automatically (at least in theory we<br>
have o bugs in implementations;-).<br>
<br>
And I assume that OLSRD doesn't announce that link during the test.</blockquote>
<div><br>
********** I just want to prototype this to showcase a possible network
topology so a bad hack is hopefully ok for now. I realize there may be
better ways of doing it. But my coding skills are pretty rusty right
now so scripting is the best choice for me now :-)<br>
<br>
Thanks,<br>
Rajesh<br>
</div>
</div>
<br>
</span></div><pre><hr size="4" width="90%"><span class="q">
_______________________________________________<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>
<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>
</span></pre>
</blockquote>
<br>
<span class="q"><pre cols="72">-- <br><br>Stop Spam Now: <a href="http://www.spamarrest.com/affl?4025320" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.spamarrest.com/affl?4025320</a>
</pre>
</span></div>
<br>_______________________________________________<br>olsr-users mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:olsr-users@olsr.org">olsr-users@olsr.org</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="https://www.olsr.org/mailman/listinfo/olsr-users" target="_blank">
https://www.olsr.org/mailman/listinfo/olsr-users</a><br><br><br></blockquote></div><br>