From: Matthieu Baerts (NGI0) Date: Sat, 27 Jul 2024 10:10:34 +0000 (+0200) Subject: man: mptcp: 'fullmesh' has to be used with 'subflow' X-Git-Tag: v6.11.0~12 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=640ebc23d8ab6d7bec0a217ae74557dd0eabbfbd;p=thirdparty%2Fiproute2.git man: mptcp: 'fullmesh' has to be used with 'subflow' 'fullmesh' affects the subflow creation, it has to be used with the 'subflow' flag. That's what is enforced on the kernel side. 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 f3d09bab..4c1161fe 100644 --- a/man/man8/ip-mptcp.8 +++ b/man/man8/ip-mptcp.8 @@ -190,7 +190,14 @@ this will behave the same as a plain .BR subflow endpoint. When the peer does announce addresses, each received ADD_ADDR sub-option will trigger creation of an additional subflow to generate a -full mesh topology. +full mesh topology. This +.BR fullmesh +flag should always be used in combination with the +.BR subflow +one to be useful, except for the address used by the initial subflow, +where +.BR subflow +is then optional. .TP .BR implicit