[Olsr-users] Fwd: Mesh network
Sahana k.srinivas
(spam-protected)
Wed Dec 24 16:59:27 CET 2014
Hi,
Thank you for your response :)
We tried the things you said using this topology
(192.168.2.101/24) (192.168.2.1/24) (10.0.0.1/24)
(10.0.0.111/24)
C1<------------------------->R1<------------------------>R2<------------------->C2
(192.168.1.1/24) (
192.168.1.45/24)
And HNA was configured on these two routers! But client to client
communication was not possible!
This topology should work right?
Regards,
Sahana
On Mon, Dec 22, 2014 at 11:20 AM, Vigneswaran R <(spam-protected)> wrote:
> On 12/22/2014 10:54 AM, Sahana k.srinivas wrote:
>
> Hi ,
>
> The topology we have created is typically as what you said.
> (192.168.1.229)
> (192.168.1.243)
> C1<------------>
> R1<--------------->R2<------------------>R3<----------->C2
> (192.168.1.75) (192.168.1.45) (192.168.1.1)
>
>
> Use different IP range for client networks and OLSR network. May be you
> can try the following.
>
> (192.168.1.2/24) (192.168.1.1/24) (192.168.2.1/24)
> (192.168.2.2/24)
> C1<------------>
> R1<--------------->R2<------------------>R3<----------->C2
> (10.0.0.1/8) (10.0.0.2/8) (10.0.0.3/8)
>
> On all the routers the following has been done.
> Hna4 {
> 192.168.1.0 255.255.255.0
> }
>
>
> * The HNA should be configured only on the Routers where clients are
> connected. So, on R2, you should not configure HNA.
>
> * The HNA entries should reflect the client networks the router connected
> to. So, in the above case,
>
> On R1,
>
> Hna4 {
> 192.168.1.0 255.255.255.0
> }
>
> On R3,
>
> Hna4 {
> 192.168.2.0 255.255.255.0
> }
>
> Restart the OLSR daemon on R1 and R3 after making the configuration
> changes.
>
> Vignesh
>
>
>
> But still the clients cant ping each other.
>
>
> Sahana
>
> On Mon, Dec 22, 2014 at 10:20 AM, Vigneswaran R <(spam-protected)>
> wrote:
>
>> On 12/21/2014 08:58 PM, Henning Rogge wrote:
>>
>>> Hi,
>>>
>>> based on your questions I added some more text to the coming OLSR
>>> wiki... can you have a look if you think they are
>>> useful/understandable?
>>>
>>> http://www.olsr.org/mediawiki/index.php/Troubleshooting
>>> http://www.olsr.org/mediawiki/index.php/OLSR_networks
>>>
>>
>> Henning:
>>
>> Excellent resources! Thanks.
>>
>> Sahana:
>>
>> If you have the topology like this, you can use the following
>> instructions to make the clients to ping each other. (Just ensure that you
>> don't have any iptables rules which interfere the traffic)
>>
>> 192.168.1.0/24 192.168.2.0/24
>> C1 <------------> R1 <---> R2 <---> R3 <------------>C2
>> .2 .1 .1 .2
>>
>> * On C1, add default route by executing the following command
>>
>> ip route add default via 192.168.1.1
>>
>> * On C2, add default route by executing the following command
>>
>> ip route add default via 192.168.2.1
>>
>> * On R1, add the HNA entry for 192.168.1.0/24 network and restart the
>> OLSR daemon. eg.,
>>
>> Hna4 {
>> 192.168.1.0 255.255.255.0
>> }
>>
>> * On R2, add the HNA entry for 192.168.2.0/24 network and restart the
>> OLSR daemon. eg.,
>>
>> Hna4 {
>> 192.168.2.0 255.255.255.0
>> }
>>
>> If everything goes fine, you can see routes to 192.168.1.0/24,
>> 192.168.2.0/24 on all the routers (R1, R2, R3) using 'ip route' command.
>> Also, the clients (C1, C2) should be able to ping each other.
>>
>>
>> Vignesh
>>
>>
>>
>>> Henning Rogge
>>>
>>> On Sun, Dec 21, 2014 at 4:07 PM, Sahana k.srinivas
>>> <(spam-protected)> wrote:
>>>
>>>> Okay! Will check it out. And let you know what happens. Thank you !
>>>>
>>>>
>>>> Regards,
>>>> Sahana
>>>>
>>>> On Sun, Dec 21, 2014 at 8:16 PM, Henning Rogge <(spam-protected)>
>>>> wrote:
>>>>
>>>>> On Sun, Dec 21, 2014 at 3:36 PM, Sahana k.srinivas
>>>>> <(spam-protected)> wrote:
>>>>>
>>>>>> The client can ping the router to which it is connected but the router
>>>>>> cannot ping its client.
>>>>>>
>>>>> Good... I expected it to work, it was just the easiest thing to test.
>>>>> ;)
>>>>>
>>>>> No, I did not set the IP address as HNA in olsrd. Will do that and
>>>>>> check
>>>>>> the
>>>>>> results.
>>>>>>
>>>>> Do so... without the HNA the mesh routers will not know about the
>>>>> IP/prefix of the attached clients of the other routers!
>>>>>
>>>>> And the 3rd point, Sorry I dint get you! Should a route be set? Or
>>>>>> does
>>>>>> a
>>>>>> default route exist?
>>>>>>
>>>>> You need a route from the client to their local router to reach the
>>>>> rest of the mesh.
>>>>>
>>>>> The easiest option is a default route, often distributed via DHCP...
>>>>> but in theory it would be enough to have a route that is "wide" enough
>>>>> to contain all nodes in the mesh and attached to the mesh.
>>>>>
>>>>> Default route does not work if one of your clients has normal internet
>>>>> access (as an example).
>>>>>
>>>>> Henning Rogge
>>>>>
>>>>
>>>>
>>>> --
>>>> Olsr-users mailing list
>>>> (spam-protected)
>>>> https://lists.olsr.org/mailman/listinfo/olsr-users
>>>>
>>>
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20141224/cbf67d5f/attachment.html>
More information about the Olsr-users
mailing list