Thread (4 messages) read the whole thread 4 messages, 3 authors, 8d ago

Re: [net-next,v4] selftests/net/openvswitch: add SCTP flow key test

From: Aaron Conole <aconole@redhat.com>
Date: 2026-07-23 02:12:42

Jakub Kicinski [off-list ref] writes:
On Mon, 20 Jul 2026 08:42:10 -0400 Aaron Conole wrote:
quoted
quoted
+# sctp_connect_v4 test
+# - sctp(dst=4443) matches client-to-server INIT
+# - sctp(src=4443) matches server-to-client INIT-ACK
+# - remove flows and verify connection fails, reinstall and recover
+test_sctp_connect_v4() {
+	local t="test_sctp_connect_v4"
+
+	which nc >/dev/null 2>&1 || return $ksft_skip
+	nc --sctp -z 127.0.0.1 1 </dev/null 2>/dev/null || return $ksft_skip  
This can probably be instead::

  nc --help 2>&1 | grep -q -- --sctp || return $ksft_skip

This reads nicer to detect SCTP support in 'nc' binary.
Can we use socat ? nc incompatibilities are hard to deal with.
Works for me
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help