111 lines · plain
1.. SPDX-License-Identifier: GPL-2.02 3=====================4MPTCP Sysfs variables5=====================6 7/proc/sys/net/mptcp/* Variables8===============================9 10add_addr_timeout - INTEGER (seconds)11 Set the timeout after which an ADD_ADDR control message will be12 resent to an MPTCP peer that has not acknowledged a previous13 ADD_ADDR message.14 15 The default value matches TCP_RTO_MAX. This is a per-namespace16 sysctl.17 18 Default: 12019 20allow_join_initial_addr_port - BOOLEAN21 Allow peers to send join requests to the IP address and port number used22 by the initial subflow if the value is 1. This controls a flag that is23 sent to the peer at connection time, and whether such join requests are24 accepted or denied.25 26 Joins to addresses advertised with ADD_ADDR are not affected by this27 value.28 29 This is a per-namespace sysctl.30 31 Default: 132 33available_schedulers - STRING34 Shows the available schedulers choices that are registered. More packet35 schedulers may be available, but not loaded.36 37blackhole_timeout - INTEGER (seconds)38 Initial time period in second to disable MPTCP on active MPTCP sockets39 when a MPTCP firewall blackhole issue happens. This time period will40 grow exponentially when more blackhole issues get detected right after41 MPTCP is re-enabled and will reset to the initial value when the42 blackhole issue goes away.43 44 0 to disable the blackhole detection.45 46 Default: 360047 48checksum_enabled - BOOLEAN49 Control whether DSS checksum can be enabled.50 51 DSS checksum can be enabled if the value is nonzero. This is a52 per-namespace sysctl.53 54 Default: 055 56close_timeout - INTEGER (seconds)57 Set the make-after-break timeout: in absence of any close or58 shutdown syscall, MPTCP sockets will maintain the status59 unchanged for such time, after the last subflow removal, before60 moving to TCP_CLOSE.61 62 The default value matches TCP_TIMEWAIT_LEN. This is a per-namespace63 sysctl.64 65 Default: 6066 67enabled - BOOLEAN68 Control whether MPTCP sockets can be created.69 70 MPTCP sockets can be created if the value is 1. This is a71 per-namespace sysctl.72 73 Default: 1 (enabled)74 75pm_type - INTEGER76 Set the default path manager type to use for each new MPTCP77 socket. In-kernel path management will control subflow78 connections and address advertisements according to79 per-namespace values configured over the MPTCP netlink80 API. Userspace path management puts per-MPTCP-connection subflow81 connection decisions and address advertisements under control of82 a privileged userspace program, at the cost of more netlink83 traffic to propagate all of the related events and commands.84 85 This is a per-namespace sysctl.86 87 * 0 - In-kernel path manager88 * 1 - Userspace path manager89 90 Default: 091 92scheduler - STRING93 Select the scheduler of your choice.94 95 Support for selection of different schedulers. This is a per-namespace96 sysctl.97 98 Default: "default"99 100stale_loss_cnt - INTEGER101 The number of MPTCP-level retransmission intervals with no traffic and102 pending outstanding data on a given subflow required to declare it stale.103 The packet scheduler ignores stale subflows.104 A low stale_loss_cnt value allows for fast active-backup switch-over,105 an high value maximize links utilization on edge scenarios e.g. lossy106 link with high BER or peer pausing the data processing.107 108 This is a per-namespace sysctl.109 110 Default: 4111