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

[-- Attachment #1: Type: text/plain, Size: 740 bytes --]

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


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-04-28 12:23 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 [this message]
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=3080757.qWi1On8dnJ@prime \
    --to=sw@simonwunderlich.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