public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: fuumind <fuumind@openmailbox.org>
To: Simon Wunderlich <sw@simonwunderlich.de>,
	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: Fri, 28 Apr 2017 16:26:36 +0200	[thread overview]
Message-ID: <1493389596.28193.10.camel@openmailbox.org> (raw)
In-Reply-To: <3080757.qWi1On8dnJ@prime>

Now I get it. :) That makes sense.

Thanks!

fre 2017-04-28 klockan 14:23 +0200 skrev Simon Wunderlich:
> Hi,
> 
> On Friday, April 28, 2017 12:44:08 PM CEST fuumind wrote:
> > 
> > Ok, so clouds of a few hundred nodes would work reasonably well and
> > at
> > the same time keep customization to a minimum.
> Yes
> 
> > 
> > 
> > What makes OSPF a better candidate for interfacing between the
> > clouds?
> > Does it keep a more limited routing table and thus minimize
> > overhead
> > traffic? I haven't been able to figure it out good enough yet.
> The idea would be that you do a layer 3 protocol only on a few
> selected 
> "gateway" nodes of the clouds. Those gateways would forward traffic
> from one 
> cloud to the other, without having the details (and thus not having
> the 
> overhead) of the state of the mesh.
> 
> Which technology is the best is beyond my knowledge.
> 
> Cheers,
>       Simon
> 

  reply	other threads:[~2017-04-28 14:26 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
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 [this message]
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=1493389596.28193.10.camel@openmailbox.org \
    --to=fuumind@openmailbox.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=sw@simonwunderlich.de \
    /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