According to some bug reports we had in the past, setting the MPTCP
endpoints might be confusing, and the wrong flags might be set.
This series adds missing info for the 'dev' parameter in the manual, but
also clarify a few other parameters.
While at it, a better error message is reported when 'id 0' is used to
'add' or 'change' an endpoint.
Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
---
Changes in v2:
- Drop the patches adding the warnings (Mat).
- Add patches 3 to 7.
- Link to v1: https://lore.kernel.org/r/20240605-mptcp-user-feedback-v1-0-d2dc3b399643@kernel.org
---
Matthieu Baerts (NGI0) (7):
man: mptcp: document 'dev IFNAME'
man: mptcp: clarify 'signal' and 'subflow' flags
man: mptcp: 'port' has to be used with 'signal'
man: mptcp: 'backup' flag also affects outgoing data
man: mptcp: 'fullmesh' has to be used with 'subflow'
man: mptcp: clarify the 'ID' parameter
ip: mptcp: 'id 0' is only for 'del'
ip/ipmptcp.c | 2 ++
man/man8/ip-mptcp.8 | 39 ++++++++++++++++++++++++++++++++-------
2 files changed, 34 insertions(+), 7 deletions(-)
---
base-commit: 554ea3649dd15b19202d7e9791310c3bbb910b34
change-id: 20240605-mptcp-user-feedback-0676915250cb
Best regards,
--
Matthieu Baerts (NGI0) <matttbe@kernel.org>