[Olsr-users] Where am I going wrong in the settings.
Teco Boot
(spam-protected)
Tue Apr 8 21:40:03 CEST 2014
Why is 10.5.0.0/16 HNA *and* the MANET subnet?
Why not use dyn_gw with 0.0.0.0/0, to be advertised with HNA if ( 0.0.0.0/0 is present in routing table ) and ( ping to host via 0.0.0.0/24 is reachable) ?
Teco
Op 8 apr. 2014, om 18:07 heeft ANDERSON JUNIOR GADO DA SILVA <(spam-protected)> het volgende geschreven:
> hello, I will show the outputs of the commands of the 3 nodes before and after cutting off the internet from one of the gw below:
>
> before
>
> Node 1 gw:
> 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 0.831 1.000 1.202
> 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 0.831 1.202
> 10.5.0.5 10.5.0.6 1.000 1.000 1.000
>
> Table: HNA
> Destination Gateway
> 10.5.0.0/16 10.5.0.5
> 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
>
> ======================================
> 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
>
> Node 2 gw:
> 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.6 10.5.0.5 0.00 1.000 1.000 1.000
> 10.5.0.6 10.5.0.4 0.00 1.000 0.713 1.400
>
> Table: Neighbors
> IP address SYM MPR MPRS Will. 2 Hop Neighbors
> 10.5.0.4 YES NO NO 3 1
> 10.5.0.5 YES NO NO 3 1
>
> Table: Topology
> Dest. IP Last hop IP LQ NLQ Cost
> 10.5.0.5 10.5.0.4 0.940 1.000 1.063
> 10.5.0.6 10.5.0.4 0.713 1.000 1.400
> 10.5.0.4 10.5.0.5 1.000 0.886 1.128
> 10.5.0.6 10.5.0.5 1.000 1.000 1.000
> 10.5.0.4 10.5.0.6 1.000 0.713 1.400
> 10.5.0.5 10.5.0.6 1.000 1.000 1.000
>
> Table: HNA
> Destination Gateway
> 10.5.0.0/16 10.5.0.6
> 0.0.0.0/0 10.5.0.6
>
> Table: MID
> IP address Aliases
>
> Table: Routes
> Destination Gateway IP Metric ETX Interface
> 10.5.0.4/32 10.5.0.4 1 1.400 wlan0
> 10.5.0.5/32 10.5.0.5 1 1.000 wlan0
>
> ===============================================
> 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.5 10.5.0.5 255.255.255.255 UGH 2 0 0 wlan0
> 172.16.0.0 * 255.255.255.0 U 0 0 0 eth1
>
>
> 3 client node:
> 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.4 10.5.0.6 0.00 0.761 1.000 1.313
> 10.5.0.4 10.5.0.5 0.00 1.000 1.000 1.000
>
> Table: Neighbors
> IP address SYM MPR MPRS Will. 2 Hop Neighbors
> 10.5.0.5 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 0.761 1.000 1.313
> 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 0.643 1.555
> 10.5.0.5 10.5.0.6 1.000 1.000 1.000
>
> Table: HNA
> Destination Gateway
> 10.5.0.0/16 10.5.0.4
> 0.0.0.0/0 10.5.0.5
> 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.5 1 1.000 wlan0
> 10.5.0.5/32 10.5.0.5 1 1.000 wlan0
> 10.5.0.6/32 10.5.0.6 1 1.313 wlan0
>
> ==========================================
> route
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> default 10.5.0.5 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.5 10.5.0.5 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
> 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
>
> after disconnecting the internet from node 1 gw
>
> Node 1 gw:
> 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 0.721 1.000 1.386
> 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 0.721 1.386
> 10.5.0.5 10.5.0.6 1.000 1.000 1.000
>
> Table: HNA
> Destination Gateway
> 10.5.0.0/16 10.5.0.5
> 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
>
> ==============================================
> 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
>
> Node 2 gw:
> 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.6 10.5.0.5 0.00 1.000 1.000 1.000
> 10.5.0.6 10.5.0.4 0.00 1.000 0.732 1.363
>
> Table: Neighbors
> IP address SYM MPR MPRS Will. 2 Hop Neighbors
> 10.5.0.4 YES NO NO 3 1
> 10.5.0.5 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 0.732 1.000 1.363
> 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 0.732 1.363
> 10.5.0.5 10.5.0.6 1.000 1.000 1.000
>
> Table: HNA
> Destination Gateway
> 10.5.0.0/16 10.5.0.6
> 0.0.0.0/0 10.5.0.6
>
> Table: MID
> IP address Aliases
>
> Table: Routes
> Destination Gateway IP Metric ETX Interface
> 10.5.0.4/32 10.5.0.4 1 1.363 wlan0
> 10.5.0.5/32 10.5.0.5 1 1.000 wlan0
>
> ======================================================
> 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.5 10.5.0.5 255.255.255.255 UGH 2 0 0 wlan0
> 172.16.0.0 * 255.255.255.0 U 0 0 0 eth1
>
> 3 client node:
> 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.4 10.5.0.6 0.00 0.831 1.000 1.202
> 10.5.0.4 10.5.0.5 0.00 1.000 1.000 1.000
>
> Table: Neighbors
> IP address SYM MPR MPRS Will. 2 Hop Neighbors
> 10.5.0.5 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 0.831 1.000 1.202
> 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 0.831 1.202
> 10.5.0.5 10.5.0.6 1.000 1.000 1.000
>
> Table: HNA
> Destination Gateway
> 10.5.0.0/16 10.5.0.4
> 0.0.0.0/0 10.5.0.5
> 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.5 1 1.000 wlan0
> 10.5.0.5/32 10.5.0.5 1 1.000 wlan0
> 10.5.0.6/32 10.5.0.6 1 1.202 wlan0
>
> ===============================================
> route
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> default 10.5.0.5 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.5 10.5.0.5 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
> 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
>
> end
>
> at node 1 gw, may notice that it added the new default "default 10.5.0.6 0.0.0.0 UG 2 0 0 wlan0" route but both the client node 2 when node 1 gw are without internet connection, I do not know why he did not remove the first route that is not more being achieved. Maybe it's because the wan node 1 gw this set of static and not in dhcp mode.
>
> Att
> Anderson Junior
>
>
>
>
> 2014-04-08 5:32 GMT-04:00 Henning Rogge <(spam-protected)>:
> On Tue, Apr 8, 2014 at 3:53 AM, ANDERSON JUNIOR GADO DA SILVA <(spam-protected)> wrote:
> Hi, I spent the weekend and all day today trying to understand where this my mistake, but so far no concegui find, I'll try clearly explain my test environment, reduce to 3 the number of routers, let's go:
>
> Node 1 gw
> Node 2 gw
> 3 client node
>
> the 2 nodes that are gw, I configured the wan interfaces with fixed ip, catching internet switch, all routers are close, the node 3 cable I have connected my computer to test the internet, so I'll call the 3 routers, logo node 3 chooses a wheel, sometimes the node 1 node 2 times.
>
> everything working fine I will do some testing, I see that this pointed to the the route to node 1, then it will switch and lock the internet from node 1 to see if the node 3 will change the route to node 2 that still has internet but this does not happen, then I see this as the routing table and it has not changed, still pointing to node 1, only works if I restart olsr (/ etc / init.d / olsrd restart), when I do that it points to route to node 2, I wonder if I have to make a script and put it in cron will clear this route table from time to time, or how to make it update routes when a change occurs in the topology below follows like this now my olsr.conf
>
> You should see the HNA (Host and Network Association) of node one vanishing (you can check with the txtinfo output on node 3).
>
> If it does not vanish your usage/configuration of the dyn_gw plugin doesn't work, which makes olsr not to detect your internet loss.
>
> Henning Rogge
>
>
> --
> Olsr-users mailing list
> (spam-protected)
> https://lists.olsr.org/mailman/listinfo/olsr-users
More information about the Olsr-users
mailing list