From: Andrew Lunn <andrew@lunn.ch>
To: Daniel Mack <daniel@zonque.org>
Cc: netdev@vger.kernel.org, jcobham@questertangent.com
Subject: Re: [PATCH v2] dsa: Allow forwarding of redirected IGMP traffic
Date: Wed, 24 Jun 2020 16:17:25 +0200 [thread overview]
Message-ID: <20200624141725.GG442307@lunn.ch> (raw)
In-Reply-To: <20200620193925.3166913-1-daniel@zonque.org>
On Sat, Jun 20, 2020 at 09:39:25PM +0200, Daniel Mack wrote:
> The driver for Marvell switches puts all ports in IGMP snooping mode
> which results in all IGMP/MLD frames that ingress on the ports to be
> forwarded to the CPU only.
>
> The bridge code in the kernel can then interpret these frames and act
> upon them, for instance by updating the mdb in the switch to reflect
> multicast memberships of stations connected to the ports. However,
> the IGMP/MLD frames must then also be forwarded to other ports of the
> bridge so external IGMP queriers can track membership reports, and
> external multicast clients can receive query reports from foreign IGMP
> queriers.
>
> Currently, this is impossible as the EDSA tagger sets offload_fwd_mark
> on the skb when it unwraps the tagged frames, and that will make the
> switchdev layer prevent the skb from egressing on any other port of
> the same switch.
>
> To fix that, look at the To_CPU code in the DSA header and make
> forwarding of the frame possible for trapped IGMP packets.
>
> Introduce some #defines for the frame types to make the code a bit more
> comprehensive.
>
> This was tested on a Marvell 88E6352 variant.
>
> Signed-off-by: Daniel Mack <daniel@zonque.org>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Tested-by: Andrew Lunn <andrew@lunn.ch>
The testing was simple regression testing, not IGMP specific.
Andrew
next prev parent reply other threads:[~2020-06-24 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 19:39 [PATCH v2] dsa: Allow forwarding of redirected IGMP traffic Daniel Mack
2020-06-23 7:55 ` Daniel Mack
2020-06-23 12:50 ` Andrew Lunn
2020-06-24 14:17 ` Andrew Lunn [this message]
2020-06-24 21:40 ` David Miller
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=20200624141725.GG442307@lunn.ch \
--to=andrew@lunn.ch \
--cc=daniel@zonque.org \
--cc=jcobham@questertangent.com \
--cc=netdev@vger.kernel.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 NNTP newsgroup(s).