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.org>
Subject: Re: [B.A.T.M.A.N.] global mesh
Date: Tue, 30 Nov 2010 15:42:44 +0100 [thread overview]
Message-ID: <201011301542.45457.lindner_marek@yahoo.de> (raw)
In-Reply-To: <AANLkTikPFR+A5uGZfxB350yD4h0VXuueE+y1g2CcNxS7@mail.gmail.com>
On Tuesday 30 November 2010 07:12:21 Kosta -- A Human Right wrote:
> Can B.A.T.M.A.N. scale to millions of users? What are the limitations
> of B.A.T.M.A.N. in this regard? Where does it excel?
A single mesh cloud consisting of millions of mesh nodes is neither feasible
nor desirable. Each mesh node is announcing itself and routing information
about the nodes "behind it". Obviously, the protocol overhead grows up to a
point where the protocol traffic eats up all available bandwidth.
On the other hand, mesh protocols inherently rely on trust. Each node trusts
its neighbor nodes that they send reliable routing information. As in real
life this trust does not scale either.
Can mesh technology be used to build local inexpensive networks connected to a
"backbone link" (e.g. satellite) to serve millions of users ? Certainly! That
is what villagetelco / Freifunk / open-mesh.com / etc are working on.
Regards,
Marek
next prev parent reply other threads:[~2010-11-30 14:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 16:54 [B.A.T.M.A.N.] global mesh Kosta Grammatis
2010-11-29 21:58 ` Marek Lindner
2010-11-30 6:12 ` Kosta -- A Human Right
2010-11-30 6:36 ` Michael van der Kolff
2010-11-30 14:42 ` Marek Lindner [this message]
2010-11-30 14:55 ` Michael van der Kolff
2010-11-30 15:10 ` Marek Lindner
2010-11-30 15:18 ` Kosta -- A Human Right
2010-11-30 15:52 ` Michael van der Kolff
2010-11-30 15:55 ` Michael van der Kolff
2010-12-02 23:51 ` L. Aaron Kaplan
2010-12-03 10:21 ` RHS Linux User
2010-11-29 23:25 ` Michael van der Kolff
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=201011301542.45457.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--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