<div dir="ltr">hello, I had already taken the test in 3 client (node without internet link) node and it does not change its route to node 2 gw (node that has the true route), it just makes the change if I restart the service ( / etc / init.d / olsrd restart) or if I turn off the power node 1 gw, al then it changes its route to node 2 gw.<br>
<br>I did not understand this question:<br>Can someone jump in here?<br><br><br>Att<br>Anderson Junior<br><div class="gmail_extra"><br><br><div class="gmail_quote">2014-04-10 10:30 GMT-04:00 Teco Boot <span dir="ltr"><<a href="mailto:teco@inf-net.nl" target="_blank">teco@inf-net.nl</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">OK, now we know the limitation. Your Linux IP stack does not remove routes to an interface that is up but not running.<br>
Can someone jump in here?<br>
<br>
The dyn_gw with ping check should avoid advertisement of a black hole in the OLSR network. Please verify that on node without the Internet link, it switches the default route to the router with internet link that does work. Test with multiple connections, e.g. another ping command. Because NAT, firewall, switched ISP / ISP links, connections would not survive the hand-over.<br>
On the failing node, with false default gateway, there is a local problem. Hard to circumvent (although we have plans for improvements).<br>
<br>
Teco<br>
<br>
<br>
Op 10 apr. 2014, om 01:00 heeft ANDERSON JUNIOR GADO DA SILVA <<a href="mailto:andersonscinfo@gmail.com">andersonscinfo@gmail.com</a>> het volgende geschreven:<br>
<div class="HOEnZb"><div class="h5"><br>
> hello, I do not know if I'm able to explain clearly, even if I understand correctly WHAT are you talking about, because I'm using google translator, but let it down the return of ifconfig eth1, with the cable connected and disconnected:<br>
><br>
> connected:<br>
><br>
> ifconfig eth1<br>
> eth1 Link encap:Ethernet HWaddr C0:4A:00:50:0C:3D<br>
> inet addr:172.16.0.3 Bcast:172.16.0.255 Mask:255.255.255.0<br>
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br>
> RX packets:720 errors:0 dropped:140 overruns:0 frame:0<br>
> TX packets:193 errors:0 dropped:0 overruns:0 carrier:0<br>
> collisions:0 txqueuelen:1000<br>
> RX bytes:114567 (111.8 KiB) TX bytes:17842 (17.4 KiB)<br>
> Interrupt:4<br>
><br>
><br>
><br>
> disconnected:<br>
><br>
> ifconfig eth1<br>
> eth1 Link encap:Ethernet HWaddr C0:4A:00:50:0C:3D<br>
> inet addr:172.16.0.3 Bcast:172.16.0.255 Mask:255.255.255.0<br>
> UP BROADCAST MULTICAST MTU:1500 Metric:1<br>
> RX packets:840 errors:0 dropped:163 overruns:0 frame:0<br>
> TX packets:212 errors:0 dropped:0 overruns:0 carrier:0<br>
> collisions:0 txqueuelen:1000<br>
> RX bytes:136368 (133.1 KiB) TX bytes:19496 (19.0 KiB)<br>
> Interrupt:4<br>
><br>
> After bringing eth1 down, the routes for that interface stays there for a long time?<br>
><br>
> R: no, they disappear quickly and the route 10.5.0.6 defaults if I use ifconfig eth1 down in at most 5/2 works normally, I believe that "ifconfig eth1 down" removes the default route 172.16.0.1<br>
><br>
><br>
> I don’t understand why OLSR puts the default, while there is the default entry with lower metric. Does it disappear after a minute or so?<br>
><br>
> no, it does not disappear, it is both as standard, when both 172.16.0.1 10.5.0.6, but if I get down ifconfig eth1 172.16.0.1 then quickly disappears.<br>
><br>
> if you wants to access the routers remotely or if I want to see more configuration files just let me know.<br>
><br>
> Att<br>
> Anderson Junior<br>
><br>
> 2014-04-09 16:05 GMT-04:00 Teco Boot <<a href="mailto:teco@inf-net.nl">teco@inf-net.nl</a>>:<br>
> I see same minor issue as what I have seen before. The list with HNA entries doesn’t show all <a href="http://0.0.0.0/0" target="_blank">0.0.0.0/0</a> routes, right?<br>
> In first HNA listing, the <a href="http://0.0.0.0/0" target="_blank">0.0.0.0/0</a> comes from 10.5.0.5, this is the own entry. Maybe use smart gateway, then you see more info. And it might work better for you.<br>
><br>
> After bringing eth1 down, the routes for that interface stays there for a long time? Really sure? Then, your ethernet NIC driver has a bug and the down condition is not detected. Please verify with ifconfig eth1, it should stop display Running.<br>
> Please report ifconfig eth1 output, with cable connected and disconnected.<br>
><br>
> I don’t understand why OLSR puts the default, while there is the default entry with lower metric. Does it disappear after a minute or so?<br>
><br>
> Teco<br>
><br>
><br>
><br>
> Op 9 apr. 2014, om 19:06 heeft ANDERSON JUNIOR GADO DA SILVA <<a href="mailto:andersonscinfo@gmail.com">andersonscinfo@gmail.com</a>> het volgende geschreven:<br>
><br>
> > hello, I send only 1 node gw, which is where I believe is the problem, before and after the removal of the cable, but I will not give a ifconfig eth1 down<br>
> ><br>
> > before:<br>
> > route<br>
> > Kernel IP routing table<br>
> > Destination Gateway Genmask Flags Metric Ref Use Iface<br>
> > default 172.16.0.1 0.0.0.0 UG 0 0 0 eth1<br>
> > 10.5.0.0 * 255.255.0.0 U 0 0 0 wlan0<br>
> > 10.5.0.4 10.5.0.4 255.255.255.255 UGH 2 0 0 wlan0<br>
> > 10.5.0.6 10.5.0.6 255.255.255.255 UGH 2 0 0 wlan0<br>
> > 172.16.0.0 * 255.255.255.0 U 0 0 0 eth1<br>
> ><br>
> > ====================================================<br>
> > echo '/all' | nc localhost 2006<br>
> > HTTP/1.0 200 OK<br>
> > Content-type: text/plain<br>
> ><br>
> > Table: Links<br>
> > Local IP Remote IP Hyst. LQ NLQ Cost<br>
> > 10.5.0.5 10.5.0.6 0.00 1.000 1.000 1.000<br>
> > 10.5.0.5 10.5.0.4 0.00 1.000 1.000 1.000<br>
> ><br>
> > Table: Neighbors<br>
> > IP address SYM MPR MPRS Will. 2 Hop Neighbors<br>
> > 10.5.0.4 YES NO NO 3 1<br>
> > 10.5.0.6 YES NO NO 3 1<br>
> ><br>
> > Table: Topology<br>
> > Dest. IP Last hop IP LQ NLQ Cost<br>
> > 10.5.0.5 10.5.0.4 1.000 1.000 1.000<br>
> > 10.5.0.6 10.5.0.4 1.000 1.000 1.000<br>
> > 10.5.0.4 10.5.0.5 1.000 1.000 1.000<br>
> > 10.5.0.6 10.5.0.5 1.000 1.000 1.000<br>
> > 10.5.0.4 10.5.0.6 1.000 1.000 1.000<br>
> > 10.5.0.5 10.5.0.6 1.000 1.000 1.000<br>
> ><br>
> > Table: HNA<br>
> > Destination Gateway<br>
> > <a href="http://0.0.0.0/0" target="_blank">0.0.0.0/0</a> 10.5.0.5<br>
> ><br>
> > Table: MID<br>
> > IP address Aliases<br>
> ><br>
> > Table: Routes<br>
> > Destination Gateway IP Metric ETX Interface<br>
> > <a href="http://10.5.0.4/32" target="_blank">10.5.0.4/32</a> 10.5.0.4 1 1.000 wlan0<br>
> > <a href="http://10.5.0.6/32" target="_blank">10.5.0.6/32</a> 10.5.0.6 1 1.000 wlan0<br>
> ><br>
> ><br>
> ><br>
> > after taking the cable:<br>
> > you may notice that it added another default route 10.5.0.6, 172.16.0.1 but not removed this no longer working, and that's where I think that the problem<br>
> ><br>
> > route<br>
> > Kernel IP routing table<br>
> > Destination Gateway Genmask Flags Metric Ref Use Iface<br>
> > default 172.16.0.1 0.0.0.0 UG 0 0 0 eth1<br>
> > default 10.5.0.6 0.0.0.0 UG 2 0 0 wlan0<br>
> > 10.5.0.0 * 255.255.0.0 U 0 0 0 wlan0<br>
> > 10.5.0.4 10.5.0.4 255.255.255.255 UGH 2 0 0 wlan0<br>
> > 10.5.0.6 10.5.0.6 255.255.255.255 UGH 2 0 0 wlan0<br>
> > 172.16.0.0 * 255.255.255.0 U 0 0 0 eth1<br>
> ><br>
> > ======================================================<br>
> > echo '/all' | nc localhost 2006<br>
> > HTTP/1.0 200 OK<br>
> > Content-type: text/plain<br>
> ><br>
> > Table: Links<br>
> > Local IP Remote IP Hyst. LQ NLQ Cost<br>
> > 10.5.0.5 10.5.0.6 0.00 1.000 1.000 1.000<br>
> > 10.5.0.5 10.5.0.4 0.00 1.000 1.000 1.000<br>
> ><br>
> > Table: Neighbors<br>
> > IP address SYM MPR MPRS Will. 2 Hop Neighbors<br>
> > 10.5.0.4 YES NO NO 3 1<br>
> > 10.5.0.6 YES NO NO 3 1<br>
> ><br>
> > Table: Topology<br>
> > Dest. IP Last hop IP LQ NLQ Cost<br>
> > 10.5.0.5 10.5.0.4 1.000 1.000 1.000<br>
> > 10.5.0.6 10.5.0.4 1.000 1.000 1.000<br>
> > 10.5.0.4 10.5.0.5 1.000 1.000 1.000<br>
> > 10.5.0.6 10.5.0.5 1.000 1.000 1.000<br>
> > 10.5.0.4 10.5.0.6 1.000 1.000 1.000<br>
> > 10.5.0.5 10.5.0.6 1.000 1.000 1.000<br>
> ><br>
> > Table: HNA<br>
> > Destination Gateway<br>
> > <a href="http://0.0.0.0/0" target="_blank">0.0.0.0/0</a> 10.5.0.6<br>
> ><br>
> > Table: MID<br>
> > IP address Aliases<br>
> ><br>
> > Table: Routes<br>
> > Destination Gateway IP Metric ETX Interface<br>
> > <a href="http://0.0.0.0/0" target="_blank">0.0.0.0/0</a> 10.5.0.6 1 1.000 wlan0<br>
> > <a href="http://10.5.0.4/32" target="_blank">10.5.0.4/32</a> 10.5.0.4 1 1.000 wlan0<br>
> > <a href="http://10.5.0.6/32" target="_blank">10.5.0.6/32</a> 10.5.0.6 1 1.000 wlan0<br>
> ><br>
> ><br>
> > Now before ifconfig eth1 down:<br>
> > route<br>
> > Kernel IP routing table<br>
> > Destination Gateway Genmask Flags Metric Ref Use Iface<br>
> > default 172.16.0.1 0.0.0.0 UG 0 0 0 eth1<br>
> > 10.5.0.0 * 255.255.0.0 U 0 0 0 wlan0<br>
> > 10.5.0.4 10.5.0.6 255.255.255.255 UGH 2 0 0 wlan0<br>
> > 10.5.0.6 10.5.0.6 255.255.255.255 UGH 2 0 0 wlan0<br>
> > 172.16.0.0 * 255.255.255.0 U 0 0 0 eth1<br>
> ><br>
> > =====================================================<br>
> ><br>
> > echo '/all' | nc localhost 2006<br>
> > HTTP/1.0 200 OK<br>
> > Content-type: text/plain<br>
> ><br>
> > Table: Links<br>
> > Local IP Remote IP Hyst. LQ NLQ Cost<br>
> > 10.5.0.5 10.5.0.6 0.00 1.000 1.000 1.000<br>
> > 10.5.0.5 10.5.0.4 0.00 1.000 1.000 1.000<br>
> ><br>
> > Table: Neighbors<br>
> > IP address SYM MPR MPRS Will. 2 Hop Neighbors<br>
> > 10.5.0.4 YES NO NO 3 1<br>
> > 10.5.0.6 YES NO NO 3 1<br>
> ><br>
> > Table: Topology<br>
> > Dest. IP Last hop IP LQ NLQ Cost<br>
> > 10.5.0.5 10.5.0.4 1.000 1.000 1.000<br>
> > 10.5.0.6 10.5.0.4 1.000 1.000 1.000<br>
> > 10.5.0.4 10.5.0.5 1.000 1.000 1.000<br>
> > 10.5.0.6 10.5.0.5 1.000 1.000 1.000<br>
> > 10.5.0.4 10.5.0.6 1.000 1.000 1.000<br>
> > 10.5.0.5 10.5.0.6 1.000 1.000 1.000<br>
> ><br>
> > Table: HNA<br>
> > Destination Gateway<br>
> > <a href="http://0.0.0.0/0" target="_blank">0.0.0.0/0</a> 10.5.0.5<br>
> ><br>
> > Table: MID<br>
> > IP address Aliases<br>
> ><br>
> > Table: Routes<br>
> > Destination Gateway IP Metric ETX Interface<br>
> > <a href="http://10.5.0.4/32" target="_blank">10.5.0.4/32</a> 10.5.0.4 1 1.000 wlan0<br>
> > <a href="http://10.5.0.6/32" target="_blank">10.5.0.6/32</a> 10.5.0.6 1 1.000 wlan0<br>
> ><br>
> ><br>
> ><br>
> > after:<br>
> ><br>
> > ifconfig eth1 down<br>
> > route<br>
> > Kernel IP routing table<br>
> > Destination Gateway Genmask Flags Metric Ref Use Iface<br>
> > default 10.5.0.6 0.0.0.0 UG 2 0 0 wlan0<br>
> > 10.5.0.0 * 255.255.0.0 U 0 0 0 wlan0<br>
> > 10.5.0.4 10.5.0.4 255.255.255.255 UGH 2 0 0 wlan0<br>
> > 10.5.0.6 10.5.0.6 255.255.255.255 UGH 2 0 0 wlan0<br>
> ><br>
> > ======================================<br>
> > echo '/all' | nc localhost 2006<br>
> > HTTP/1.0 200 OK<br>
> > Content-type: text/plain<br>
> ><br>
> > Table: Links<br>
> > Local IP Remote IP Hyst. LQ NLQ Cost<br>
> > 10.5.0.5 10.5.0.6 0.00 1.000 1.000 1.000<br>
> > 10.5.0.5 10.5.0.4 0.00 1.000 1.000 1.000<br>
> ><br>
> > Table: Neighbors<br>
> > IP address SYM MPR MPRS Will. 2 Hop Neighbors<br>
> > 10.5.0.4 YES NO NO 3 1<br>
> > 10.5.0.6 YES NO NO 3 1<br>
> ><br>
> > Table: Topology<br>
> > Dest. IP Last hop IP LQ NLQ Cost<br>
> > 10.5.0.5 10.5.0.4 1.000 1.000 1.000<br>
> > 10.5.0.6 10.5.0.4 1.000 1.000 1.000<br>
> > 10.5.0.4 10.5.0.5 1.000 1.000 1.000<br>
> > 10.5.0.6 10.5.0.5 1.000 1.000 1.000<br>
> > 10.5.0.4 10.5.0.6 1.000 1.000 1.000<br>
> > 10.5.0.5 10.5.0.6 1.000 1.000 1.000<br>
> ><br>
> > Table: HNA<br>
> > Destination Gateway<br>
> > <a href="http://0.0.0.0/0" target="_blank">0.0.0.0/0</a> 10.5.0.6<br>
> ><br>
> > Table: MID<br>
> > IP address Aliases<br>
> ><br>
> > Table: Routes<br>
> > Destination Gateway IP Metric ETX Interface<br>
> > <a href="http://0.0.0.0/0" target="_blank">0.0.0.0/0</a> 10.5.0.6 1 1.000 wlan0<br>
> > <a href="http://10.5.0.4/32" target="_blank">10.5.0.4/32</a> 10.5.0.4 1 1.000 wlan0<br>
> > <a href="http://10.5.0.6/32" target="_blank">10.5.0.6/32</a> 10.5.0.6 1 1.000 wlan0<br>
> ><br>
> > ==========================================<br>
> ><br>
> ><br>
> > Now you can see that he removed the 172.16.0.1, al worked out, I think it should work without giving a down on eth1, because he should understand when the gw 172.16.0.1 (eth1) back to work and pick it up as the better as it is directly on the cable.<br>
> ><br>
> > Att<br>
> > Anderson Junior<br>
> ><br>
> > 2014-04-09 11:12 GMT-03:00 Teco Boot <<a href="mailto:teco@inf-net.nl">teco@inf-net.nl</a>>:<br>
> > No, it doesn’t matter how the default route is provided.<br>
> > If static, after an ifconfig eth1 up, you should reinstall the route again.<br>
> ><br>
> > I am a bit lost on the status. I guess dyn_gw is working, right?<br>
> > If not, please provide fresh config and status as you sent before.<br>
> ><br>
> > Teco<br>
> ><br>
> ><br>
> > Op 9 apr. 2014, om 14:21 heeft ANDERSON JUNIOR GADO DA SILVA <<a href="mailto:andersonscinfo@gmail.com">andersonscinfo@gmail.com</a>> het volgende geschreven:<br>
> ><br>
> > > hello again, one thing I noticed was that the nodes gw, when I give the command:<br>
> > ><br>
> > > ifconfig eth1 down<br>
> > ><br>
> > > it works properly, at 5 pings at most the route works correctly, so I think the problem is because it is using static ip instead of dhcp on eth1 (wan), because when I give the command to down on eth1 it removes the route default 172.16.0.1<br>
> > ><br>
> > > Att<br>
> > > Anderson Junior<br>
> > ><br>
> > ><br>
> > > 2014-04-09 7:31 GMT-04:00 ANDERSON JUNIOR GADO DA SILVA <<a href="mailto:andersonscinfo@gmail.com">andersonscinfo@gmail.com</a>>:<br>
> > > Hello, I'm using openwrt, I found this command in openwrt has some other would work similarly?<br>
> > ><br>
> > > Att<br>
> > > Anderson Junior<br>
> > ><br>
> > ><br>
> > > 2014-04-09 1:38 GMT-04:00 Teco Boot <<a href="mailto:teco@inf-net.nl">teco@inf-net.nl</a>>:<br>
> > ><br>
> > > If you have a static default route via an interface, and that interface goes down, the route should be removed from routing table.<br>
> > ><br>
> > > The ping function in dyn-gw is for connectivity problems while local interface is still up.<br>
> > ><br>
> > > Please provide logging from following commands:<br>
> > ><br>
> > > ip route show table all dev eth1<br>
> > > ip route show table all | grep default<br>
> > > ping -c 2 -w 4 8.8.8.8<br>
> > ><br>
> > > ifconfig eth1 down<br>
> > > ip route show table all dev eth1<br>
> > > ip route show table all | grep default<br>
> > > ping -c 2 -w 4 8.8.8.8<br>
> > ><br>
> > > ifconfig eth1 up<br>
> > > ip route show table all dev eth1<br>
> > > ip route show table all | grep default<br>
> > > ping -c 2 -w 4 8.8.8.8<br>
> > ><br>
> > > Change 8.8.8.8 to 10.4.0.1 if you are not connected to internet.<br>
> > ><br>
> > > Teco<br>
> > ><br>
> > ><br>
> > > Op 8 apr. 2014, om 23:35 heeft ANDERSON JUNIOR GADO DA SILVA <<a href="mailto:andersonscinfo@gmail.com">andersonscinfo@gmail.com</a>> het volgende geschreven:<br>
> > ><br>
> > > > 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.<br>
> > > ><br>
> > > > Att<br>
> > > > Anderson Junior<br>
> > > ><br>
> > > ><br>
> > > > 2014-04-08 16:59 GMT-04:00 Teco Boot <<a href="mailto:teco@inf-net.nl">teco@inf-net.nl</a>>:<br>
> > > > The plugin parameters are ordered, at least for dyn_gw.<br>
> > > > Read from bottom to top.<br>
> > > > Your config reads first "HNA" "0.0.0.0 0.0.0.0", no ping test set.<br>
> > > > Then the "Ping" "10.4.0.1", but no HNA for it.<br>
> > > ><br>
> > > > Please test with:<br>
> > > ><br>
> > > > LoadPlugin "olsrd_dyn_gw.so.0.5"<br>
> > > > {<br>
> > > > PlParam "HNA" "0.0.0.0 0.0.0.0"<br>
> > > > PlParam "Ping" "10.4.0.1"<br>
> > > > PlParam "CheckInterval" "5000"<br>
> > > > PlParam "PingInterval" "5"<br>
> > > > }<br>
> > > ><br>
> > > ><br>
> > > > When no HNA parameter is provided, "HNA" "0.0.0.0 0.0.0.0” is assumed (not tested by me!).<br>
> > > ><br>
> > > > Teco<br>
> > > ><br>
> > > ><br>
> > > > Op 8 apr. 2014, om 22:47 heeft ANDERSON JUNIOR GADO DA SILVA <<a href="mailto:andersonscinfo@gmail.com">andersonscinfo@gmail.com</a>> het volgende geschreven:<br>
> > > ><br>
> > > > > I understand WHAT you explained to me, since I made the change as suggested Teco, thus:<br>
> > > > ><br>
> > > > > LoadPlugin "olsrd_dyn_gw.so.0.5"<br>
> > > > > {<br>
> > > > > PlParam "Ping" "10.4.0.1"<br>
> > > > > PlParam "HNA" "0.0.0.0 0.0.0.0"<br>
> > > > > PlParam "CheckInterval" "5000"<br>
> > > > > PlParam "PingInterval" "5"<br>
> > > > > }<br>
> > > > ><br>
> > > > > 10.4.0.1 is a local dns server, so I continued using it as a reference for the ping,<br>
> > > > ><br>
> > > > > this correct?<br>
> > > > ><br>
> > > > > Att<br>
> > > > > Anderson Junior<br>
> > > > ><br>
> > > > ><br>
> > > > > 2014-04-08 16:34 GMT-04:00 Henning Rogge <<a href="mailto:hrogge@gmail.com">hrogge@gmail.com</a>>:<br>
> > > > > On Tue, Apr 8, 2014 at 10:27 PM, ANDERSON JUNIOR GADO DA SILVA<br>
> > > > > <<a href="mailto:andersonscinfo@gmail.com">andersonscinfo@gmail.com</a>> wrote:<br>
> > > > > > I'll try to explain with my words, ping the address must be a reachable<br>
> > > > > > address outside the network, preferably the Internet, a known site or dns,<br>
> > > > > > it ensures that the node has internet, HNA understand to be the network<br>
> > > > > > where the olsr will flood with your posts, this would be the network where<br>
> > > > > > the working olsr. If you are traveling to pull my ear, (laughs).<br>
> > > > ><br>
> > > > > A HNA announces a prefix outside the OLSR mesh network. In fact it<br>
> > > > > announces that the local node can reach this prefix, the HNA allows<br>
> > > > > the other nodes to access this prefix through the local node.<br>
> > > > ><br>
> > > > > The ping mechanism of the dyn_gw plugin checks the bi-directional<br>
> > > > > connectivity to a host within this prefix.<br>
> > > > ><br>
> > > > > If you are re-distributing a route to the internet, the prefix would<br>
> > > > > be <a href="http://0.0.0.0/0" target="_blank">0.0.0.0/0</a> (the default route) and the ping address would be a host<br>
> > > > > on the internet (e.g. 8.8.8.8, the google dns).<br>
> > > > ><br>
> > > > > Henning<br>
> > > > ><br>
> > > > ><br>
> > > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> ><br>
> ><br>
> ><br>
><br>
><br>
<br>
</div></div></blockquote></div><br><br></div></div>