[Olsr-users] [Babel-users] Mesh Network

Sahana k.srinivas (spam-protected)
Wed Mar 25 18:32:15 CET 2015


Hi,

I have setup HNA on olsrd as below
HNA4
{ 192.168.2.0 255.255.255.0
}
DHCP is enabled on the router for AP interface.
So
I cannot ping different mesh routers
I can ping between mesh router and its local client
I cannot ping AP client from different mesh router
I cannot ping two AP clients from different mesh router


Regards,
Sahana

On Wed, Mar 25, 2015 at 1:07 PM, Henning Rogge <(spam-protected)> wrote:

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


More information about the Olsr-users mailing list