744ee14054
To avoid confusions, it seems better to parse this sysctl parameter as a boolean. We use it as a boolean, no need to parse an integer and bring confusions if we see a value different from 0 and 1, especially with this parameter name: enabled. It seems fine to do this modification because the default value is 1 (enabled). Then the only other interesting value to set is 0 (disabled). All other values would not have changed the default behaviour. Suggested-by: Florian Westphal <fw@strlen.de> Acked-by: Florian Westphal <fw@strlen.de> Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net> Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
27 lines
613 B
ReStructuredText
27 lines
613 B
ReStructuredText
.. SPDX-License-Identifier: GPL-2.0
|
|
|
|
=====================
|
|
MPTCP Sysfs variables
|
|
=====================
|
|
|
|
/proc/sys/net/mptcp/* Variables
|
|
===============================
|
|
|
|
enabled - BOOLEAN
|
|
Control whether MPTCP sockets can be created.
|
|
|
|
MPTCP sockets can be created if the value is 1. This is a
|
|
per-namespace sysctl.
|
|
|
|
Default: 1 (enabled)
|
|
|
|
add_addr_timeout - INTEGER (seconds)
|
|
Set the timeout after which an ADD_ADDR control message will be
|
|
resent to an MPTCP peer that has not acknowledged a previous
|
|
ADD_ADDR message.
|
|
|
|
The default value matches TCP_RTO_MAX. This is a per-namespace
|
|
sysctl.
|
|
|
|
Default: 120
|