<div dir="ltr"><div class="gmail_quote">Hi ,<br><div dir="ltr"><div><div><div><div><br></div>The topology we have created is typically as what you said. <br>(192.168.1.229) (192.168.1.243)<br></div> C1<------------> R1<--------------->R2<------------------>R3<----------->C2 <br> (192.168.1.75) (192.168.1.45) (192.168.1.1)<br><br> <br>
On all the routers the following has been done.<br>
Hna4 {<br>
192.168.1.0 255.255.255.0<br>
}<br><br><br></div>But still the clients cant ping each other.<span class="HOEnZb"><font color="#888888"><br><br><br></font></span></div><span class="HOEnZb"><font color="#888888">Sahana<br></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 22, 2014 at 10:20 AM, Vigneswaran R <span dir="ltr"><<a href="mailto:vignesh@atc.tcs.com" target="_blank">vignesh@atc.tcs.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On 12/21/2014 08:58 PM, Henning Rogge wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
based on your questions I added some more text to the coming OLSR<br>
wiki... can you have a look if you think they are<br>
useful/understandable?<br>
<br>
<a href="http://www.olsr.org/mediawiki/index.php/Troubleshooting" target="_blank">http://www.olsr.org/mediawiki/<u></u>index.php/Troubleshooting</a><br>
<a href="http://www.olsr.org/mediawiki/index.php/OLSR_networks" target="_blank">http://www.olsr.org/mediawiki/<u></u>index.php/OLSR_networks</a><br>
</blockquote>
<br></span>
Henning:<br>
<br>
Excellent resources! Thanks.<br>
<br>
Sahana:<br>
<br>
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)<br>
<br>
<a href="http://192.168.1.0/24" target="_blank">192.168.1.0/24</a> <a href="http://192.168.2.0/24" target="_blank">192.168.2.0/24</a><br>
C1 <------------> R1 <---> R2 <---> R3 <------------>C2<br>
.2 .1 .1 .2<br>
<br>
* On C1, add default route by executing the following command<br>
<br>
ip route add default via 192.168.1.1<br>
<br>
* On C2, add default route by executing the following command<br>
<br>
ip route add default via 192.168.2.1<br>
<br>
* On R1, add the HNA entry for <a href="http://192.168.1.0/24" target="_blank">192.168.1.0/24</a> network and restart the OLSR daemon. eg.,<br>
<br>
Hna4 {<br>
192.168.1.0 255.255.255.0<br>
}<br>
<br>
* On R2, add the HNA entry for <a href="http://192.168.2.0/24" target="_blank">192.168.2.0/24</a> network and restart the OLSR daemon. eg.,<br>
<br>
Hna4 {<br>
192.168.2.0 255.255.255.0<br>
}<br>
<br>
If everything goes fine, you can see routes to <a href="http://192.168.1.0/24" target="_blank">192.168.1.0/24</a>, <a href="http://192.168.2.0/24" target="_blank">192.168.2.0/24</a> on all the routers (R1, R2, R3) using 'ip route' command. Also, the clients (C1, C2) should be able to ping each other.<br>
<br>
<br>
Vignesh<div><div><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Henning Rogge<br>
<br>
On Sun, Dec 21, 2014 at 4:07 PM, Sahana k.srinivas<br>
<<a href="mailto:sahana19793@gmail.com" target="_blank">sahana19793@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Okay! Will check it out. And let you know what happens. Thank you !<br>
<br>
<br>
Regards,<br>
Sahana<br>
<br>
On Sun, Dec 21, 2014 at 8:16 PM, Henning Rogge <<a href="mailto:hrogge@gmail.com" target="_blank">hrogge@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Sun, Dec 21, 2014 at 3:36 PM, Sahana k.srinivas<br>
<<a href="mailto:sahana19793@gmail.com" target="_blank">sahana19793@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The client can ping the router to which it is connected but the router<br>
cannot ping its client.<br>
</blockquote>
Good... I expected it to work, it was just the easiest thing to test. ;)<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
No, I did not set the IP address as HNA in olsrd. Will do that and check<br>
the<br>
results.<br>
</blockquote>
Do so... without the HNA the mesh routers will not know about the<br>
IP/prefix of the attached clients of the other routers!<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
And the 3rd point, Sorry I dint get you! Should a route be set? Or does<br>
a<br>
default route exist?<br>
</blockquote>
You need a route from the client to their local router to reach the<br>
rest of the mesh.<br>
<br>
The easiest option is a default route, often distributed via DHCP...<br>
but in theory it would be enough to have a route that is "wide" enough<br>
to contain all nodes in the mesh and attached to the mesh.<br>
<br>
Default route does not work if one of your clients has normal internet<br>
access (as an example).<br>
<br>
Henning Rogge<br>
</blockquote>
<br>
<br>
--<br>
Olsr-users mailing list<br>
<a href="mailto:Olsr-users@lists.olsr.org" target="_blank">Olsr-users@lists.olsr.org</a><br>
<a href="https://lists.olsr.org/mailman/listinfo/olsr-users" target="_blank">https://lists.olsr.org/<u></u>mailman/listinfo/olsr-users</a><br>
</blockquote></blockquote>
<br>
</div></div></blockquote></div><br></div>
</div></div></div><br></div>