[OLSR-users] Anyone tried two nodes with internet connection?

[Rajesh Narayanan]

Hi,

My apologies if I am repeating myself..

Some configuration on Node1.
The WAN (vlan1) interface is on the 10.33.176.0/24 network. And whether OLSR
is running or not, the default route is:

0.0.0.0         10.33.176.1     0.0.0.0         UG    0      0        0
vlan1
Now the HNA configuration in the olsrd.conf looks like
Hna4 {
        0.0.0.0         0.0.0.0
}

So when Node2 advertises itself as a route to reach the internet (it gets
added below the above route. Now even if the above route fails, it stays in
the route table and so the router forces all pings to go via this route
rather than the OLSR route.

Thanks,
Rajesh.

On 1/10/07, Rajesh Narayanan <(spam-protected)> wrote:
>
> Well, thats right and exactly the problem I am having.
> Even when the pings do not go through via the static route, the router
> does not route the pings via the route introduced by the OLSR. But when I
> manually remove the static route, the pings are successful.
>
> My question is that this process should be transparent to the user. I
> should not need to go remove the static route so that I can reach via the
> olsr route.
>
> Dont you think?
>
> Thanks,
> Rajesh.
>
> On 1/10/07, Sven-Ola Tuecke <(spam-protected)> wrote:
> >
> > Hi,
> >
> > this is easy. A linux / windows / macos [fill in] pc does not remove any
> > static default route just by wishing. You can distingush static routes
> > by
> > metric=0, whereas route introduced by olsrd always have metric>=1
> >
> > // Sven-Ola
> >
> > ""Rajesh Narayanan"" <(spam-protected)> schrieb im Newsbeitrag
> > news:(spam-protected) ...
> > Hi,
> >
> > Here are some more observations.
> >
> > In the network, the OLSR (on Node1) seems to behave correctly by
> > advertising
> > to Node2 that you cannot reach the internet via Node1 anymore. Doing a
> > 'route -n' on Node2 shows that it Node1's IP addres HAS been removed.
> >
> > Now the confusion is, if Node1 informs Node2 of it (Node1) not being a
> > route
> > to internet anymore, why does it not remove its own default internet
> > route???? Pings, traceroutes, linkstates, interface-states, seriously I
> > dont
> > think really matters. One can use whatever parameter they want. Just
> > make
> > sure the damn route does not exist in Node1 when it finds out that its
> > own
> > WAN interface cannot be used to reach the internet.
> >
> > Some suggestions:
> > 1. If using pings/traceroutes ensure that the packets are sent over the
> > WAN
> > interface of that node and if it fails then take appropriate action
> > (delete
> > it as the route in case pings or traceroute fails, keep it or add it if
> > it
> > succeeds)
> > 2. Link/Interface state (probably means the same thing) should also be
> > used,
> > as its an internally generated event and OLSR can be notified
> > immediately.
> > Take similar actions as above of deleting or adding the route
> > appropriatel
> >
> >
> > _______________________________________________
> > olsr-users mailing list
> > (spam-protected)
> > https://www.olsr.org/mailman/listinfo/olsr-users
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20070110/9976f37a/attachment.html>