From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCH v4 1/2] batman-adv: mcast: detect, distribute and maintain multicast router presence
Date: Mon, 10 Jun 2019 07:39:17 +0200 [thread overview]
Message-ID: <4372099.eJBBBCqJL5@sven-edge> (raw)
In-Reply-To: <20190610004535.13725-2-linus.luessing@c0d3.blue>
[-- Attachment #1: Type: text/plain, Size: 1679 bytes --]
On Monday, 10 June 2019 02:45:34 CEST Linus Lüssing wrote:
> If a multicast router is detected then this is signalized via the new
> BATADV_MCAST_WANT_ALL_RTR4 and BATADV_MCAST_WANT_ALL_RTR6
> multicast tvlv flags (which are sent flipped over the wire for backwards
> compatibility - so that old nodes will always have them "set").
This doesn't seem to match the code (see below).
> diff --git a/include/uapi/linux/batadv_packet.h b/include/uapi/linux/batadv_packet.h
> index 4ebc2135..23a43043 100644
> --- a/include/uapi/linux/batadv_packet.h
> +++ b/include/uapi/linux/batadv_packet.h
> @@ -107,12 +107,20 @@ enum batadv_icmp_packettype {
> * @BATADV_MCAST_WANT_ALL_UNSNOOPABLES: we want all packets destined for
> * 224.0.0.0/24 or ff02::1
> * @BATADV_MCAST_WANT_ALL_IPV4: we want all IPv4 multicast packets
> + * (both link-local and routeable ones)
> * @BATADV_MCAST_WANT_ALL_IPV6: we want all IPv6 multicast packets
> + * (both link-local and routable ones)
> + * @BATADV_MCAST_WANT_NO_RTR4: we have no IPv4 multicast router and therefore
> + * only need routeable IPv4 multicast packets we signed up for explicitly
> + * @BATADV_MCAST_WANT_NO_RTR6: we have no IPv6 multicast router and therefore
> + * only need routeable IPv6 multicast packets we signed up for explicitly
> */
> enum batadv_mcast_flags {
> BATADV_MCAST_WANT_ALL_UNSNOOPABLES = 1UL << 0,
> BATADV_MCAST_WANT_ALL_IPV4 = 1UL << 1,
> BATADV_MCAST_WANT_ALL_IPV6 = 1UL << 2,
> + BATADV_MCAST_WANT_NO_RTR4 = 1UL << 3,
> + BATADV_MCAST_WANT_NO_RTR6 = 1UL << 4,
> };
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-06-10 5:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 0:45 [PATCH v4 0/2] batman-adv: Add routeable multicast optimizations Linus Lüssing
2019-06-10 0:45 ` [PATCH v4 1/2] batman-adv: mcast: detect, distribute and maintain multicast router presence Linus Lüssing
2019-06-10 5:39 ` Sven Eckelmann [this message]
2019-06-10 7:24 ` Sven Eckelmann
2019-06-10 23:14 ` Linus Lüssing
2019-06-10 23:45 ` Linus Lüssing
2019-06-11 5:44 ` Sven Eckelmann
2019-06-11 14:12 ` Linus Lüssing
2019-06-10 0:45 ` [PATCH v4 2/2] batman-adv: mcast: apply optimizations for routeable packets, too 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=4372099.eJBBBCqJL5@sven-edge \
--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