From: Matthieu Baerts (NGI0) Date: Sat, 27 Jul 2024 10:10:31 +0000 (+0200) Subject: man: mptcp: clarify 'signal' and 'subflow' flags X-Git-Tag: v6.11.0~15 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=80392875faa810aa31f7f50d6c320370b4bdb8b0;p=thirdparty%2Fiproute2.git man: mptcp: clarify 'signal' and 'subflow' flags According to some bug reports on the MPTCP project, these options might be a bit confusing for some. Mentioning that the 'signal' flag is typically for a server, and the 'subflow' one is typically for a client should help the user knowing in which context which flag should be picked. 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 89fcb64f..2b693564 100644 --- a/man/man8/ip-mptcp.8 +++ b/man/man8/ip-mptcp.8 @@ -150,7 +150,8 @@ is a unique numeric identifier for the given endpoint .TP .BR signal The endpoint will be announced/signaled to each peer via an MPTCP ADD_ADDR -sub-option. Upon reception of an ADD_ADDR sub-option, the peer can try to +sub-option. Typically, a server would be responsible for this. Upon reception of +an ADD_ADDR sub-option, the other peer, typically the client side, can try to create additional subflows, see .BR ADD_ADDR_ACCEPTED_NR. @@ -158,7 +159,8 @@ create additional subflows, see .BR subflow If additional subflow creation is allowed by the MPTCP limits, the MPTCP path manager will try to create an additional subflow using this endpoint -as the source address after the MPTCP connection is established. +as the source address after the MPTCP connection is established. A client would +typically do this. .TP .BR backup