From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] Mesh network advice
Date: Sat, 19 Dec 2009 10:57:00 +0800 [thread overview]
Message-ID: <200912191057.00380.lindner_marek@yahoo.de> (raw)
In-Reply-To: <84e340bd0912181430i39ab586ck614e0116ab05c33d@mail.gmail.com>
Hi,
> I would like to hear your thoughts / advice on batman vs batman-advanced. I
> read the wiki entry on the pros and cons of batman-adv but I am still in
> doubt about which one to use. For instance, batman-adv doesnt have gateway
> support, but it has ipv6 which if I understand correctly can automatically
> configure gateways/routes.
I believe the wiki page is a bit misleading - I just corrected it. We were
trying to convey that batman-adv users can't expect batmand gateway behaviour.
The kernel module won't help you to choose you best gateway (regarding wifi
link qualities / bandwidth / etc). You always can run DHCP, IPv6 autoconf or
any mechanism you like.
In reality it means if you have multiple DHCP gateways in your network the
clients might not always choose the "best" one. Although this is going to
change in the upcoming batman-adv 0.3 branch over the next weeks.
> For a practical scenario like mine, what is the factors I should consider
> when choosing between the two and which one would you suggest?
On one hand it depends the applications you want to run over the mesh. Things
like autoconfiguration via DHCP, filesharing amongst clients, roaming, mDNS, etc
require a layer 2 mesh. Otherwise you are free to choose.
Regards,
Marek
next prev parent reply other threads:[~2009-12-19 2:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 22:30 [B.A.T.M.A.N.] Mesh network advice Rudolf Meijering
2009-12-19 2:57 ` Marek Lindner [this message]
2009-12-19 11:50 ` RHS Linux User
2009-12-19 17:21 ` Marek Lindner
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=200912191057.00380.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@lists.open-mesh.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