From: Minxi Hou <houminxi@gmail.com>
To: netdev@vger.kernel.org
Cc: aconole@redhat.com, davem@davemloft.net, dev@openvswitch.org,
echaudro@redhat.com, edumazet@google.com, i.maximets@ovn.org,
i.maximets@redhat.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
pabeni@redhat.com, shuah@kernel.org, horms@kernel.org,
Minxi Hou <houminxi@gmail.com>
Subject: [PATCH net-next 1/2] selftests/net/openvswitch: add SCTP flow key test over IPv6
Date: Sat, 22 Aug 2026 22:09:41 -0400 [thread overview]
Message-ID: <20260823020942.3101898-2-houminxi@gmail.com> (raw)
In-Reply-To: <20260823020942.3101898-1-houminxi@gmail.com>
The merged SCTP test covers only IPv4. The IPv6 extraction path
(parse_ipv6hdr walking extension headers, then the proto=132 branch in
key_extract) and the v6 side of the SCTP netlink validation have no
selftest coverage at all, so a regression there would ship silently.
Add test_sctp_connect_v6 mirroring the v4 test: NS/NA forwarding flows
stand in for ARP, and ipv6(proto=132),sctp(dst=4443)/sctp(src=4443)
flows gate the association in the same three phases (flows installed,
flows removed, flows reinstalled). After the association succeeds the
test also pushes a known payload across and verifies the listener
received it, so a flow-key bug that matches handshake packets but
breaks DATA chunks is caught too. Skips when the sctp module is
missing, socat lacks SCTP support, or IPv6 is unavailable; an
association or DATA failure with the flows installed fails the test.
Signed-off-by: Minxi Hou <houminxi@gmail.com>
---
.../selftests/net/openvswitch/openvswitch.sh | 97 ++++++++++++++++++-
1 file changed, 96 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/net/openvswitch/openvswitch.sh b/tools/testing/selftests/net/openvswitch/openvswitch.sh
index a31f7fb6882d..06bd98d80a08 100755
--- a/tools/testing/selftests/net/openvswitch/openvswitch.sh
+++ b/tools/testing/selftests/net/openvswitch/openvswitch.sh
@@ -33,7 +33,8 @@ tests="
action_set set: SET action rewrites fields
trunc trunc: output truncation
icmpv6 icmpv6: ICMPv6 echo type match
- sctp_connect_v4 sctp: SCTP flow key matching
+ sctp_connect_v4 sctp: SCTP flow key matching
+ sctp_connect_v6 sctp6: SCTP flow key matching over IPv6
psample psample: Sampling packets with psample"
info() {
@@ -700,6 +701,100 @@ test_sctp_connect_v4() {
return 0
}
+# sctp_connect_v6 test
+# - sctp(dst=4443) matches client-to-server INIT
+# - sctp(src=4443) matches server-to-client INIT-ACK
+# - icmpv6 NS/NA flows forward neighbour discovery
+# - remove flows and verify connection fails, reinstall and recover
+test_sctp_connect_v6() {
+ local t="test_sctp_connect_v6"
+ local v6="eth_type(0x86dd),ipv6(proto=132)"
+ local payload="SCTP6_DATA_OK"
+ local rxfile="${ovs_base}/${t}/sctp-rx.txt"
+
+ modprobe -q sctp 2>/dev/null || return "$ksft_skip"
+ socat -V 2>&1 | grep -q "define WITH_SCTP" || return "$ksft_skip"
+ [ -e /proc/sys/net/ipv6 ] || return "$ksft_skip"
+
+ sbx_add "$t" || return $?
+ ovs_add_dp "$t" sctp6 || return 1
+
+ info "create namespaces"
+ for ns in client server; do
+ ovs_add_netns_and_veths "$t" "sctp6" "$ns" \
+ "${ns:0:1}0" "${ns:0:1}1" || return 1
+ done
+
+ ip netns exec client ip addr add fd00::1/64 dev c1 nodad
+ ip netns exec client ip link set c1 up
+ ip netns exec server ip addr add fd00::2/64 dev s1 nodad
+ ip netns exec server ip link set s1 up
+
+ # NS/NA forwarding
+ ovs_add_flow "$t" sctp6 \
+ 'in_port(1),eth(),eth_type(0x86dd),ipv6(proto=58),icmpv6()' \
+ '2' || return 1
+ ovs_add_flow "$t" sctp6 \
+ 'in_port(2),eth(),eth_type(0x86dd),ipv6(proto=58),icmpv6()' \
+ '1' || return 1
+
+ # SCTP port matching: dst for request, src for reply
+ ovs_add_flow "$t" sctp6 \
+ "in_port(1),eth(),$v6,sctp(dst=4443)" \
+ '2' || return 1
+ ovs_add_flow "$t" sctp6 \
+ "in_port(2),eth(),$v6,sctp(src=4443)" \
+ '1' || return 1
+
+ ovs_netns_spawn_daemon "$t" "server" \
+ socat -u -t 1 SCTP6-LISTEN:4443,fork \
+ OPEN:"$rxfile",creat,append
+ ovs_wait sctp_eps_has server 4443 || return 1
+
+ info "verify SCTP association with port-keyed flows"
+ ovs_sbx "$t" ip netns exec client \
+ timeout 3 socat -u STDIN "SCTP6-CONNECT:[fd00::2]:4443" </dev/null \
+ || return 1
+
+ info "verify SCTP DATA chunk crosses the datapath"
+ ovs_sbx "$t" ip netns exec client \
+ timeout 3 socat -u STDIN "SCTP6-CONNECT:[fd00::2]:4443" \
+ <<< "$payload" || return 1
+ grep -q "$payload" "$rxfile" 2>/dev/null \
+ || { info "server did not receive SCTP DATA payload"
+ return 1; }
+
+ ovs_del_flows "$t" sctp6
+
+ info "verify connection fails without flows"
+ ovs_add_flow "$t" sctp6 \
+ 'in_port(1),eth(),eth_type(0x86dd),ipv6(proto=58),icmpv6()' \
+ '2' || return 1
+ ovs_add_flow "$t" sctp6 \
+ 'in_port(2),eth(),eth_type(0x86dd),ipv6(proto=58),icmpv6()' \
+ '1' || return 1
+
+ ovs_sbx "$t" ip netns exec client \
+ timeout 3 socat -u STDIN "SCTP6-CONNECT:[fd00::2]:4443" </dev/null \
+ >/dev/null 2>&1 \
+ && { info "connection should fail without flows"
+ return 1; }
+
+ info "reinstall flows and verify recovery"
+ ovs_add_flow "$t" sctp6 \
+ "in_port(1),eth(),$v6,sctp(dst=4443)" \
+ '2' || return 1
+ ovs_add_flow "$t" sctp6 \
+ "in_port(2),eth(),$v6,sctp(src=4443)" \
+ '1' || return 1
+
+ ovs_sbx "$t" ip netns exec client \
+ timeout 3 socat -u STDIN "SCTP6-CONNECT:[fd00::2]:4443" </dev/null \
+ || return 1
+
+ return 0
+}
+
# psample test
# - use psample to observe packets
test_psample() {
base-commit: 91ec2035134982b98fab0609a9fd8480e8217dc1
--
2.55.0
next prev parent reply other threads:[~2026-08-23 2:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 2:09 [PATCH net-next 0/2] selftests: openvswitch: SCTP flow key coverage (IPv6 + NAT) Minxi Hou
2026-08-23 2:09 ` Minxi Hou [this message]
2026-08-23 2:09 ` [PATCH net-next 2/2] selftests/net/openvswitch: add SCTP flow key test across conntrack NAT Minxi Hou
2026-08-25 9:51 ` [PATCH net-next 0/2] selftests: openvswitch: SCTP flow key coverage (IPv6 + NAT) Paolo Abeni
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=20260823020942.3101898-2-houminxi@gmail.com \
--to=houminxi@gmail.com \
--cc=aconole@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=echaudro@redhat.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=i.maximets@ovn.org \
--cc=i.maximets@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@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