All of lore.kernel.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.] MAC addresses of loop detect frames in global translation-table
Date: Thu, 01 Jun 2017 10:07:39 +0200	[thread overview]
Message-ID: <2097745.f56AfyDzbC@prime> (raw)
In-Reply-To: <20170531155631.GG29826@otheros>

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

On Wednesday, May 31, 2017 5:56:31 PM CEST Linus Lüssing wrote:
> On Wed, May 31, 2017 at 04:40:56PM +0200, Simon Wunderlich wrote:
> Although, sending these mesh wide sounds like it could create quite
> some overhead? Is this new to BLA2?

Yes, it's new in BLA2. Actually it wasn't in the first BLA2 as well, we merged 
the patch not so long ago.

The loop detection packet is sent every 60 seconds as a broadcast to the LAN. 
It will therefore only end up in the mesh if there are other mesh nodes on the 
same backbone LAN to forward it. Therefore, I think the overhead for community 
networks at least should be minimal.

Cheers,
      Simon

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

  reply	other threads:[~2017-06-01  8:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-31 13:18 [B.A.T.M.A.N.] MAC addresses of loop detect frames in global translation-table Andreas Pape
2017-05-31 13:39 ` Simon Wunderlich
2017-05-31 14:20   ` Linus Lüssing
2017-05-31 14:40     ` Simon Wunderlich
2017-05-31 15:56       ` Linus Lüssing
2017-06-01  8:07         ` Simon Wunderlich [this message]
2017-06-01  6:12     ` [B.A.T.M.A.N.] Antwort: " Andreas Pape
2017-06-01  8:16       ` Simon Wunderlich

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=2097745.f56AfyDzbC@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.