diff mbox series

[iproute2-net,5/7] man: mptcp: 'fullmesh' has to be used with 'subflow'

Message ID 20240727-upstream-iproute2-net-20240726-mptcp-man-user-feedback-v1-5-c6398c2014ea@kernel.org (mailing list archive)
State Accepted
Commit 640ebc23d8ab6d7bec0a217ae74557dd0eabbfbd
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 (NGI0) July 27, 2024, 10:10 a.m. UTC 
'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 <martineau@kernel.org>
Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
---
 man/man8/ip-mptcp.8 | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)
diff mbox series

Patch

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