From: Joachim Wiberg <troglobit@gmail.com>
To: Roopa Prabhu <roopa@nvidia.com>,
Nikolay Aleksandrov <razor@blackwall.org>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Joachim Wiberg <troglobit@gmail.com>,
Tobias Waldekranz <tobias@waldekranz.com>,
Vladimir Oltean <vladimir.oltean@nxp.com>
Subject: [PATCH RFC net-next 13/13] selftests: forwarding: verify flood of known mc on mcast_router port
Date: Mon, 11 Apr 2022 15:38:37 +0200 [thread overview]
Message-ID: <20220411133837.318876-14-troglobit@gmail.com> (raw)
In-Reply-To: <20220411133837.318876-1-troglobit@gmail.com>
This test verifies that both known (in mdb) and unknown IP multicast is
forwarded to a mcast_router port.
Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
---
.../selftests/net/forwarding/bridge_mdb.sh | 54 ++++++++++++++++++-
1 file changed, 53 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/net/forwarding/bridge_mdb.sh b/tools/testing/selftests/net/forwarding/bridge_mdb.sh
index 137bc79fd677..3fd7d68bca09 100755
--- a/tools/testing/selftests/net/forwarding/bridge_mdb.sh
+++ b/tools/testing/selftests/net/forwarding/bridge_mdb.sh
@@ -10,13 +10,16 @@
# Verify selective multicast forwarding (strict mdb), when bridge port
# mcast_flood is disabled, of known MAC, IPv4, IPv6 traffic.
#
+# Verify flooding towards mcast_router ports of known IP multicast.
+#
# Note: this test completely disables IPv6 auto-configuration to avoid
# any type of dynamic behavior outside of MLD and IGMP protocols.
# Static IPv6 addresses are used to ensure consistent behavior,
# even in the startup phase when multicast snooping is enabled.
#
-ALL_TESTS="mdb_add_del_test mdb_compat_fwd_test mdb_mac_fwd_test mdb_ip4_fwd_test mdb_ip6_fwd_test"
+ALL_TESTS="mdb_add_del_test mdb_compat_fwd_test mdb_rport_fwd_test \
+ mdb_mac_fwd_test mdb_ip4_fwd_test mdb_ip6_fwd_test"
NUM_NETIFS=6
SRC_PORT="1234"
@@ -246,6 +249,55 @@ mdb_compat_fwd_test()
do_compat_fwd "br0"
}
+#
+# Verify fwd of IP multicast to router ports. A detected multicast
+# router should always receive both known and unknown multicast.
+#
+mdb_rport_fwd_test()
+{
+ pass_grp=$PASS_GRP_IP4
+ fail_grp=$FAIL_GRP_IP4
+ pass_pkt=$PASS_PKT_IP4
+ fail_pkt=$FAIL_PKT_IP4
+ decoy="br0"
+ port=$h1
+ type="IPv4"
+
+ # Disable flooding of unknown multicast, strict MDB forwarding
+ bridge link set dev "$swp1" mcast_flood off
+ bridge link set dev "$swp2" mcast_flood off
+ bridge link set dev "br0" mcast_flood off self
+
+ # Let h2 act as a multicast router
+ ip link set dev "$swp1" type bridge_slave mcast_router 2
+
+ # Static filter only to this decoy port
+ bridge mdb add dev br0 port $decoy grp "$pass_grp"
+ check_err $? "Failed adding multicast group $pass_grp to bridge port $decoy"
+
+ tcpdump_start "$port"
+
+ # Real data we're expecting
+ $MZ -q "$h2" "$pass_pkt"
+ # This should not pass
+ $MZ -q "$h2" "$fail_pkt"
+
+ sleep 1
+ tcpdump_stop "$port"
+
+ tcpdump_show "$port" |grep -q "$src$spt > $pass_grp$dpt"
+ check_err $? "Failed forwarding $type multicast $pass_grp from $h2 to port $port"
+
+ tcpdump_show "$port" |grep -q "$src$spt > $fail_grp$dpt"
+ check_err $? "Failed forwarding $type multicast $fail_grp from $h2 to port $port"
+
+ bridge mdb del dev br0 port br0 grp "$pass_grp"
+ ip link set dev "$swp1" type bridge_slave mcast_router 1
+
+ log_test "MDB forward all $type multicast to multicast router on $port"
+ tcpdump_cleanup "$port"
+}
+
do_mdb_fwd()
{
type=$1
--
2.25.1
prev parent reply other threads:[~2022-04-11 13:39 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 13:38 [PATCH RFC net-next 00/13] net: bridge: forwarding of unknown IPv4/IPv6/MAC BUM traffic Joachim Wiberg
2022-04-11 13:38 ` [PATCH RFC net-next 01/13] net: bridge: add control of bum flooding to bridge itself Joachim Wiberg
2022-04-12 18:27 ` Nikolay Aleksandrov
2022-04-12 20:29 ` Nikolay Aleksandrov
2022-04-13 9:51 ` Joachim Wiberg
2022-04-13 9:58 ` Nikolay Aleksandrov
2022-04-13 10:09 ` Joachim Wiberg
2022-04-11 13:38 ` [PATCH RFC net-next 02/13] net: bridge: rename br_switchdev_set_port_flag() to .._dev_flag() Joachim Wiberg
2022-04-11 13:38 ` [PATCH RFC net-next 03/13] net: bridge: minor refactor of br_setlink() for readability Joachim Wiberg
2022-04-12 18:36 ` Nikolay Aleksandrov
2022-04-13 9:22 ` Joachim Wiberg
2022-04-11 13:38 ` [PATCH RFC net-next 04/13] net: bridge: netlink support for controlling BUM flooding to bridge Joachim Wiberg
2022-04-12 18:24 ` Nikolay Aleksandrov
2022-04-13 10:04 ` Joachim Wiberg
2022-04-11 13:38 ` [PATCH RFC net-next 05/13] selftests: forwarding: add TCPDUMP_EXTRA_FLAGS to lib.sh Joachim Wiberg
2022-04-11 17:20 ` Vladimir Oltean
2022-04-12 7:39 ` Joachim Wiberg
2022-04-11 13:38 ` [PATCH RFC net-next 06/13] selftests: forwarding: multiple instances in tcpdump helper Joachim Wiberg
2022-04-11 17:26 ` Vladimir Oltean
2022-04-11 13:38 ` [PATCH RFC net-next 07/13] selftests: forwarding: new test, verify bridge flood flags Joachim Wiberg
2022-04-11 20:21 ` Vladimir Oltean
2022-04-12 7:55 ` Joachim Wiberg
2022-04-12 13:40 ` Vladimir Oltean
2022-04-11 13:38 ` [PATCH RFC net-next 08/13] net: bridge: avoid classifying unknown multicast as mrouters_only Joachim Wiberg
2022-04-12 13:59 ` Nikolay Aleksandrov
2022-04-12 17:27 ` Joachim Wiberg
2022-04-12 17:37 ` Nikolay Aleksandrov
2022-04-13 8:51 ` Joachim Wiberg
2022-04-13 8:55 ` Nikolay Aleksandrov
2022-04-13 9:00 ` Nikolay Aleksandrov
2022-04-13 10:12 ` Joachim Wiberg
2022-04-11 13:38 ` [PATCH RFC net-next 09/13] selftests: forwarding: rename test groups for next bridge mdb tests Joachim Wiberg
2022-04-11 20:23 ` Vladimir Oltean
2022-04-12 7:57 ` Joachim Wiberg
2022-04-11 13:38 ` [PATCH RFC net-next 10/13] selftests: forwarding: verify flooding of unknown multicast Joachim Wiberg
2022-04-11 13:38 ` [PATCH RFC net-next 11/13] selftests: forwarding: verify strict mdb fwd of known multicast Joachim Wiberg
2022-04-11 13:38 ` [PATCH RFC net-next 12/13] selftests: forwarding: verify strict filtering doesn't leak Joachim Wiberg
2022-04-11 13:38 ` Joachim Wiberg [this message]
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=20220411133837.318876-14-troglobit@gmail.com \
--to=troglobit@gmail.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=tobias@waldekranz.com \
--cc=vladimir.oltean@nxp.com \
/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).