| Message ID | 20240726-mptcp-user-feedback-v3-5-c6ba1f5fa13e@kernel.org (mailing list archive) |
|---|---|
| State | Superseded, archived |
| Delegated to: | Mat Martineau |
| Headers | show |
| Series | mptcp: guide the user to avoid mistakes | expand |
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
'fullmesh' affects the subflow creation, it has to be used with the 'subflow' flag. That's what is enforced on the kernel side. Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org> --- man/man8/ip-mptcp.8 | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)