public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: fuumind <fuumind@openmailbox.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] how well does batman-adv scale
Date: Wed, 26 Apr 2017 18:06:08 +0200	[thread overview]
Message-ID: <1493222768.13937.11.camel@openmailbox.org> (raw)
In-Reply-To: <c63cb109-81bf-4a08-6b29-813a89590170@viisauksena.de>

Hi Jens! 

By 'sufficient power', do you mean processing power to handle overhead
traffic? I'm imagining a network which primarily connects WLANs.

Clouds of batman-adv networks sounds like a good idea. Any idea about
how to implement the interfaces between these clouds? How big should
they be allowed to grow before forming a new cloud?

fuumind


ons 2017-04-26 klockan 17:10 +0200 skrev jens:
> i think this could scale , but you will need sufficient power /
> ethernet
> capacities at the nodes.
> 
> and the biggest problem may be that these endpoints make much noise
> on
> the layer2 level.
> (disovery protocolls and stuff like this)
> 
> you could easily imagine what would happen if you have a layer2
> switch
> with 100000 ports.
> 
> i think that most of the time you will not do this, and implement
> some
> sort of routing between some clouds of batman-adv networks.
> 
> 
> 
> On 26.04.2017 16:20, fuumind wrote:
> > 
> > Hi list!
> > 
> > Been lurking for almost a year on the battlemesh list and recently
> > joined here as well. 
> > 
> > I'm curious about how well batman-adv scales. Would a network of 10
> > 000
> > nodes work well? What about 100 000 nodes or 1 000 000?
> > 
> > Thanks!
> > fuumind
> > 

  parent reply	other threads:[~2017-04-26 16:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26 14:20 [B.A.T.M.A.N.] how well does batman-adv scale fuumind
2017-04-26 15:10 ` jens
2017-04-26 15:53   ` dan
2017-04-26 16:06   ` fuumind [this message]
2017-04-26 16:12     ` dan
2017-04-26 16:05 ` Simon Wunderlich
2017-04-28 10:44   ` fuumind
2017-04-28 12:23     ` Simon Wunderlich
2017-04-28 14:26       ` fuumind
2017-05-02 11:35       ` Adrian Reyer

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=1493222768.13937.11.camel@openmailbox.org \
    --to=fuumind@openmailbox.org \
    --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