From: Matthieu Baerts (NGI0) Date: Sat, 27 Jul 2024 10:10:32 +0000 (+0200) Subject: man: mptcp: 'port' has to be used with 'signal' X-Git-Tag: v6.11.0~14 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=8251786f3d8158b4cc0dcc995a6c5fe58c908b6d;p=thirdparty%2Fiproute2.git man: mptcp: 'port' has to be used with 'signal' 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 Signed-off-by: Matthieu Baerts (NGI0) Signed-off-by: Stephen Hemminger --- 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