<div dir="ltr"><div style="font-size:12.8000001907349px"><div>Hi,</div><div><br></div><div>I have setup HNA on olsrd as below<br>HNA4<br>{ 192.168.2.0 255.255.255.0<br>}<br></div><div>DHCP is enabled on the router for AP interface.<br></div>So<br></div><div style="font-size:12.8000001907349px">I cannot ping different mesh routers<br></div><div style="font-size:12.8000001907349px">I can ping between mesh router and its local client<br></div><div style="font-size:12.8000001907349px">I cannot ping AP client from different mesh router<br></div><div style="font-size:12.8000001907349px">I cannot ping two AP clients from different mesh router</div><div style="font-size:12.8000001907349px"><br></div><div style="font-size:12.8000001907349px"><br></div><div style="font-size:12.8000001907349px">Regards,</div><div style="font-size:12.8000001907349px">Sahana</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 25, 2015 at 1:07 PM, Henning Rogge <span dir="ltr"><<a href="mailto:hrogge@gmail.com" target="_blank">hrogge@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I am crossposting this to olsr-users because my answer should be<br>
generic enough for both OLSR and Babel... and the mail I am responding<br>
to contains much more information than the one we received on the<br>
olsr-users list.<br>
<br>
You need four basic things for routing between the clients attached to<br>
the access points of your mesh.<br>
<br>
A) routing between the mesh routers itself (I think you got this covered)<br>
B) routing from the mesh routers to the IPs of the attached access<br>
points (You got that covered by setting the network mask on the AP<br>
interface)<br>
C) routing of mesh routers for the prefix of an AP towards the mesh<br>
router the AP is attached to.<br>
D) routing of traffic for mesh routers and attached APs from a client<br>
connected to an AP to the local mesh router.<br>
<br>
C is done by telling the routing protocol that your local mesh node is<br>
responsible for more prefixes. In olsrd you have to set the prefix as<br>
a "HNA" (Host Network Association), in Babel you have to tell Babel to<br>
export the routes of the AP interface I think (Someone here on the<br>
list can tell you all the details).<br>
<br>
D is most times done by setting up a DHCP on the mesh router for the<br>
AP interface that distributes a default route back towards the router.<br>
<br>
So check:<br>
- can I ping between two different mesh routers?<br>
- can I ping between the mesh router and a local AP client?<br>
- can I ping an AP client from a different mesh router?<br>
- can I ping between two AP clients attached to different mesh routers?<br>
<span class="HOEnZb"><font color="#888888"><br>
Henning Rogge<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Wed, Mar 25, 2015 at 4:27 AM, Sahana k.srinivas<br>
<<a href="mailto:sahana19793@gmail.com">sahana19793@gmail.com</a>> wrote:<br>
> Hi,<br>
><br>
><br>
> Thank you for your response! :)<br>
><br>
> Outback Dingo : Here is The problem with details<br>
> Three routers r1 r2 r3 with ad-hoc and Access point are configured on wlan0<br>
> interface running on 2.4GHz<br>
> The configuration<br>
> router r1<br>
> adhoc mode : ssid "mesh"<br>
> ip: 192.168.1.1<br>
> subnet:255.255.255.0<br>
> access point: ssid C1<br>
> ip 192.168.2.1<br>
> subnet 255.255.255.0<br>
> router r2<br>
> adhoc mode : ssid "mesh"<br>
> ip: 192.168.1.45<br>
> subnet:255.255.255.0<br>
> access point: ssid C2<br>
> ip 192.168.2.45<br>
> subnet 255.255.255.0<br>
> router r1<br>
> adhoc mode : ssid "mesh"<br>
> ip: 192.168.1.75<br>
> subnet:255.255.255.0<br>
> access point: ssid C1<br>
> ip 192.168.2.75<br>
> subnet 255.255.255.0<br>
><br>
> Im running Babel on three routers on wlan0 interface. I have disabled<br>
> firewall as of now. when laptop(not running babel) connects to R1 it cannot<br>
> access the routing table of babel i.e it cannot communicate with R2 and R3<br>
> also.<br>
> So could you please help me with this problem.And we want to do it without<br>
> having to install Babel on the clients! Because it wouldn't be feasible for<br>
> all the clients in our network to run Babel if they need to communicate with<br>
> other clients.<br>
><br>
><br>
><br>
> Juliusz Chroboczek : Yeah!! I realized that as soon as i sent the mail. And<br>
> immediately sent the corrections in the next mail!! :) Thank you :)<br>
><br>
><br>
> Henning Rogge : Yeah! one of my TeamMate sent the same mail on OLSR group.<br>
> Its because we are trying to implement three routing protocols on our<br>
> network and doing a comparative analysis of them as to which one suits best<br>
> for the topology considered.<br>
> We are stuck up with the client-to-client communication in all the three..<br>
> so trying to get help in all forums :) :)<br>
><br>
><br>
><br>
> Regards,<br>
> Sahana<br>
><br>
><br>
><br>
> On Tue, Mar 24, 2015 at 3:40 PM, Henning Rogge <<a href="mailto:hrogge@gmail.com">hrogge@gmail.com</a>> wrote:<br>
>><br>
>> We got the same mail on olsr-users ~ 23 hours ago.<br>
>><br>
>> Henning Rogge<br>
>><br>
>> On Tue, Mar 24, 2015 at 10:36 AM, Juliusz Chroboczek<br>
>> <<a href="mailto:jch@pps.univ-paris-diderot.fr">jch@pps.univ-paris-diderot.fr</a>> wrote:<br>
>> > Dear Sahana,<br>
>> ><br>
>> >> The router is running OLSRD on wireless interface (wlan0).<br>
>> ><br>
>> > The olsrd mailing list is at <<a href="mailto:olsr-users@lists.olsr.org">olsr-users@lists.olsr.org</a>>. They're<br>
>> > a friendly bunch, please ask there.<br>
>> ><br>
>> > This list is for the Babel routing protocol, which is somewhat similar<br>
>> > to<br>
>> > OLSR but completely different ;-)<br>
>> ><br>
>> > -- Juliusz<br>
>> ><br>
>> > _______________________________________________<br>
>> > Babel-users mailing list<br>
>> > <a href="mailto:Babel-users@lists.alioth.debian.org">Babel-users@lists.alioth.debian.org</a><br>
>> > <a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users</a><br>
><br>
><br>
</div></div></blockquote></div><br></div>