diff mbox series

[iproute2-net,3/7] man: mptcp: 'port' has to be used with 'signal'

Message ID 20240727-upstream-iproute2-net-20240726-mptcp-man-user-feedback-v1-3-c6398c2014ea@kernel.org (mailing list archive)
State Accepted
Commit 8251786f3d8158b4cc0dcc995a6c5fe58c908b6d
Delegated to: Stephen Hemminger
Headers show
Series mptcp: improve man pages to avoid confusions | expand

Checks

Context Check Description
netdev/tree_selection success Clearly marked for net
netdev/apply fail Patch does not apply to net-0

Commit Message

Matthieu Baerts July 27, 2024, 10:10 a.m. UTC 
That's what is enforced by the kernel: the 'port' is used to create a
new listening socket on that port, not to create a new subflow from/to
that port. It then requires the 'signal' flag.

Acked-by: Mat Martineau <martineau@kernel.org>
Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
---
 man/man8/ip-mptcp.8 | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)
diff mbox series

Patch

diff --git a/man/man8/ip-mptcp.8 b/man/man8/ip-mptcp.8
index 2b693564..11df43ce 100644
--- a/man/man8/ip-mptcp.8
+++ b/man/man8/ip-mptcp.8
@@ -133,7 +133,10 @@  is 0.
 When a port number is specified, incoming MPTCP subflows for already
 established MPTCP sockets will be accepted on the specified port, regardless
 the original listener port accepting the first MPTCP subflow and/or
-this peer being actually on the client side.
+this peer being actually on the client side. This option has to be used in
+combination with the
+.BR signal
+flag.
 
 .TP
 .IR IFNAME