From: Matthieu Baerts (NGI0) Date: Sat, 27 Jul 2024 10:10:35 +0000 (+0200) Subject: man: mptcp: clarify the 'ID' parameter X-Git-Tag: v6.11.0~11 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=8145a842736d1b7dc3f15c1b9024ffdb943824df;p=thirdparty%2Fiproute2.git man: mptcp: clarify the 'ID' parameter Explain the range (u8), and the special case for ID 0. The endpoints here are for all the connections, while the ID 0 is a special case per connection, depending on the source address used by the initial subflow. This ID 0 can then not be used for the global endpoints. 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 4c1161fe..e4a55f6c 100644 --- a/man/man8/ip-mptcp.8 +++ b/man/man8/ip-mptcp.8 @@ -148,7 +148,11 @@ expected behavior. .TP .IR ID -is a unique numeric identifier for the given endpoint +is a unique numeric identifier, between 0 and 255, for the given endpoint. It is +not possible to add endpoints with ID 0, because this special ID is reserved for +the initial subflow. For rules linked to the initial subflow, the path-manager +will look at endpoints matching the same address, and port if set, ignoring the +ID. .TP .BR signal