[Olsr-users] Where am I going wrong in the settings.
ANDERSON JUNIOR GADO DA SILVA
(spam-protected)
Thu Apr 10 01:00:33 CEST 2014
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:
connected:
ifconfig eth1
eth1 Link encap:Ethernet HWaddr C0:4A:00:50:0C:3D
inet addr:172.16.0.3 Bcast:172.16.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:720 errors:0 dropped:140 overruns:0 frame:0
TX packets:193 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:114567 (111.8 KiB) TX bytes:17842 (17.4 KiB)
Interrupt:4
disconnected:
ifconfig eth1
eth1 Link encap:Ethernet HWaddr C0:4A:00:50:0C:3D
inet addr:172.16.0.3 Bcast:172.16.0.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:840 errors:0 dropped:163 overruns:0 frame:0
TX packets:212 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:136368 (133.1 KiB) TX bytes:19496 (19.0 KiB)
Interrupt:4
After bringing eth1 down, the routes for that interface stays there for a
long time?
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
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?
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.
if you wants to access the routers remotely or if I want to see more
configuration files just let me know.
Att
Anderson Junior
2014-04-09 16:05 GMT-04:00 Teco Boot <(spam-protected)>:
> I see same minor issue as what I have seen before. The list with HNA
> entries doesn't show all 0.0.0.0/0 routes, right?
> In first HNA listing, the 0.0.0.0/0 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.
>
> 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.
> Please report ifconfig eth1 output, with cable connected and disconnected.
>
> 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?
>
> Teco
>
>
>
> Op 9 apr. 2014, om 19:06 heeft ANDERSON JUNIOR GADO DA SILVA <
> (spam-protected)> het volgende geschreven:
>
> > 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
> >
> > before:
> > route
> > Kernel IP routing table
> > Destination Gateway Genmask Flags Metric Ref Use
> Iface
> > default 172.16.0.1 0.0.0.0 UG 0 0 0
> eth1
> > 10.5.0.0 * 255.255.0.0 U 0 0 0
> wlan0
> > 10.5.0.4 10.5.0.4 255.255.255.255 UGH 2 0 0
> wlan0
> > 10.5.0.6 10.5.0.6 255.255.255.255 UGH 2 0 0
> wlan0
> > 172.16.0.0 * 255.255.255.0 U 0 0 0
> eth1
> >
> > ====================================================
> > echo '/all' | nc localhost 2006
> > HTTP/1.0 200 OK
> > Content-type: text/plain
> >
> > Table: Links
> > Local IP Remote IP Hyst. LQ NLQ Cost
> > 10.5.0.5 10.5.0.6 0.00 1.000 1.000 1.000
> > 10.5.0.5 10.5.0.4 0.00 1.000 1.000 1.000
> >
> > Table: Neighbors
> > IP address SYM MPR MPRS Will. 2 Hop Neighbors
> > 10.5.0.4 YES NO NO 3 1
> > 10.5.0.6 YES NO NO 3 1
> >
> > Table: Topology
> > Dest. IP Last hop IP LQ NLQ Cost
> > 10.5.0.5 10.5.0.4 1.000 1.000 1.000
> > 10.5.0.6 10.5.0.4 1.000 1.000 1.000
> > 10.5.0.4 10.5.0.5 1.000 1.000 1.000
> > 10.5.0.6 10.5.0.5 1.000 1.000 1.000
> > 10.5.0.4 10.5.0.6 1.000 1.000 1.000
> > 10.5.0.5 10.5.0.6 1.000 1.000 1.000
> >
> > Table: HNA
> > Destination Gateway
> > 0.0.0.0/0 10.5.0.5
> >
> > Table: MID
> > IP address Aliases
> >
> > Table: Routes
> > Destination Gateway IP Metric ETX Interface
> > 10.5.0.4/32 10.5.0.4 1 1.000 wlan0
> > 10.5.0.6/32 10.5.0.6 1 1.000 wlan0
> >
> >
> >
> > after taking the cable:
> > 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
> >
> > route
> > Kernel IP routing table
> > Destination Gateway Genmask Flags Metric Ref Use
> Iface
> > default 172.16.0.1 0.0.0.0 UG 0 0 0
> eth1
> > default 10.5.0.6 0.0.0.0 UG 2 0 0
> wlan0
> > 10.5.0.0 * 255.255.0.0 U 0 0 0
> wlan0
> > 10.5.0.4 10.5.0.4 255.255.255.255 UGH 2 0 0
> wlan0
> > 10.5.0.6 10.5.0.6 255.255.255.255 UGH 2 0 0
> wlan0
> > 172.16.0.0 * 255.255.255.0 U 0 0 0
> eth1
> >
> > ======================================================
> > echo '/all' | nc localhost 2006
> > HTTP/1.0 200 OK
> > Content-type: text/plain
> >
> > Table: Links
> > Local IP Remote IP Hyst. LQ NLQ Cost
> > 10.5.0.5 10.5.0.6 0.00 1.000 1.000 1.000
> > 10.5.0.5 10.5.0.4 0.00 1.000 1.000 1.000
> >
> > Table: Neighbors
> > IP address SYM MPR MPRS Will. 2 Hop Neighbors
> > 10.5.0.4 YES NO NO 3 1
> > 10.5.0.6 YES NO NO 3 1
> >
> > Table: Topology
> > Dest. IP Last hop IP LQ NLQ Cost
> > 10.5.0.5 10.5.0.4 1.000 1.000 1.000
> > 10.5.0.6 10.5.0.4 1.000 1.000 1.000
> > 10.5.0.4 10.5.0.5 1.000 1.000 1.000
> > 10.5.0.6 10.5.0.5 1.000 1.000 1.000
> > 10.5.0.4 10.5.0.6 1.000 1.000 1.000
> > 10.5.0.5 10.5.0.6 1.000 1.000 1.000
> >
> > Table: HNA
> > Destination Gateway
> > 0.0.0.0/0 10.5.0.6
> >
> > Table: MID
> > IP address Aliases
> >
> > Table: Routes
> > Destination Gateway IP Metric ETX Interface
> > 0.0.0.0/0 10.5.0.6 1 1.000 wlan0
> > 10.5.0.4/32 10.5.0.4 1 1.000 wlan0
> > 10.5.0.6/32 10.5.0.6 1 1.000 wlan0
> >
> >
> > Now before ifconfig eth1 down:
> > route
> > Kernel IP routing table
> > Destination Gateway Genmask Flags Metric Ref Use
> Iface
> > default 172.16.0.1 0.0.0.0 UG 0 0 0
> eth1
> > 10.5.0.0 * 255.255.0.0 U 0 0 0
> wlan0
> > 10.5.0.4 10.5.0.6 255.255.255.255 UGH 2 0 0
> wlan0
> > 10.5.0.6 10.5.0.6 255.255.255.255 UGH 2 0 0
> wlan0
> > 172.16.0.0 * 255.255.255.0 U 0 0 0
> eth1
> >
> > =====================================================
> >
> > echo '/all' | nc localhost 2006
> > HTTP/1.0 200 OK
> > Content-type: text/plain
> >
> > Table: Links
> > Local IP Remote IP Hyst. LQ NLQ Cost
> > 10.5.0.5 10.5.0.6 0.00 1.000 1.000 1.000
> > 10.5.0.5 10.5.0.4 0.00 1.000 1.000 1.000
> >
> > Table: Neighbors
> > IP address SYM MPR MPRS Will. 2 Hop Neighbors
> > 10.5.0.4 YES NO NO 3 1
> > 10.5.0.6 YES NO NO 3 1
> >
> > Table: Topology
> > Dest. IP Last hop IP LQ NLQ Cost
> > 10.5.0.5 10.5.0.4 1.000 1.000 1.000
> > 10.5.0.6 10.5.0.4 1.000 1.000 1.000
> > 10.5.0.4 10.5.0.5 1.000 1.000 1.000
> > 10.5.0.6 10.5.0.5 1.000 1.000 1.000
> > 10.5.0.4 10.5.0.6 1.000 1.000 1.000
> > 10.5.0.5 10.5.0.6 1.000 1.000 1.000
> >
> > Table: HNA
> > Destination Gateway
> > 0.0.0.0/0 10.5.0.5
> >
> > Table: MID
> > IP address Aliases
> >
> > Table: Routes
> > Destination Gateway IP Metric ETX Interface
> > 10.5.0.4/32 10.5.0.4 1 1.000 wlan0
> > 10.5.0.6/32 10.5.0.6 1 1.000 wlan0
> >
> >
> >
> > after:
> >
> > ifconfig eth1 down
> > route
> > Kernel IP routing table
> > Destination Gateway Genmask Flags Metric Ref Use
> Iface
> > default 10.5.0.6 0.0.0.0 UG 2 0 0
> wlan0
> > 10.5.0.0 * 255.255.0.0 U 0 0 0
> wlan0
> > 10.5.0.4 10.5.0.4 255.255.255.255 UGH 2 0 0
> wlan0
> > 10.5.0.6 10.5.0.6 255.255.255.255 UGH 2 0 0
> wlan0
> >
> > ======================================
> > echo '/all' | nc localhost 2006
> > HTTP/1.0 200 OK
> > Content-type: text/plain
> >
> > Table: Links
> > Local IP Remote IP Hyst. LQ NLQ Cost
> > 10.5.0.5 10.5.0.6 0.00 1.000 1.000 1.000
> > 10.5.0.5 10.5.0.4 0.00 1.000 1.000 1.000
> >
> > Table: Neighbors
> > IP address SYM MPR MPRS Will. 2 Hop Neighbors
> > 10.5.0.4 YES NO NO 3 1
> > 10.5.0.6 YES NO NO 3 1
> >
> > Table: Topology
> > Dest. IP Last hop IP LQ NLQ Cost
> > 10.5.0.5 10.5.0.4 1.000 1.000 1.000
> > 10.5.0.6 10.5.0.4 1.000 1.000 1.000
> > 10.5.0.4 10.5.0.5 1.000 1.000 1.000
> > 10.5.0.6 10.5.0.5 1.000 1.000 1.000
> > 10.5.0.4 10.5.0.6 1.000 1.000 1.000
> > 10.5.0.5 10.5.0.6 1.000 1.000 1.000
> >
> > Table: HNA
> > Destination Gateway
> > 0.0.0.0/0 10.5.0.6
> >
> > Table: MID
> > IP address Aliases
> >
> > Table: Routes
> > Destination Gateway IP Metric ETX Interface
> > 0.0.0.0/0 10.5.0.6 1 1.000 wlan0
> > 10.5.0.4/32 10.5.0.4 1 1.000 wlan0
> > 10.5.0.6/32 10.5.0.6 1 1.000 wlan0
> >
> > ==========================================
> >
> >
> > 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.
> >
> > Att
> > Anderson Junior
> >
> > 2014-04-09 11:12 GMT-03:00 Teco Boot <(spam-protected)>:
> > No, it doesn't matter how the default route is provided.
> > If static, after an ifconfig eth1 up, you should reinstall the route
> again.
> >
> > I am a bit lost on the status. I guess dyn_gw is working, right?
> > If not, please provide fresh config and status as you sent before.
> >
> > Teco
> >
> >
> > Op 9 apr. 2014, om 14:21 heeft ANDERSON JUNIOR GADO DA SILVA <
> (spam-protected)> het volgende geschreven:
> >
> > > hello again, one thing I noticed was that the nodes gw, when I give
> the command:
> > >
> > > ifconfig eth1 down
> > >
> > > 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
> > >
> > > Att
> > > Anderson Junior
> > >
> > >
> > > 2014-04-09 7:31 GMT-04:00 ANDERSON JUNIOR GADO DA SILVA <
> (spam-protected)>:
> > > Hello, I'm using openwrt, I found this command in openwrt has some
> other would work similarly?
> > >
> > > Att
> > > Anderson Junior
> > >
> > >
> > > 2014-04-09 1:38 GMT-04:00 Teco Boot <(spam-protected)>:
> > >
> > > 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
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> >
> >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20140409/86238f90/attachment.html>
More information about the Olsr-users
mailing list