| 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: <20251124-iproute-mptcp-laminar-v1-2-e56437483fdf@kernel.org> Date: Mon, 24 Nov 2025 12:19:22 +0100 From: "Matthieu Baerts (NGI0)" <matttbe@...nel.org> To: Stephen Hemminger <stephen@...workplumber.org> Cc: netdev@...r.kernel.org, MPTCP Linux <mptcp@...ts.linux.dev>, Mat Martineau <martineau@...nel.org>, Geliang Tang <geliang@...nel.org>, "Matthieu Baerts (NGI0)" <matttbe@...nel.org>, David Ahern <dsahern@...nel.org> Subject: [PATCH iproute2-net 2/6] man: mptcp: fix minor typos - 'signaled' -> 'signalled' - 'a implicit' -> 'an implicit' Signed-off-by: Matthieu Baerts (NGI0) <matttbe@...nel.org> --- man/man8/ip-mptcp.8 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/man/man8/ip-mptcp.8 b/man/man8/ip-mptcp.8 index e4a55f6c..500dc671 100644 --- a/man/man8/ip-mptcp.8 +++ b/man/man8/ip-mptcp.8 @@ -156,7 +156,7 @@ ID. .TP .BR signal -The endpoint will be announced/signaled to each peer via an MPTCP ADD_ADDR +The endpoint will be announced/signalled to each peer via an MPTCP ADD_ADDR 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 @@ -207,7 +207,7 @@ is then optional. .BR implicit In some scenarios, an MPTCP .BR subflow -can use a local address mapped by a implicit endpoint created by the +can use a local address mapped by an implicit endpoint created by the in-kernel path manager. Once set, the implicit flag cannot be removed, but other flags can be added to the endpoint. Implicit endpoints cannot be created from user-space. -- 2.51.0
Powered by blists - more mailing lists