From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Marek Lindner <mareklindner@neomailbox.ch>
Subject: Re: [PATCH v2] batman-adv: Introduce no noflood mark
Date: Tue, 07 May 2019 10:21:40 +0200 [thread overview]
Message-ID: <1895475.8kFdyZb9vl@bentobox> (raw)
In-Reply-To: <3691280.TvIfeD7Em7@rousseau>
[-- Attachment #1: Type: text/plain, Size: 1491 bytes --]
On Tuesday, 7 May 2019 10:00:18 CEST Marek Lindner wrote:
[...]
> > 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).
>
> As I understand the use-case (Linus correct me if I am wrong): The mark is
> supposed to drop packets that couldn't be $optimized by one of the various
> batman-adv payload traffic optimizations. From outside of batman-adv it would be
> difficult to tell if a broadcast / multicast packet was optimized (think: served
> via DAT cache, sent as unicast, etc) or not.
It should be easy to see in tc whether a packet is transmitted as unicast or
broadcast. It is just a bit check in the destination mac. So it would end up
as a filter somewheere in the hardif tx path which first checks following
before rejecting a packet:
* is it a multicast/broadcast destination address?
- maybe this part isn't even necessary - at least the mcast2unicast stuff
uses batadv_send_skb_unicast
* is it a batman-adv packet?
* is is a batman-adv compat 15 broadcast packet?
* does it have the noflood mark?
This would even allow some fancy stuff like rate limiting or per hardif
behavior. With the problem that there is no package yet which does this in
gluon.
Or am I missing something essential here which is also done in the
batadv_interface_tx path?
And why would we see see stuff which as served via DAT? This is usually not
transmitted on the hardif ports.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-05-07 8:21 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
2019-05-07 8:00 ` Marek Lindner
2019-05-07 8:21 ` Sven Eckelmann [this message]
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=1895475.8kFdyZb9vl@bentobox \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=mareklindner@neomailbox.ch \
/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