[Olsr-users] OLSR network routing question

[Deepak Lal]

Yes I meant [interface=eth1].


What follows is the output from 192.168.2.1 (mesh router), 192.168.2.2 (mesh router), 192.168.2.10 (mesh point on the 192.168.2.1 segment) and 192.168.2.12 (mesh point on the 192.168.2.2 segment)  [ please refer image ]


I can ping almost everything to everything with the following three exceptions:


1) The mesh router 192.168.2.1 cannot ping 192.168.2.2    (If you look at the ip route output on 192.168.2.1, there is no "explicit" route to 192.168.2.2)


The mesh router 192.168.2.2 can on the other hand ping 192.168.2.1  (if you look at the ip route output on 192.168.2.2, there is an explicit route to 192.168.2.1)


2) The IP 192.168.2.12 cannot ping 192.168.2.1


3) The IP 192.168.2.10 cannot ping 192.168.2.2




*** On 192.168.2.2 routing table, please note that the  line:

192.168.2.1 via 192.168.3.1 dev eth0

is present. A corresponding line is not present on 192.168.2.1. *****


-------------------

IP 192.168.2.1

--------------------


olsrd2 config file:


[olsrv2]
originator -127.0.0.1/8
originator -::/0
originator default_accept

[interface]
bindto -127.0.0.1/8
bindto -::/0
bindto default_accept

[interface=eth1]
[interface=eth0]
[interface=lo




IP ROUTE output


 # ip route
192.168.2.0/24 dev eth1  proto kernel  scope link  src 192.168.2.1  metric 1
192.168.2.10 via 192.168.2.10 dev eth1  proto 100  src 192.168.3.1  metric 2 onlink
192.168.2.11 via 192.168.2.11 dev eth1  proto 100  src 192.168.3.1  metric 2 onlink
192.168.2.12 via 192.168.3.2 dev eth0  proto 100  src 192.168.3.1  metric 2 onlink
192.168.3.0/24 dev eth0  proto kernel  scope link  src 192.168.3.1  metric 1
192.168.3.2 via 192.168.3.2 dev eth0  proto 100  src 192.168.3.1  metric 2 onlink


---------------
192.168.2.2
----------------

olsrd2 config file:

[olsrv2]
originator  -127.0.0.1/8
originator  -::/0
originator  default_accept

[interface]
bindto  -127.0.0.1/8
bindto  -::/0
bindto  default_accept

[interface=eth1]
[interface=eth0]
[interface=lo]

IP ROUTE output

192.168.2.0/24 dev eth1  proto kernel  scope link  src 192.168.2.2  metric 1
192.168.2.1 via 192.168.3.1 dev eth0
192.168.2.10 via 192.168.3.1 dev eth0  proto 100  src 192.168.3.2  metric 2 onlink
192.168.2.11 via 192.168.3.1 dev eth0  proto 100  src 192.168.3.2  metric 2 onlink
192.168.2.12 via 192.168.2.12 dev eth1  proto 100  src 192.168.3.2  metric 2 onlink
192.168.3.0/24 dev eth0  proto kernel  scope link  src 192.168.3.2  metric 1
192.168.3.1 via 192.168.3.1 dev eth0  proto 100  src 192.168.3.2  metric 2 onlink



------------------
192.168.2.10
-------------------

# olsrd2_static enp0s25 lo

 IP ROUTE OUPUT:
169.254.0.0/16 dev enp0s25  scope link  metric 1000
192.168.2.0/24 dev enp0s25  proto kernel  scope link  src 192.168.2.10
192.168.2.11 via 192.168.2.11 dev enp0s25  proto 100  src 192.168.2.10  metric 2 onlink
192.168.2.12 via 192.168.2.1 dev enp0s25  proto 100  src 192.168.2.10  metric 2 onlink
192.168.3.1 via 192.168.2.1 dev enp0s25  proto 100  src 192.168.2.10  metric 2 onlink
192.168.3.2 via 192.168.2.1 dev enp0s25  proto 100  src 192.168.2.10  metric 2 onlink


----------------------
192.168.2.12
-----------------------

#olsrd2_static eth0 lo

IP ROUTE OUTPUT:

192.168.2.0/24 dev eth0  proto kernel  scope link  src 192.168.2.12  metric 1
192.168.2.10 via 192.168.2.2 dev eth0  proto 100  src 192.168.2.12  metric 2 onlink
192.168.2.11 via 192.168.2.2 dev eth0  proto 100  src 192.168.2.12  metric 2 onlink
192.168.3.1 via 192.168.2.2 dev eth0  proto 100  src 192.168.2.12  metric 2 onlink
192.168.3.2 via 192.168.2.2 dev eth0  proto 100  src 192.168.2.12  metric 2 onlink




Thanks


________________________________
From: Henning Rogge <(spam-protected)>
Sent: February 15, 2017 9:28 AM
To: Deepak Lal
Cc: (spam-protected)
Subject: Re: [Olsr-users] OLSR network routing question

On Wed, Feb 15, 2017 at 3:23 PM, Deepak Lal <(spam-protected)> wrote:
> Thanks.
>
> I tried two appproaches and neither work correctly.
>
> Approach 1) On the TWO multi-homed linux routers, I had the following config
> (192.168.2.0/24 is mesh network and 192.168.3.0/24 is lan)

> ---
>
> [olsrv2]
>   lan 192.168.3.0/24
>
> [interface eth1]


you mean "[interface=eth1]" ?

> The issue here was that the whole topology was not propagated
>
> -> 192.168.2.10/11 could not reach 192.168.2.12 and vice-versa
>
> ->192.168.2.10/11 could not reach 192.168.3.2
>
> ->192.168.2.12 could not reach 192.168.3.1

Please don't forget that olsrd2 only installs routes on the mesh
routers... so you need some kind of route on the devices attached to
the "local ethernet" back to the router, e.g. a default route.

> Approach 2)  On the two multi-homes linux routers, I had the following
> config (running olsr on both interfaces)
>
> [interface eth0]
>
> [interface eth1]
>
>
> Now, I had much elaborate routing tables and almost everything was working
> except:
>
>
> -> I could not ping 192.168.2.1 from 192.168.2.2
>
> -> I could not ping 192.168.2.2 from 192.168.2.1
>
> -> I could not ping 192.168.2.1 from 192.168.2.12
>
> -> I could not ping 192.168.2.2 from 192.168.2.10

maybe you could just post the output of "ip route" from all 4 devices
(two mesh routers and two attached devices)?

Henning
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20170215/8aacdc81/attachment-0001.html>