From: cmsv <cmsv@wirelesspt.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Replacing OLSRD with batman-adv?
Date: Sat, 09 Nov 2013 05:57:51 -0500 [thread overview]
Message-ID: <527E152F.5090708@wirelesspt.net> (raw)
In-Reply-To: <CAAxzKbRQ-ZPZ8vQUu8GevK+gC-J16EZ-WDkyTcpVxqPZbYg5gw@mail.gmail.com>
Hello Travis.
On 11/08/2013 03:42 AM, tjhowse wrote:
> Hi Ladies and Gents,
>
> I've built a three-node mesh network using cheap TP-Link TL-WDR3600
> routers. They can do simultaneous 5.8GHz and 2.4GHz. I use the 5.8 for
> the backbone links between the nodes, and 2.4 to clients. The nodes
> are running OpenWRT and OLSRD.
>
> This system mostly works well, but there are a couple of problems with
> it that I'm wondering if batman-adv would solve or make easier to
> solve:
>
> 1) The backbone links cannot be better protected than WEP, a
> limitation of OLSRD,
> 2) Gateway assignment is a manual process, which must be performed on
> every node in the mesh, referring to the single node connected to the
> WAN,
> 3) The manual gateway configuration of 2) prevents peer-to-peer
> communications between mesh clients,
> 4) Each node has its own /24 subnet. This causes problems when a
> device roams from one device's jurisdiction to another if the
> interface doesn't re-issue a DHCP request.
>
> We're expanding the network, I've just bought another ten of these
> routers, and I'm going to spend some time assessing if batman-adv
> would be a better fit for our purposes. There will be a range of ios,
> android and windows devices connecting to the mesh.
>
> My questions are as follows:
>
> 1) Does batman-adv worth with WPA2 or better encryption?
Yes but you need some changes such as replacing wpad-mini by wpad and
probably mac80211 and hostpad depending on which openwrt release you
will be using to do all this.
> 2) Must every client to a batman-adv mesh have a daemon installed?
Every node must have batman-adv
> 3) Is it possible to separate different radio interfaces for different
> purposes? I.E. 5.8 for backbone, 2.4 for clients.
Yes and you can even have VAP's
> 4) Can all nodes and clients on a mesh have an IP in the same subnet,
> solving some of the roaming problems caused by bad interface settings
> or drivers?
Yes.
Let me know about your progress regarding these changes if you encounter
some issues because there are some and i have also being trying to solve
them.
>
> Thanks,
> Travis.
> .
>
next prev parent reply other threads:[~2013-11-09 10:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 8:42 [B.A.T.M.A.N.] Replacing OLSRD with batman-adv? tjhowse
2013-11-08 9:02 ` Simon Wunderlich
2013-11-09 10:57 ` cmsv [this message]
2013-11-08 11:07 ` Antonio Quartulli
2013-11-09 11:12 ` cmsv
2013-11-08 11:15 ` Antonio Quartulli
2013-11-08 11:24 ` Andrew Lunn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=527E152F.5090708@wirelesspt.net \
--to=cmsv@wirelesspt.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox