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

Sven-Ola Tuecke (spam-protected)
Wed Jan 10 19:25:57 CET 2007


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 

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
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 

More information about the Olsr-users mailing list