| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <20240727-upstream-iproute2-net-20240726-mptcp-man-user-feedback-v1-5-c6398c2014ea@kernel.org> Date: Sat, 27 Jul 2024 12:10:34 +0200 From: "Matthieu Baerts (NGI0)" <matttbe@...nel.org> To: Stephen Hemminger <stephen@...workplumber.org> Cc: David Ahern <dsahern@...il.com>, netdev@...r.kernel.org, MPTCP Upstream <mptcp@...ts.linux.dev>, Mat Martineau <martineau@...nel.org>, Geliang Tang <geliang@...nel.org>, "Matthieu Baerts (NGI0)" <matttbe@...nel.org> Subject: [PATCH iproute2-net 5/7] 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 <martineau@...nel.org> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@...nel.org> --- man/man8/ip-mptcp.8 | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) 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 -- 2.45.2
Powered by blists - more mailing lists