From: Andrew Lunn <andrew@lunn.ch>
To: cmsv@wirelesspt.net,
The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Cc: Antonio Quartulli <antonio@meshcoding.com>
Subject: Re: [B.A.T.M.A.N.] Replacing OLSRD with batman-adv?
Date: Fri, 8 Nov 2013 12:24:37 +0100 [thread overview]
Message-ID: <20131108112437.GH4440@lunn.ch> (raw)
In-Reply-To: <527E189A.4060000@wirelesspt.net>
On Sat, Nov 09, 2013 at 06:12:26AM -0500, cmsv wrote:
> Perhaps i misunderstood.
>
> On 11/08/2013 06:07 AM, Antonio Quartulli wrote:
> > On Sat, Nov 09, 2013 at 05:57:51AM -0500, cmsv wrote:
> >>> 2) Must every client to a batman-adv mesh have a daemon installed?
> >> Every node must have batman-adv
> >
> > Be careful to do not confuse him. He asked about *clients*, and clients are not
> > required to run batman-adv.
>
> Does he mean clients as the people connecting to the access points with
> their computer or node clients that connect to mesh node routers that
> are servers and or gateways and are part of the backbone?
With BATMAN you can split the network into two parts. The mesh
infrastructure, a.k.a the mesh nodes, and devices using the
infrastructure, a.k.a, the clients.
All nodes in the mesh infrastructure need to run batman-adv, so that
they play an active part in the mesh. With the hardware described
here, one of the two interfaces is running in Adhoc mode and is part
of the mesh.
The other interface is run in plain old access point mode. The devices
using the mesh infrastructure connect to the access point as a
station. Thus they don't need batman-adv. They can also roam from
access point to access point, and the mesh infrastructure will work
out delivering the frames to the right access point and so to the
client.
Andrew
prev parent reply other threads:[~2013-11-08 11:24 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
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 [this message]
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=20131108112437.GH4440@lunn.ch \
--to=andrew@lunn.ch \
--cc=antonio@meshcoding.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=cmsv@wirelesspt.net \
/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