netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolay Aleksandrov <razor@blackwall.org>
To: netdev@vger.kernel.org
Cc: roopa@nvidia.com, kuba@kernel.org,
	bridge@lists.linux-foundation.org,
	Nikolay Aleksandrov <nikolay@nvidia.com>
Subject: [PATCH net-next 03/16] selftests: net: bridge: igmp: check for specific udp ip protocol
Date: Tue, 27 Oct 2020 20:59:21 +0200	[thread overview]
Message-ID: <20201027185934.227040-4-razor@blackwall.org> (raw)
In-Reply-To: <20201027185934.227040-1-razor@blackwall.org>

From: Nikolay Aleksandrov <nikolay@nvidia.com>

We have to specifically check for udp protocol in addition to the mac
address because in IGMPv3 tests group-specific queries will use the same
mac address.

Signed-off-by: Nikolay Aleksandrov <nikolay@nvidia.com>
---
 tools/testing/selftests/net/forwarding/bridge_igmp.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/testing/selftests/net/forwarding/bridge_igmp.sh b/tools/testing/selftests/net/forwarding/bridge_igmp.sh
index 1c19459dbc58..5562aef14c0a 100755
--- a/tools/testing/selftests/net/forwarding/bridge_igmp.sh
+++ b/tools/testing/selftests/net/forwarding/bridge_igmp.sh
@@ -93,7 +93,7 @@ mcast_packet_test()
 	# was received by it or not.
 	tc qdisc add dev $host2_if ingress
 	tc filter add dev $host2_if ingress protocol ip pref 1 handle 101 \
-		flower dst_mac $mac action drop
+		flower ip_proto udp dst_mac $mac action drop
 
 	$MZ $host1_if -c 1 -p 64 -b $mac -A $src_ip -B $ip -t udp "dp=4096,sp=2048" -q
 	sleep 1
-- 
2.25.4


  parent reply	other threads:[~2020-10-27 19:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-27 18:59 [PATCH net-next 00/16] selftests: net: bridge: add tests for IGMPv3 Nikolay Aleksandrov
2020-10-27 18:59 ` [PATCH net-next 01/16] selftests: net: bridge: rename current igmp tests to igmpv2 Nikolay Aleksandrov
2020-10-27 18:59 ` [PATCH net-next 02/16] selftests: net: bridge: igmp: add support for packet source address Nikolay Aleksandrov
2020-10-27 18:59 ` Nikolay Aleksandrov [this message]
2020-10-27 18:59 ` [PATCH net-next 04/16] selftests: net: bridge: igmp: add IGMPv3 entries' state helpers Nikolay Aleksandrov
2020-10-27 18:59 ` [PATCH net-next 05/16] selftests: net: bridge: add tests for igmpv3 is_include and inc -> allow reports Nikolay Aleksandrov
2020-10-27 18:59 ` [PATCH net-next 06/16] selftests: net: bridge: add test for igmpv3 inc -> is_include report Nikolay Aleksandrov
2020-10-27 18:59 ` [PATCH net-next 07/16] selftests: net: bridge: add test for igmpv3 inc -> is_exclude report Nikolay Aleksandrov
2020-10-27 18:59 ` [PATCH net-next 08/16] selftests: net: bridge: add test for igmpv3 inc -> to_exclude report Nikolay Aleksandrov
2020-10-27 18:59 ` [PATCH net-next 09/16] selftests: net: bridge: add test for igmpv3 exc -> allow report Nikolay Aleksandrov
2020-10-27 18:59 ` [PATCH net-next 10/16] selftests: net: bridge: add test for igmpv3 exc -> is_include report Nikolay Aleksandrov
2020-10-27 18:59 ` [PATCH net-next 11/16] selftests: net: bridge: add test for igmpv3 exc -> is_exclude report Nikolay Aleksandrov
2020-10-27 18:59 ` [PATCH net-next 12/16] selftests: net: bridge: add test for igmpv3 exc -> to_exclude report Nikolay Aleksandrov
2020-10-27 18:59 ` [PATCH net-next 13/16] selftests: net: bridge: add test for igmpv3 inc -> block report Nikolay Aleksandrov
2020-10-27 18:59 ` [PATCH net-next 14/16] selftests: net: bridge: add test for igmpv3 exc " Nikolay Aleksandrov
2020-10-27 18:59 ` [PATCH net-next 15/16] selftests: net: bridge: add test for igmpv3 exclude timeout Nikolay Aleksandrov
2020-10-27 18:59 ` [PATCH net-next 16/16] selftests: net: bridge: add test for igmpv3 *,g auto-add Nikolay Aleksandrov
2020-10-30 17:53 ` [PATCH net-next 00/16] selftests: net: bridge: add tests for IGMPv3 Jakub Kicinski

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=20201027185934.227040-4-razor@blackwall.org \
    --to=razor@blackwall.org \
    --cc=bridge@lists.linux-foundation.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@nvidia.com \
    --cc=roopa@nvidia.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).