From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH v6 1/3] batman-adv: mcast: implement multicast packet reception and forwarding
Date: Fri, 28 Jul 2023 19:52:03 +0200 [thread overview]
Message-ID: <5938380.MhkbZ0Pkbq@sven-l14> (raw)
In-Reply-To: <20230720043556.12163-2-linus.luessing@c0d3.blue>
[-- Attachment #1: Type: text/plain, Size: 1728 bytes --]
On Thursday, 20 July 2023 06:35:53 CEST Linus Lüssing wrote:
> Implement functionality to receive and forward a new TVLV capable
> multicast packet type.
>
> The new batman-adv multicast packet type allows to contain several
> originator destination addresses within a TVLV. Routers on the way will
> potentially split the batman-adv multicast packet and adjust its tracker
> TVLV contents.
>
> Routing decisions are still based on the selected BATMAN IV or BATMAN V
> routing algorithm. So this new batman-adv multicast packet type retains
> the same loop-free properties.
>
> Also a new OGM multicast TVLV flag is introduced to signal to other
> nodes that we are capable of handling a batman-adv multicast packet and
> multicast tracker TVLV. And that all of our hard interfaces have an MTU
> of at least 1280 bytes (IPv6 minimum MTU), as a simple solution for now
> to avoid MTU issues while forwarding.
>
> Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>
> ---
> include/uapi/linux/batadv_packet.h | 45 ++++-
> net/batman-adv/Makefile | 1 +
> net/batman-adv/main.c | 2 +
> net/batman-adv/multicast.c | 48 +++++-
> net/batman-adv/multicast.h | 5 +
> net/batman-adv/multicast_forw.c | 256 +++++++++++++++++++++++++++++
> net/batman-adv/originator.c | 1 +
> net/batman-adv/routing.c | 70 ++++++++
> net/batman-adv/routing.h | 11 ++
> net/batman-adv/soft-interface.c | 12 ++
> net/batman-adv/types.h | 64 ++++++++
> 11 files changed, 504 insertions(+), 11 deletions(-)
> create mode 100644 net/batman-adv/multicast_forw.c
Acked-by: Sven Eckelmann <sven@narfation.org>
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-07-28 17:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 4:35 [PATCH v6 0/3] Implementation of a Stateless Multicast Packet Type Linus Lüssing
2023-07-20 4:35 ` [PATCH v6 1/3] batman-adv: mcast: implement multicast packet reception and forwarding Linus Lüssing
2023-07-28 17:52 ` Sven Eckelmann [this message]
2023-08-14 15:35 ` Simon Wunderlich
2023-08-14 15:53 ` Simon Wunderlich
2023-07-20 4:35 ` [PATCH v6 2/3] batman-adv: mcast: implement multicast packet generation Linus Lüssing
2023-07-29 10:49 ` Sven Eckelmann
2023-07-20 4:35 ` [PATCH v6 3/3] batman-adv: mcast: shrink tracker packet after scrubbing Linus Lüssing
2023-07-29 11:11 ` Sven Eckelmann
2023-08-14 15:56 ` Simon Wunderlich
2023-07-29 11:11 ` [PATCH v6 0/3] Implementation of a Stateless Multicast Packet Type Sven Eckelmann
2023-08-14 16:05 ` Sven Eckelmann
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=5938380.MhkbZ0Pkbq@sven-l14 \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).