public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH v2] batman-adv: Introduce no noflood mark
Date: Tue, 07 May 2019 09:30:46 +0200	[thread overview]
Message-ID: <3693433.LtgH54LjNc@bentobox> (raw)
In-Reply-To: <20190507072821.8147-1-linus.luessing@c0d3.blue>

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

On Tuesday, 7 May 2019 09:28:21 CEST Linus Lüssing wrote:
> This mark prevents a multicast packet being flooded through the whole
> mesh. The advantage of marking certain multicast packets via e.g.
> ebtables instead of dropping is then the following:
> 
> This allows an administrator to let specific multicast packets pass as
> long as they are forwarded to a limited number of nodes only and are
> therefore creating no burdon to unrelated nodes.
> 
> Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>

I still don't see why this has to be implemented in batman-adv and not as an 
external filter (tc-ebpf or something like that).

Kind regards,
	Sven

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

  reply	other threads:[~2019-05-07  7:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-07  7:28 [PATCH v2] batman-adv: Introduce no noflood mark Linus Lüssing
2019-05-07  7:30 ` Sven Eckelmann [this message]
2019-05-07  8:00   ` Marek Lindner
2019-05-07  8:21     ` Sven Eckelmann
2019-05-07 15:17       ` Linus Lüssing
2019-05-07 15:34         ` Linus Lüssing
2019-05-07 15:45         ` Sven Eckelmann
2019-05-14  8:19         ` Linus Lüssing

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=3693433.LtgH54LjNc@bentobox \
    --to=sven@narfation.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