diff options
author | Daniel Mack <daniel@zonque.org> | 2020-06-20 21:39:25 +0200 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2020-06-24 14:39:43 -0700 |
commit | 1ed9ec9b08addbd8d3e36d5f4a652d8590a6ddb7 (patch) | |
tree | c2632f062b28f1274e36faf2c7ba84dbe88ba1f4 /drivers/net | |
parent | 17843655708e1941c0653af3cd61be6948e36f43 (diff) | |
download | linux-stable-1ed9ec9b08addbd8d3e36d5f4a652d8590a6ddb7.tar.gz linux-stable-1ed9ec9b08addbd8d3e36d5f4a652d8590a6ddb7.tar.bz2 linux-stable-1ed9ec9b08addbd8d3e36d5f4a652d8590a6ddb7.zip |
dsa: Allow forwarding of redirected IGMP traffic
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>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net')
0 files changed, 0 insertions, 0 deletions