[Olsr-users] Where am I going wrong in the settings.

[Teco Boot]

If you have a static default route via an interface, and that interface goes down, the route should be removed from routing table.

The ping function in dyn-gw is for connectivity problems while local interface is still up. 

Please provide logging from following commands:

ip route show table all dev eth1
ip route show table all | grep default
ping -c 2 -w 4 8.8.8.8

ifconfig eth1 down
ip route show table all dev eth1
ip route show table all | grep default
ping -c 2 -w 4 8.8.8.8

ifconfig eth1 up
ip route show table all dev eth1
ip route show table all | grep default
ping -c 2 -w 4 8.8.8.8

Change 8.8.8.8 to 10.4.0.1 if you are not connected to internet.

Teco


Op 8 apr. 2014, om 23:35 heeft ANDERSON JUNIOR GADO DA SILVA <(spam-protected)> het volgende geschreven:

> hello, I tried changing the order and also removing "HNA" "0.0.0.0 0.0.0.0", but none of the forms solved the problem of the route, I believe I know what the problem is, the network adapter configured with static wan this address then believe that this default route configured the olsr not remove it because it was not he who created it, why looking at the behavior of the route table, even if the route 172.16.0.1 is not over with the cable she keeps it in route table, olsr adds a new route that is 10.5.0.6, I think the first 172.16.0.1 prevails over the others, if u wants to access my small network I fix a computer with remote access for you to look at settings of radios.
> 
> Att
> Anderson Junior
> 
> 
> 2014-04-08 16:59 GMT-04:00 Teco Boot <(spam-protected)>:
> The plugin parameters are ordered, at least for dyn_gw.
> Read from bottom to top.
> Your config reads first "HNA" "0.0.0.0 0.0.0.0", no ping test set.
> Then the "Ping" "10.4.0.1", but no HNA for it.
> 
> Please test with:
> 
> LoadPlugin "olsrd_dyn_gw.so.0.5"
> {
>         PlParam "HNA" "0.0.0.0 0.0.0.0"
>         PlParam "Ping" "10.4.0.1"
>         PlParam "CheckInterval" "5000"
>         PlParam "PingInterval" "5"
> }
> 
> 
> When no HNA parameter is provided, "HNA" "0.0.0.0 0.0.0.0” is assumed (not tested by me!).
> 
> Teco
> 
> 
> Op 8 apr. 2014, om 22:47 heeft ANDERSON JUNIOR GADO DA SILVA <(spam-protected)> het volgende geschreven:
> 
> > I understand WHAT you explained to me, since I made the change as suggested Teco, thus:
> >
> > LoadPlugin "olsrd_dyn_gw.so.0.5"
> > {
> >         PlParam "Ping" "10.4.0.1"
> >         PlParam "HNA" "0.0.0.0 0.0.0.0"
> >         PlParam "CheckInterval" "5000"
> >         PlParam "PingInterval" "5"
> > }
> >
> > 10.4.0.1 is a local dns server, so I continued using it as a reference for the ping,
> >
> > this correct?
> >
> > Att
> > Anderson Junior
> >
> >
> > 2014-04-08 16:34 GMT-04:00 Henning Rogge <(spam-protected)>:
> > On Tue, Apr 8, 2014 at 10:27 PM, ANDERSON JUNIOR GADO DA SILVA
> > <(spam-protected)> wrote:
> > > I'll try to explain with my words, ping the address must be a reachable
> > > address outside the network, preferably the Internet, a known site or dns,
> > > it ensures that the node has internet, HNA understand to be the network
> > > where the olsr will flood with your posts, this would be the network where
> > > the working olsr. If you are traveling to pull my ear, (laughs).
> >
> > A HNA announces a prefix outside the OLSR mesh network. In fact it
> > announces that the local node can reach this prefix, the HNA allows
> > the other nodes to access this prefix through the local node.
> >
> > The ping mechanism of the dyn_gw plugin checks the bi-directional
> > connectivity to a host within this prefix.
> >
> > If you are re-distributing a route to the internet, the prefix would
> > be 0.0.0.0/0 (the default route) and the ping address would be a host
> > on the internet (e.g. 8.8.8.8, the google dns).
> >
> > Henning
> >
> >
> >
> 
> 
> 
>