1 /proc/sys/net/ipv4/* Variables:
7 Forward Packets between interfaces.
9 This variable is special, its change resets all configuration
10 parameters to their default state (RFC1122 for hosts, RFC1812
13 ip_default_ttl - INTEGER
14 Default value of TTL field (Time To Live) for outgoing (but not
15 forwarded) IP packets. Should be between 1 and 255 inclusive.
16 Default: 64 (as recommended by RFC1700)
18 ip_no_pmtu_disc - INTEGER
19 Disable Path MTU Discovery. If enabled in mode 1 and a
20 fragmentation-required ICMP is received, the PMTU to this
21 destination will be set to min_pmtu (see below). You will need
22 to raise min_pmtu to the smallest interface MTU on your system
23 manually if you want to avoid locally generated fragments.
25 In mode 2 incoming Path MTU Discovery messages will be
26 discarded. Outgoing frames are handled the same as in mode 1,
27 implicitly setting IP_PMTUDISC_DONT on every created socket.
29 Mode 3 is a hardened pmtu discover mode. The kernel will only
30 accept fragmentation-needed errors if the underlying protocol
31 can verify them besides a plain socket lookup. Current
32 protocols for which pmtu events will be honored are TCP, SCTP
33 and DCCP as they verify e.g. the sequence number or the
34 association. This mode should not be enabled globally but is
35 only intended to secure e.g. name servers in namespaces where
36 TCP path mtu must still work but path MTU information of other
37 protocols should be discarded. If enabled globally this mode
38 could break other protocols.
44 default 552 - minimum discovered Path MTU
46 ip_forward_use_pmtu - BOOLEAN
47 By default we don't trust protocol path MTUs while forwarding
48 because they could be easily forged and can lead to unwanted
49 fragmentation by the router.
50 You only need to enable this if you have user-space software
51 which tries to discover path mtus by itself and depends on the
52 kernel honoring this information. This is normally not the
59 fwmark_reflect - BOOLEAN
60 Controls the fwmark of kernel-generated IPv4 reply packets that are not
61 associated with a socket for example, TCP RSTs or ICMP echo replies).
62 If unset, these packets have a fwmark of zero. If set, they have the
63 fwmark of the packet they are replying to.
66 fib_multipath_use_neigh - BOOLEAN
67 Use status of existing neighbor entry when determining nexthop for
68 multipath routes. If disabled, neighbor information is not used and
69 packets could be directed to a failed nexthop. Only valid for kernels
70 built with CONFIG_IP_ROUTE_MULTIPATH enabled.
76 fib_multipath_hash_policy - INTEGER
77 Controls which hash policy to use for multipath routes. Only valid
78 for kernels built with CONFIG_IP_ROUTE_MULTIPATH enabled.
83 2 - Layer 3 or inner Layer 3 if present
85 fib_sync_mem - UNSIGNED INTEGER
86 Amount of dirty memory from fib entries that can be backlogged before
87 synchronize_rcu is forced.
88 Default: 512kB Minimum: 64kB Maximum: 64MB
90 ip_forward_update_priority - INTEGER
91 Whether to update SKB priority from "TOS" field in IPv4 header after it
92 is forwarded. The new SKB priority is mapped from TOS field value
93 according to an rt_tos2priority table (see e.g. man tc-prio).
94 Default: 1 (Update priority.)
96 0 - Do not update priority.
99 route/max_size - INTEGER
100 Maximum number of routes allowed in the kernel. Increase
101 this when using large numbers of interfaces and/or routes.
102 From linux kernel 3.6 onwards, this is deprecated for ipv4
103 as route cache is no longer used.
105 neigh/default/gc_thresh1 - INTEGER
106 Minimum number of entries to keep. Garbage collector will not
107 purge entries if there are fewer than this number.
110 neigh/default/gc_thresh2 - INTEGER
111 Threshold when garbage collector becomes more aggressive about
112 purging entries. Entries older than 5 seconds will be cleared
113 when over this number.
116 neigh/default/gc_thresh3 - INTEGER
117 Maximum number of non-PERMANENT neighbor entries allowed. Increase
118 this when using large numbers of interfaces and when communicating
119 with large numbers of directly-connected peers.
122 neigh/default/unres_qlen_bytes - INTEGER
123 The maximum number of bytes which may be used by packets
124 queued for each unresolved address by other network layers.
126 Setting negative value is meaningless and will return error.
127 Default: SK_WMEM_MAX, (same as net.core.wmem_default).
128 Exact value depends on architecture and kernel options,
129 but should be enough to allow queuing 256 packets
132 neigh/default/unres_qlen - INTEGER
133 The maximum number of packets which may be queued for each
134 unresolved address by other network layers.
135 (deprecated in linux 3.3) : use unres_qlen_bytes instead.
136 Prior to linux 3.3, the default value is 3 which may cause
137 unexpected packet loss. The current default value is calculated
138 according to default value of unres_qlen_bytes and true size of
142 mtu_expires - INTEGER
143 Time, in seconds, that cached PMTU information is kept.
145 min_adv_mss - INTEGER
146 The advertised MSS depends on the first hop route MTU, but will
147 never be lower than this setting.
151 ipfrag_high_thresh - LONG INTEGER
152 Maximum memory used to reassemble IP fragments.
154 ipfrag_low_thresh - LONG INTEGER
155 (Obsolete since linux-4.17)
156 Maximum memory used to reassemble IP fragments before the kernel
157 begins to remove incomplete fragment queues to free up resources.
158 The kernel still accepts new fragments for defragmentation.
160 ipfrag_time - INTEGER
161 Time in seconds to keep an IP fragment in memory.
163 ipfrag_max_dist - INTEGER
164 ipfrag_max_dist is a non-negative integer value which defines the
165 maximum "disorder" which is allowed among fragments which share a
166 common IP source address. Note that reordering of packets is
167 not unusual, but if a large number of fragments arrive from a source
168 IP address while a particular fragment queue remains incomplete, it
169 probably indicates that one or more fragments belonging to that queue
170 have been lost. When ipfrag_max_dist is positive, an additional check
171 is done on fragments before they are added to a reassembly queue - if
172 ipfrag_max_dist (or more) fragments have arrived from a particular IP
173 address between additions to any IP fragment queue using that source
174 address, it's presumed that one or more fragments in the queue are
175 lost. The existing fragment queue will be dropped, and a new one
176 started. An ipfrag_max_dist value of zero disables this check.
178 Using a very small value, e.g. 1 or 2, for ipfrag_max_dist can
179 result in unnecessarily dropping fragment queues when normal
180 reordering of packets occurs, which could lead to poor application
181 performance. Using a very large value, e.g. 50000, increases the
182 likelihood of incorrectly reassembling IP fragments that originate
183 from different IP datagrams, which could result in data corruption.
188 inet_peer_threshold - INTEGER
189 The approximate size of the storage. Starting from this threshold
190 entries will be thrown aggressively. This threshold also determines
191 entries' time-to-live and time intervals between garbage collection
192 passes. More entries, less time-to-live, less GC interval.
194 inet_peer_minttl - INTEGER
195 Minimum time-to-live of entries. Should be enough to cover fragment
196 time-to-live on the reassembling side. This minimum time-to-live is
197 guaranteed if the pool size is less than inet_peer_threshold.
200 inet_peer_maxttl - INTEGER
201 Maximum time-to-live of entries. Unused entries will expire after
202 this period of time if there is no memory pressure on the pool (i.e.
203 when the number of entries in the pool is very small).
209 Limit of socket listen() backlog, known in userspace as SOMAXCONN.
210 Defaults to 4096. (Was 128 before linux-5.4)
211 See also tcp_max_syn_backlog for additional tuning for TCP sockets.
213 tcp_abort_on_overflow - BOOLEAN
214 If listening service is too slow to accept new connections,
215 reset them. Default state is FALSE. It means that if overflow
216 occurred due to a burst, connection will recover. Enable this
217 option _only_ if you are really sure that listening daemon
218 cannot be tuned to accept connections faster. Enabling this
219 option can harm clients of your server.
221 tcp_adv_win_scale - INTEGER
222 Count buffering overhead as bytes/2^tcp_adv_win_scale
223 (if tcp_adv_win_scale > 0) or bytes-bytes/2^(-tcp_adv_win_scale),
225 Possible values are [-31, 31], inclusive.
228 tcp_allowed_congestion_control - STRING
229 Show/set the congestion control choices available to non-privileged
230 processes. The list is a subset of those listed in
231 tcp_available_congestion_control.
232 Default is "reno" and the default setting (tcp_congestion_control).
234 tcp_app_win - INTEGER
235 Reserve max(window/2^tcp_app_win, mss) of window for application
236 buffer. Value 0 is special, it means that nothing is reserved.
239 tcp_autocorking - BOOLEAN
240 Enable TCP auto corking :
241 When applications do consecutive small write()/sendmsg() system calls,
242 we try to coalesce these small writes as much as possible, to lower
243 total amount of sent packets. This is done if at least one prior
244 packet for the flow is waiting in Qdisc queues or device transmit
245 queue. Applications can still use TCP_CORK for optimal behavior
246 when they know how/when to uncork their sockets.
249 tcp_available_congestion_control - STRING
250 Shows the available congestion control choices that are registered.
251 More congestion control algorithms may be available as modules,
254 tcp_base_mss - INTEGER
255 The initial value of search_low to be used by the packetization layer
256 Path MTU discovery (MTU probing). If MTU probing is enabled,
257 this is the initial MSS used by the connection.
259 tcp_mtu_probe_floor - INTEGER
260 If MTU probing is enabled this caps the minimum MSS used for search_low
265 tcp_min_snd_mss - INTEGER
266 TCP SYN and SYNACK messages usually advertise an ADVMSS option,
267 as described in RFC 1122 and RFC 6691.
268 If this ADVMSS option is smaller than tcp_min_snd_mss,
269 it is silently capped to tcp_min_snd_mss.
271 Default : 48 (at least 8 bytes of payload per segment)
273 tcp_congestion_control - STRING
274 Set the congestion control algorithm to be used for new
275 connections. The algorithm "reno" is always available, but
276 additional choices may be available based on kernel configuration.
277 Default is set as part of kernel configuration.
278 For passive connections, the listener congestion control choice
280 [see setsockopt(listenfd, SOL_TCP, TCP_CONGESTION, "name" ...) ]
283 Allows TCP to send "duplicate" SACKs.
285 tcp_early_retrans - INTEGER
286 Tail loss probe (TLP) converts RTOs occurring due to tail
287 losses into fast recovery (draft-ietf-tcpm-rack). Note that
288 TLP requires RACK to function properly (see tcp_recovery below)
295 Control use of Explicit Congestion Notification (ECN) by TCP.
296 ECN is used only when both ends of the TCP connection indicate
297 support for it. This feature is useful in avoiding losses due
298 to congestion by allowing supporting routers to signal
299 congestion before having to drop packets.
301 0 Disable ECN. Neither initiate nor accept ECN.
302 1 Enable ECN when requested by incoming connections and
303 also request ECN on outgoing connection attempts.
304 2 Enable ECN when requested by incoming connections
305 but do not request ECN on outgoing connections.
308 tcp_ecn_fallback - BOOLEAN
309 If the kernel detects that ECN connection misbehaves, enable fall
310 back to non-ECN. Currently, this knob implements the fallback
311 from RFC3168, section 6.1.1.1., but we reserve that in future,
312 additional detection mechanisms could be implemented under this
313 knob. The value is not used, if tcp_ecn or per route (or congestion
314 control) ECN settings are disabled.
315 Default: 1 (fallback enabled)
318 This is a legacy option, it has no effect anymore.
320 tcp_fin_timeout - INTEGER
321 The length of time an orphaned (no longer referenced by any
322 application) connection will remain in the FIN_WAIT_2 state
323 before it is aborted at the local end. While a perfectly
324 valid "receive only" state for an un-orphaned connection, an
325 orphaned connection in FIN_WAIT_2 state could otherwise wait
326 forever for the remote to close its end of the connection.
331 Enables Forward RTO-Recovery (F-RTO) defined in RFC5682.
332 F-RTO is an enhanced recovery algorithm for TCP retransmission
333 timeouts. It is particularly beneficial in networks where the
334 RTT fluctuates (e.g., wireless). F-RTO is sender-side only
335 modification. It does not require any support from the peer.
337 By default it's enabled with a non-zero value. 0 disables F-RTO.
339 tcp_fwmark_accept - BOOLEAN
340 If set, incoming connections to listening sockets that do not have a
341 socket mark will set the mark of the accepting socket to the fwmark of
342 the incoming SYN packet. This will cause all packets on that connection
343 (starting from the first SYNACK) to be sent with that fwmark. The
344 listening socket's mark is unchanged. Listening sockets that already
345 have a fwmark set via setsockopt(SOL_SOCKET, SO_MARK, ...) are
350 tcp_invalid_ratelimit - INTEGER
351 Limit the maximal rate for sending duplicate acknowledgments
352 in response to incoming TCP packets that are for an existing
353 connection but that are invalid due to any of these reasons:
355 (a) out-of-window sequence number,
356 (b) out-of-window acknowledgment number, or
357 (c) PAWS (Protection Against Wrapped Sequence numbers) check failure
359 This can help mitigate simple "ack loop" DoS attacks, wherein
360 a buggy or malicious middlebox or man-in-the-middle can
361 rewrite TCP header fields in manner that causes each endpoint
362 to think that the other is sending invalid TCP segments, thus
363 causing each side to send an unterminating stream of duplicate
364 acknowledgments for invalid segments.
366 Using 0 disables rate-limiting of dupacks in response to
367 invalid segments; otherwise this value specifies the minimal
368 space between sending such dupacks, in milliseconds.
370 Default: 500 (milliseconds).
372 tcp_keepalive_time - INTEGER
373 How often TCP sends out keepalive messages when keepalive is enabled.
376 tcp_keepalive_probes - INTEGER
377 How many keepalive probes TCP sends out, until it decides that the
378 connection is broken. Default value: 9.
380 tcp_keepalive_intvl - INTEGER
381 How frequently the probes are send out. Multiplied by
382 tcp_keepalive_probes it is time to kill not responding connection,
383 after probes started. Default value: 75sec i.e. connection
384 will be aborted after ~11 minutes of retries.
386 tcp_l3mdev_accept - BOOLEAN
387 Enables child sockets to inherit the L3 master device index.
388 Enabling this option allows a "global" listen socket to work
389 across L3 master domains (e.g., VRFs) with connected sockets
390 derived from the listen socket to be bound to the L3 domain in
391 which the packets originated. Only valid when the kernel was
392 compiled with CONFIG_NET_L3_MASTER_DEV.
393 Default: 0 (disabled)
395 tcp_low_latency - BOOLEAN
396 This is a legacy option, it has no effect anymore.
398 tcp_max_orphans - INTEGER
399 Maximal number of TCP sockets not attached to any user file handle,
400 held by system. If this number is exceeded orphaned connections are
401 reset immediately and warning is printed. This limit exists
402 only to prevent simple DoS attacks, you _must_ not rely on this
403 or lower the limit artificially, but rather increase it
404 (probably, after increasing installed memory),
405 if network conditions require more than default value,
406 and tune network services to linger and kill such states
407 more aggressively. Let me to remind again: each orphan eats
408 up to ~64K of unswappable memory.
410 tcp_max_syn_backlog - INTEGER
411 Maximal number of remembered connection requests (SYN_RECV),
412 which have not received an acknowledgment from connecting client.
413 This is a per-listener limit.
414 The minimal value is 128 for low memory machines, and it will
415 increase in proportion to the memory of machine.
416 If server suffers from overload, try increasing this number.
417 Remember to also check /proc/sys/net/core/somaxconn
418 A SYN_RECV request socket consumes about 304 bytes of memory.
420 tcp_max_tw_buckets - INTEGER
421 Maximal number of timewait sockets held by system simultaneously.
422 If this number is exceeded time-wait socket is immediately destroyed
423 and warning is printed. This limit exists only to prevent
424 simple DoS attacks, you _must_ not lower the limit artificially,
425 but rather increase it (probably, after increasing installed memory),
426 if network conditions require more than default value.
428 tcp_mem - vector of 3 INTEGERs: min, pressure, max
429 min: below this number of pages TCP is not bothered about its
432 pressure: when amount of memory allocated by TCP exceeds this number
433 of pages, TCP moderates its memory consumption and enters memory
434 pressure mode, which is exited when memory consumption falls
437 max: number of pages allowed for queueing by all TCP sockets.
439 Defaults are calculated at boot time from amount of available
442 tcp_min_rtt_wlen - INTEGER
443 The window length of the windowed min filter to track the minimum RTT.
444 A shorter window lets a flow more quickly pick up new (higher)
445 minimum RTT when it is moved to a longer path (e.g., due to traffic
446 engineering). A longer window makes the filter more resistant to RTT
447 inflations such as transient congestion. The unit is seconds.
448 Possible values: 0 - 86400 (1 day)
451 tcp_moderate_rcvbuf - BOOLEAN
452 If set, TCP performs receive buffer auto-tuning, attempting to
453 automatically size the buffer (no greater than tcp_rmem[2]) to
454 match the size required by the path for full throughput. Enabled by
457 tcp_mtu_probing - INTEGER
458 Controls TCP Packetization-Layer Path MTU Discovery. Takes three
461 1 - Disabled by default, enabled when an ICMP black hole detected
462 2 - Always enabled, use initial MSS of tcp_base_mss.
464 tcp_probe_interval - UNSIGNED INTEGER
465 Controls how often to start TCP Packetization-Layer Path MTU
466 Discovery reprobe. The default is reprobing every 10 minutes as
469 tcp_probe_threshold - INTEGER
470 Controls when TCP Packetization-Layer Path MTU Discovery probing
471 will stop in respect to the width of search range in bytes. Default
474 tcp_no_metrics_save - BOOLEAN
475 By default, TCP saves various connection metrics in the route cache
476 when the connection closes, so that connections established in the
477 near future can use these to set initial conditions. Usually, this
478 increases overall performance, but may sometimes cause performance
479 degradation. If set, TCP will not cache metrics on closing
482 tcp_no_ssthresh_metrics_save - BOOLEAN
483 Controls whether TCP saves ssthresh metrics in the route cache.
484 Default is 1, which disables ssthresh metrics.
486 tcp_orphan_retries - INTEGER
487 This value influences the timeout of a locally closed TCP connection,
488 when RTO retransmissions remain unacknowledged.
489 See tcp_retries2 for more details.
491 The default value is 8.
492 If your machine is a loaded WEB server,
493 you should think about lowering this value, such sockets
494 may consume significant resources. Cf. tcp_max_orphans.
496 tcp_recovery - INTEGER
497 This value is a bitmap to enable various experimental loss recovery
500 RACK: 0x1 enables the RACK loss detection for fast detection of lost
501 retransmissions and tail drops. It also subsumes and disables
502 RFC6675 recovery for SACK connections.
503 RACK: 0x2 makes RACK's reordering window static (min_rtt/4).
504 RACK: 0x4 disables RACK's DUPACK threshold heuristic
508 tcp_reordering - INTEGER
509 Initial reordering level of packets in a TCP stream.
510 TCP stack can then dynamically adjust flow reordering level
511 between this initial value and tcp_max_reordering
514 tcp_max_reordering - INTEGER
515 Maximal reordering level of packets in a TCP stream.
516 300 is a fairly conservative value, but you might increase it
517 if paths are using per packet load balancing (like bonding rr mode)
520 tcp_retrans_collapse - BOOLEAN
521 Bug-to-bug compatibility with some broken printers.
522 On retransmit try to send bigger packets to work around bugs in
525 tcp_retries1 - INTEGER
526 This value influences the time, after which TCP decides, that
527 something is wrong due to unacknowledged RTO retransmissions,
528 and reports this suspicion to the network layer.
529 See tcp_retries2 for more details.
531 RFC 1122 recommends at least 3 retransmissions, which is the
534 tcp_retries2 - INTEGER
535 This value influences the timeout of an alive TCP connection,
536 when RTO retransmissions remain unacknowledged.
537 Given a value of N, a hypothetical TCP connection following
538 exponential backoff with an initial RTO of TCP_RTO_MIN would
539 retransmit N times before killing the connection at the (N+1)th RTO.
541 The default value of 15 yields a hypothetical timeout of 924.6
542 seconds and is a lower bound for the effective timeout.
543 TCP will effectively time out at the first RTO which exceeds the
544 hypothetical timeout.
546 RFC 1122 recommends at least 100 seconds for the timeout,
547 which corresponds to a value of at least 8.
549 tcp_rfc1337 - BOOLEAN
550 If set, the TCP stack behaves conforming to RFC1337. If unset,
551 we are not conforming to RFC, but prevent TCP TIME_WAIT
555 tcp_rmem - vector of 3 INTEGERs: min, default, max
556 min: Minimal size of receive buffer used by TCP sockets.
557 It is guaranteed to each TCP socket, even under moderate memory
561 default: initial size of receive buffer used by TCP sockets.
562 This value overrides net.core.rmem_default used by other protocols.
563 Default: 87380 bytes. This value results in window of 65535 with
564 default setting of tcp_adv_win_scale and tcp_app_win:0 and a bit
565 less for default tcp_app_win. See below about these variables.
567 max: maximal size of receive buffer allowed for automatically
568 selected receiver buffers for TCP socket. This value does not override
569 net.core.rmem_max. Calling setsockopt() with SO_RCVBUF disables
570 automatic tuning of that socket's receive buffer size, in which
571 case this value is ignored.
572 Default: between 87380B and 6MB, depending on RAM size.
575 Enable select acknowledgments (SACKS).
577 tcp_comp_sack_delay_ns - LONG INTEGER
578 TCP tries to reduce number of SACK sent, using a timer
579 based on 5% of SRTT, capped by this sysctl, in nano seconds.
580 The default is 1ms, based on TSO autosizing period.
582 Default : 1,000,000 ns (1 ms)
584 tcp_comp_sack_nr - INTEGER
585 Max number of SACK that can be compressed.
586 Using 0 disables SACK compression.
590 tcp_slow_start_after_idle - BOOLEAN
591 If set, provide RFC2861 behavior and time out the congestion
592 window after an idle period. An idle period is defined at
593 the current RTO. If unset, the congestion window will not
594 be timed out after an idle period.
598 Use the Host requirements interpretation of the TCP urgent pointer field.
599 Most hosts use the older BSD interpretation, so if you turn this on
600 Linux might not communicate correctly with them.
603 tcp_synack_retries - INTEGER
604 Number of times SYNACKs for a passive TCP connection attempt will
605 be retransmitted. Should not be higher than 255. Default value
606 is 5, which corresponds to 31seconds till the last retransmission
607 with the current initial RTO of 1second. With this the final timeout
608 for a passive TCP connection will happen after 63seconds.
610 tcp_syncookies - INTEGER
611 Only valid when the kernel was compiled with CONFIG_SYN_COOKIES
612 Send out syncookies when the syn backlog queue of a socket
613 overflows. This is to prevent against the common 'SYN flood attack'
616 Note, that syncookies is fallback facility.
617 It MUST NOT be used to help highly loaded servers to stand
618 against legal connection rate. If you see SYN flood warnings
619 in your logs, but investigation shows that they occur
620 because of overload with legal connections, you should tune
621 another parameters until this warning disappear.
622 See: tcp_max_syn_backlog, tcp_synack_retries, tcp_abort_on_overflow.
624 syncookies seriously violate TCP protocol, do not allow
625 to use TCP extensions, can result in serious degradation
626 of some services (f.e. SMTP relaying), visible not by you,
627 but your clients and relays, contacting you. While you see
628 SYN flood warnings in logs not being really flooded, your server
629 is seriously misconfigured.
631 If you want to test which effects syncookies have to your
632 network connections you can set this knob to 2 to enable
633 unconditionally generation of syncookies.
635 tcp_fastopen - INTEGER
636 Enable TCP Fast Open (RFC7413) to send and accept data in the opening
639 The client support is enabled by flag 0x1 (on by default). The client
640 then must use sendmsg() or sendto() with the MSG_FASTOPEN flag,
641 rather than connect() to send data in SYN.
643 The server support is enabled by flag 0x2 (off by default). Then
644 either enable for all listeners with another flag (0x400) or
645 enable individual listeners via TCP_FASTOPEN socket option with
646 the option value being the length of the syn-data backlog.
648 The values (bitmap) are
649 0x1: (client) enables sending data in the opening SYN on the client.
650 0x2: (server) enables the server support, i.e., allowing data in
651 a SYN packet to be accepted and passed to the
652 application before 3-way handshake finishes.
653 0x4: (client) send data in the opening SYN regardless of cookie
654 availability and without a cookie option.
655 0x200: (server) accept data-in-SYN w/o any cookie option present.
656 0x400: (server) enable all listeners to support Fast Open by
657 default without explicit TCP_FASTOPEN socket option.
661 Note that that additional client or server features are only
662 effective if the basic support (0x1 and 0x2) are enabled respectively.
664 tcp_fastopen_blackhole_timeout_sec - INTEGER
665 Initial time period in second to disable Fastopen on active TCP sockets
666 when a TFO firewall blackhole issue happens.
667 This time period will grow exponentially when more blackhole issues
668 get detected right after Fastopen is re-enabled and will reset to
669 initial value when the blackhole issue goes away.
670 0 to disable the blackhole detection.
671 By default, it is set to 1hr.
673 tcp_fastopen_key - list of comma separated 32-digit hexadecimal INTEGERs
674 The list consists of a primary key and an optional backup key. The
675 primary key is used for both creating and validating cookies, while the
676 optional backup key is only used for validating cookies. The purpose of
677 the backup key is to maximize TFO validation when keys are rotated.
679 A randomly chosen primary key may be configured by the kernel if
680 the tcp_fastopen sysctl is set to 0x400 (see above), or if the
681 TCP_FASTOPEN setsockopt() optname is set and a key has not been
682 previously configured via sysctl. If keys are configured via
683 setsockopt() by using the TCP_FASTOPEN_KEY optname, then those
684 per-socket keys will be used instead of any keys that are specified via
687 A key is specified as 4 8-digit hexadecimal integers which are separated
688 by a '-' as: xxxxxxxx-xxxxxxxx-xxxxxxxx-xxxxxxxx. Leading zeros may be
689 omitted. A primary and a backup key may be specified by separating them
690 by a comma. If only one key is specified, it becomes the primary key and
691 any previously configured backup keys are removed.
693 tcp_syn_retries - INTEGER
694 Number of times initial SYNs for an active TCP connection attempt
695 will be retransmitted. Should not be higher than 127. Default value
696 is 6, which corresponds to 63seconds till the last retransmission
697 with the current initial RTO of 1second. With this the final timeout
698 for an active TCP connection attempt will happen after 127seconds.
700 tcp_timestamps - INTEGER
701 Enable timestamps as defined in RFC1323.
703 1: Enable timestamps as defined in RFC1323 and use random offset for
704 each connection rather than only using the current time.
705 2: Like 1, but without random offsets.
708 tcp_min_tso_segs - INTEGER
709 Minimal number of segments per TSO frame.
710 Since linux-3.12, TCP does an automatic sizing of TSO frames,
711 depending on flow rate, instead of filling 64Kbytes packets.
712 For specific usages, it's possible to force TCP to build big
713 TSO frames. Note that TCP stack might split too big TSO packets
714 if available window is too small.
717 tcp_pacing_ss_ratio - INTEGER
718 sk->sk_pacing_rate is set by TCP stack using a ratio applied
719 to current rate. (current_rate = cwnd * mss / srtt)
720 If TCP is in slow start, tcp_pacing_ss_ratio is applied
721 to let TCP probe for bigger speeds, assuming cwnd can be
722 doubled every other RTT.
725 tcp_pacing_ca_ratio - INTEGER
726 sk->sk_pacing_rate is set by TCP stack using a ratio applied
727 to current rate. (current_rate = cwnd * mss / srtt)
728 If TCP is in congestion avoidance phase, tcp_pacing_ca_ratio
729 is applied to conservatively probe for bigger throughput.
732 tcp_tso_win_divisor - INTEGER
733 This allows control over what percentage of the congestion window
734 can be consumed by a single TSO frame.
735 The setting of this parameter is a choice between burstiness and
736 building larger TSO frames.
739 tcp_tw_reuse - INTEGER
740 Enable reuse of TIME-WAIT sockets for new connections when it is
741 safe from protocol viewpoint.
744 2 - enable for loopback traffic only
745 It should not be changed without advice/request of technical
749 tcp_window_scaling - BOOLEAN
750 Enable window scaling as defined in RFC1323.
752 tcp_wmem - vector of 3 INTEGERs: min, default, max
753 min: Amount of memory reserved for send buffers for TCP sockets.
754 Each TCP socket has rights to use it due to fact of its birth.
757 default: initial size of send buffer used by TCP sockets. This
758 value overrides net.core.wmem_default used by other protocols.
759 It is usually lower than net.core.wmem_default.
762 max: Maximal amount of memory allowed for automatically tuned
763 send buffers for TCP sockets. This value does not override
764 net.core.wmem_max. Calling setsockopt() with SO_SNDBUF disables
765 automatic tuning of that socket's send buffer size, in which case
766 this value is ignored.
767 Default: between 64K and 4MB, depending on RAM size.
769 tcp_notsent_lowat - UNSIGNED INTEGER
770 A TCP socket can control the amount of unsent bytes in its write queue,
771 thanks to TCP_NOTSENT_LOWAT socket option. poll()/select()/epoll()
772 reports POLLOUT events if the amount of unsent bytes is below a per
773 socket value, and if the write queue is not full. sendmsg() will
774 also not add new buffers if the limit is hit.
776 This global variable controls the amount of unsent data for
777 sockets not using TCP_NOTSENT_LOWAT. For these sockets, a change
778 to the global variable has immediate effect.
780 Default: UINT_MAX (0xFFFFFFFF)
782 tcp_workaround_signed_windows - BOOLEAN
783 If set, assume no receipt of a window scaling option means the
784 remote TCP is broken and treats the window as a signed quantity.
785 If unset, assume the remote TCP is not broken even if we do
786 not receive a window scaling option from them.
789 tcp_thin_linear_timeouts - BOOLEAN
790 Enable dynamic triggering of linear timeouts for thin streams.
791 If set, a check is performed upon retransmission by timeout to
792 determine if the stream is thin (less than 4 packets in flight).
793 As long as the stream is found to be thin, up to 6 linear
794 timeouts may be performed before exponential backoff mode is
795 initiated. This improves retransmission latency for
796 non-aggressive thin streams, often found to be time-dependent.
797 For more information on thin streams, see
798 Documentation/networking/tcp-thin.txt
801 tcp_limit_output_bytes - INTEGER
802 Controls TCP Small Queue limit per tcp socket.
803 TCP bulk sender tends to increase packets in flight until it
804 gets losses notifications. With SNDBUF autotuning, this can
805 result in a large amount of packets queued on the local machine
806 (e.g.: qdiscs, CPU backlog, or device) hurting latency of other
807 flows, for typical pfifo_fast qdiscs. tcp_limit_output_bytes
808 limits the number of bytes on qdisc or device to reduce artificial
809 RTT/cwnd and reduce bufferbloat.
810 Default: 1048576 (16 * 65536)
812 tcp_challenge_ack_limit - INTEGER
813 Limits number of Challenge ACK sent per second, as recommended
814 in RFC 5961 (Improving TCP's Robustness to Blind In-Window Attacks)
817 tcp_rx_skb_cache - BOOLEAN
818 Controls a per TCP socket cache of one skb, that might help
819 performance of some workloads. This might be dangerous
820 on systems with a lot of TCP sockets, since it increases
823 Default: 0 (disabled)
827 udp_l3mdev_accept - BOOLEAN
828 Enabling this option allows a "global" bound socket to work
829 across L3 master domains (e.g., VRFs) with packets capable of
830 being received regardless of the L3 domain in which they
831 originated. Only valid when the kernel was compiled with
832 CONFIG_NET_L3_MASTER_DEV.
833 Default: 0 (disabled)
835 udp_mem - vector of 3 INTEGERs: min, pressure, max
836 Number of pages allowed for queueing by all UDP sockets.
838 min: Below this number of pages UDP is not bothered about its
839 memory appetite. When amount of memory allocated by UDP exceeds
840 this number, UDP starts to moderate memory usage.
842 pressure: This value was introduced to follow format of tcp_mem.
844 max: Number of pages allowed for queueing by all UDP sockets.
846 Default is calculated at boot time from amount of available memory.
848 udp_rmem_min - INTEGER
849 Minimal size of receive buffer used by UDP sockets in moderation.
850 Each UDP socket is able to use the size for receiving data, even if
851 total pages of UDP sockets exceed udp_mem pressure. The unit is byte.
854 udp_wmem_min - INTEGER
855 Minimal size of send buffer used by UDP sockets in moderation.
856 Each UDP socket is able to use the size for sending data, even if
857 total pages of UDP sockets exceed udp_mem pressure. The unit is byte.
862 raw_l3mdev_accept - BOOLEAN
863 Enabling this option allows a "global" bound socket to work
864 across L3 master domains (e.g., VRFs) with packets capable of
865 being received regardless of the L3 domain in which they
866 originated. Only valid when the kernel was compiled with
867 CONFIG_NET_L3_MASTER_DEV.
872 cipso_cache_enable - BOOLEAN
873 If set, enable additions to and lookups from the CIPSO label mapping
874 cache. If unset, additions are ignored and lookups always result in a
875 miss. However, regardless of the setting the cache is still
876 invalidated when required when means you can safely toggle this on and
877 off and the cache will always be "safe".
880 cipso_cache_bucket_size - INTEGER
881 The CIPSO label cache consists of a fixed size hash table with each
882 hash bucket containing a number of cache entries. This variable limits
883 the number of entries in each hash bucket; the larger the value the
884 more CIPSO label mappings that can be cached. When the number of
885 entries in a given hash bucket reaches this limit adding new entries
886 causes the oldest entry in the bucket to be removed to make room.
889 cipso_rbm_optfmt - BOOLEAN
890 Enable the "Optimized Tag 1 Format" as defined in section 3.4.2.6 of
891 the CIPSO draft specification (see Documentation/netlabel for details).
892 This means that when set the CIPSO tag will be padded with empty
893 categories in order to make the packet data 32-bit aligned.
896 cipso_rbm_structvalid - BOOLEAN
897 If set, do a very strict check of the CIPSO option when
898 ip_options_compile() is called. If unset, relax the checks done during
899 ip_options_compile(). Either way is "safe" as errors are caught else
900 where in the CIPSO processing code but setting this to 0 (False) should
901 result in less work (i.e. it should be faster) but could cause problems
902 with other implementations that require strict checking.
907 ip_local_port_range - 2 INTEGERS
908 Defines the local port range that is used by TCP and UDP to
909 choose the local port. The first number is the first, the
910 second the last local port number.
911 If possible, it is better these numbers have different parity
912 (one even and one odd value).
913 Must be greater than or equal to ip_unprivileged_port_start.
914 The default values are 32768 and 60999 respectively.
916 ip_local_reserved_ports - list of comma separated ranges
917 Specify the ports which are reserved for known third-party
918 applications. These ports will not be used by automatic port
919 assignments (e.g. when calling connect() or bind() with port
920 number 0). Explicit port allocation behavior is unchanged.
922 The format used for both input and output is a comma separated
923 list of ranges (e.g. "1,2-4,10-10" for ports 1, 2, 3, 4 and
924 10). Writing to the file will clear all previously reserved
925 ports and update the current list with the one given in the
928 Note that ip_local_port_range and ip_local_reserved_ports
929 settings are independent and both are considered by the kernel
930 when determining which ports are available for automatic port
933 You can reserve ports which are not in the current
934 ip_local_port_range, e.g.:
936 $ cat /proc/sys/net/ipv4/ip_local_port_range
938 $ cat /proc/sys/net/ipv4/ip_local_reserved_ports
941 although this is redundant. However such a setting is useful
942 if later the port range is changed to a value that will
943 include the reserved ports.
947 ip_unprivileged_port_start - INTEGER
948 This is a per-namespace sysctl. It defines the first
949 unprivileged port in the network namespace. Privileged ports
950 require root or CAP_NET_BIND_SERVICE in order to bind to them.
951 To disable all privileged ports, set this to 0. They must not
952 overlap with the ip_local_port_range.
956 ip_nonlocal_bind - BOOLEAN
957 If set, allows processes to bind() to non-local IP addresses,
958 which can be quite useful - but may break some applications.
961 ip_autobind_reuse - BOOLEAN
962 By default, bind() does not select the ports automatically even if
963 the new socket and all sockets bound to the port have SO_REUSEADDR.
964 ip_autobind_reuse allows bind() to reuse the port and this is useful
965 when you use bind()+connect(), but may break some applications.
966 The preferred solution is to use IP_BIND_ADDRESS_NO_PORT and this
967 option should only be set by experts.
971 If set non-zero, enables support for dynamic addresses.
972 If set to a non-zero value larger than 1, a kernel log
973 message will be printed when dynamic address rewriting
977 ip_early_demux - BOOLEAN
978 Optimize input packet processing down to one demux for
979 certain kinds of local sockets. Currently we only do this
980 for established TCP and connected UDP sockets.
982 It may add an additional cost for pure routing workloads that
983 reduces overall throughput, in such case you should disable it.
986 tcp_early_demux - BOOLEAN
987 Enable early demux for established TCP sockets.
990 udp_early_demux - BOOLEAN
991 Enable early demux for connected UDP sockets. Disable this if
992 your system could experience more unconnected load.
995 icmp_echo_ignore_all - BOOLEAN
996 If set non-zero, then the kernel will ignore all ICMP ECHO
1000 icmp_echo_ignore_broadcasts - BOOLEAN
1001 If set non-zero, then the kernel will ignore all ICMP ECHO and
1002 TIMESTAMP requests sent to it via broadcast/multicast.
1005 icmp_ratelimit - INTEGER
1006 Limit the maximal rates for sending ICMP packets whose type matches
1007 icmp_ratemask (see below) to specific targets.
1008 0 to disable any limiting,
1009 otherwise the minimal space between responses in milliseconds.
1010 Note that another sysctl, icmp_msgs_per_sec limits the number
1011 of ICMP packets sent on all targets.
1014 icmp_msgs_per_sec - INTEGER
1015 Limit maximal number of ICMP packets sent per second from this host.
1016 Only messages whose type matches icmp_ratemask (see below) are
1017 controlled by this limit.
1020 icmp_msgs_burst - INTEGER
1021 icmp_msgs_per_sec controls number of ICMP packets sent per second,
1022 while icmp_msgs_burst controls the burst size of these packets.
1025 icmp_ratemask - INTEGER
1026 Mask made of ICMP types for which rates are being limited.
1027 Significant bits: IHGFEDCBA9876543210
1028 Default mask: 0000001100000011000 (6168)
1030 Bit definitions (see include/linux/icmp.h):
1032 3 Destination Unreachable *
1037 C Parameter Problem *
1042 H Address Mask Request
1043 I Address Mask Reply
1045 * These are rate limited by default (see default mask above)
1047 icmp_ignore_bogus_error_responses - BOOLEAN
1048 Some routers violate RFC1122 by sending bogus responses to broadcast
1049 frames. Such violations are normally logged via a kernel warning.
1050 If this is set to TRUE, the kernel will not give such warnings, which
1051 will avoid log file clutter.
1054 icmp_errors_use_inbound_ifaddr - BOOLEAN
1056 If zero, icmp error messages are sent with the primary address of
1057 the exiting interface.
1059 If non-zero, the message will be sent with the primary address of
1060 the interface that received the packet that caused the icmp error.
1061 This is the behaviour network many administrators will expect from
1062 a router. And it can make debugging complicated network layouts
1065 Note that if no primary address exists for the interface selected,
1066 then the primary address of the first non-loopback interface that
1067 has one will be used regardless of this setting.
1071 igmp_max_memberships - INTEGER
1072 Change the maximum number of multicast groups we can subscribe to.
1075 Theoretical maximum value is bounded by having to send a membership
1076 report in a single datagram (i.e. the report can't span multiple
1077 datagrams, or risk confusing the switch and leaving groups you don't
1080 The number of supported groups 'M' is bounded by the number of group
1081 report entries you can fit into a single datagram of 65535 bytes.
1083 M = 65536-sizeof (ip header)/(sizeof(Group record))
1085 Group records are variable length, with a minimum of 12 bytes.
1086 So net.ipv4.igmp_max_memberships should not be set higher than:
1088 (65536-24) / 12 = 5459
1090 The value 5459 assumes no IP header options, so in practice
1091 this number may be lower.
1093 igmp_max_msf - INTEGER
1094 Maximum number of addresses allowed in the source filter list for a
1099 Controls the IGMP query robustness variable (see RFC2236 8.1).
1100 Default: 2 (as specified by RFC2236 8.1)
1101 Minimum: 1 (as specified by RFC6636 4.5)
1103 force_igmp_version - INTEGER
1104 0 - (default) No enforcement of a IGMP version, IGMPv1/v2 fallback
1105 allowed. Will back to IGMPv3 mode again if all IGMPv1/v2 Querier
1106 Present timer expires.
1107 1 - Enforce to use IGMP version 1. Will also reply IGMPv1 report if
1108 receive IGMPv2/v3 query.
1109 2 - Enforce to use IGMP version 2. Will fallback to IGMPv1 if receive
1110 IGMPv1 query message. Will reply report if receive IGMPv3 query.
1111 3 - Enforce to use IGMP version 3. The same react with default 0.
1113 Note: this is not the same with force_mld_version because IGMPv3 RFC3376
1114 Security Considerations does not have clear description that we could
1115 ignore other version messages completely as MLDv2 RFC3810. So make
1116 this value as default 0 is recommended.
1118 conf/interface/* changes special settings per interface (where
1119 "interface" is the name of your network interface)
1121 conf/all/* is special, changes the settings for all interfaces
1123 log_martians - BOOLEAN
1124 Log packets with impossible addresses to kernel log.
1125 log_martians for the interface will be enabled if at least one of
1126 conf/{all,interface}/log_martians is set to TRUE,
1127 it will be disabled otherwise
1129 accept_redirects - BOOLEAN
1130 Accept ICMP redirect messages.
1131 accept_redirects for the interface will be enabled if:
1132 - both conf/{all,interface}/accept_redirects are TRUE in the case
1133 forwarding for the interface is enabled
1135 - at least one of conf/{all,interface}/accept_redirects is TRUE in the
1136 case forwarding for the interface is disabled
1137 accept_redirects for the interface will be disabled otherwise
1141 forwarding - BOOLEAN
1142 Enable IP forwarding on this interface. This controls whether packets
1143 received _on_ this interface can be forwarded.
1145 mc_forwarding - BOOLEAN
1146 Do multicast routing. The kernel needs to be compiled with CONFIG_MROUTE
1147 and a multicast routing daemon is required.
1148 conf/all/mc_forwarding must also be set to TRUE to enable multicast
1149 routing for the interface
1152 Integer value used to differentiate the devices by the medium they
1153 are attached to. Two devices can have different id values when
1154 the broadcast packets are received only on one of them.
1155 The default value 0 means that the device is the only interface
1156 to its medium, value of -1 means that medium is not known.
1158 Currently, it is used to change the proxy_arp behavior:
1159 the proxy_arp feature is enabled for packets forwarded between
1160 two devices attached to different media.
1164 proxy_arp for the interface will be enabled if at least one of
1165 conf/{all,interface}/proxy_arp is set to TRUE,
1166 it will be disabled otherwise
1168 proxy_arp_pvlan - BOOLEAN
1169 Private VLAN proxy arp.
1170 Basically allow proxy arp replies back to the same interface
1171 (from which the ARP request/solicitation was received).
1173 This is done to support (ethernet) switch features, like RFC
1174 3069, where the individual ports are NOT allowed to
1175 communicate with each other, but they are allowed to talk to
1176 the upstream router. As described in RFC 3069, it is possible
1177 to allow these hosts to communicate through the upstream
1178 router by proxy_arp'ing. Don't need to be used together with
1181 This technology is known by different names:
1182 In RFC 3069 it is called VLAN Aggregation.
1183 Cisco and Allied Telesyn call it Private VLAN.
1184 Hewlett-Packard call it Source-Port filtering or port-isolation.
1185 Ericsson call it MAC-Forced Forwarding (RFC Draft).
1187 shared_media - BOOLEAN
1188 Send(router) or accept(host) RFC1620 shared media redirects.
1189 Overrides secure_redirects.
1190 shared_media for the interface will be enabled if at least one of
1191 conf/{all,interface}/shared_media is set to TRUE,
1192 it will be disabled otherwise
1195 secure_redirects - BOOLEAN
1196 Accept ICMP redirect messages only to gateways listed in the
1197 interface's current gateway list. Even if disabled, RFC1122 redirect
1199 Overridden by shared_media.
1200 secure_redirects for the interface will be enabled if at least one of
1201 conf/{all,interface}/secure_redirects is set to TRUE,
1202 it will be disabled otherwise
1205 send_redirects - BOOLEAN
1206 Send redirects, if router.
1207 send_redirects for the interface will be enabled if at least one of
1208 conf/{all,interface}/send_redirects is set to TRUE,
1209 it will be disabled otherwise
1212 bootp_relay - BOOLEAN
1213 Accept packets with source address 0.b.c.d destined
1214 not to this host as local ones. It is supposed, that
1215 BOOTP relay daemon will catch and forward such packets.
1216 conf/all/bootp_relay must also be set to TRUE to enable BOOTP relay
1219 Not Implemented Yet.
1221 accept_source_route - BOOLEAN
1222 Accept packets with SRR option.
1223 conf/all/accept_source_route must also be set to TRUE to accept packets
1224 with SRR option on the interface
1225 default TRUE (router)
1228 accept_local - BOOLEAN
1229 Accept packets with local source addresses. In combination with
1230 suitable routing, this can be used to direct packets between two
1231 local interfaces over the wire and have them accepted properly.
1234 route_localnet - BOOLEAN
1235 Do not consider loopback addresses as martian source or destination
1236 while routing. This enables the use of 127/8 for local routing purposes.
1240 0 - No source validation.
1241 1 - Strict mode as defined in RFC3704 Strict Reverse Path
1242 Each incoming packet is tested against the FIB and if the interface
1243 is not the best reverse path the packet check will fail.
1244 By default failed packets are discarded.
1245 2 - Loose mode as defined in RFC3704 Loose Reverse Path
1246 Each incoming packet's source address is also tested against the FIB
1247 and if the source address is not reachable via any interface
1248 the packet check will fail.
1250 Current recommended practice in RFC3704 is to enable strict mode
1251 to prevent IP spoofing from DDos attacks. If using asymmetric routing
1252 or other complicated routing, then loose mode is recommended.
1254 The max value from conf/{all,interface}/rp_filter is used
1255 when doing source validation on the {interface}.
1257 Default value is 0. Note that some distributions enable it
1260 arp_filter - BOOLEAN
1261 1 - Allows you to have multiple network interfaces on the same
1262 subnet, and have the ARPs for each interface be answered
1263 based on whether or not the kernel would route a packet from
1264 the ARP'd IP out that interface (therefore you must use source
1265 based routing for this to work). In other words it allows control
1266 of which cards (usually 1) will respond to an arp request.
1268 0 - (default) The kernel can respond to arp requests with addresses
1269 from other interfaces. This may seem wrong but it usually makes
1270 sense, because it increases the chance of successful communication.
1271 IP addresses are owned by the complete host on Linux, not by
1272 particular interfaces. Only for more complex setups like load-
1273 balancing, does this behaviour cause problems.
1275 arp_filter for the interface will be enabled if at least one of
1276 conf/{all,interface}/arp_filter is set to TRUE,
1277 it will be disabled otherwise
1279 arp_announce - INTEGER
1280 Define different restriction levels for announcing the local
1281 source IP address from IP packets in ARP requests sent on
1283 0 - (default) Use any local address, configured on any interface
1284 1 - Try to avoid local addresses that are not in the target's
1285 subnet for this interface. This mode is useful when target
1286 hosts reachable via this interface require the source IP
1287 address in ARP requests to be part of their logical network
1288 configured on the receiving interface. When we generate the
1289 request we will check all our subnets that include the
1290 target IP and will preserve the source address if it is from
1291 such subnet. If there is no such subnet we select source
1292 address according to the rules for level 2.
1293 2 - Always use the best local address for this target.
1294 In this mode we ignore the source address in the IP packet
1295 and try to select local address that we prefer for talks with
1296 the target host. Such local address is selected by looking
1297 for primary IP addresses on all our subnets on the outgoing
1298 interface that include the target IP address. If no suitable
1299 local address is found we select the first local address
1300 we have on the outgoing interface or on all other interfaces,
1301 with the hope we will receive reply for our request and
1302 even sometimes no matter the source IP address we announce.
1304 The max value from conf/{all,interface}/arp_announce is used.
1306 Increasing the restriction level gives more chance for
1307 receiving answer from the resolved target while decreasing
1308 the level announces more valid sender's information.
1310 arp_ignore - INTEGER
1311 Define different modes for sending replies in response to
1312 received ARP requests that resolve local target IP addresses:
1313 0 - (default): reply for any local target IP address, configured
1315 1 - reply only if the target IP address is local address
1316 configured on the incoming interface
1317 2 - reply only if the target IP address is local address
1318 configured on the incoming interface and both with the
1319 sender's IP address are part from same subnet on this interface
1320 3 - do not reply for local addresses configured with scope host,
1321 only resolutions for global and link addresses are replied
1323 8 - do not reply for all local addresses
1325 The max value from conf/{all,interface}/arp_ignore is used
1326 when ARP request is received on the {interface}
1328 arp_notify - BOOLEAN
1329 Define mode for notification of address and device changes.
1330 0 - (default): do nothing
1331 1 - Generate gratuitous arp requests when device is brought up
1332 or hardware address changes.
1334 arp_accept - BOOLEAN
1335 Define behavior for gratuitous ARP frames who's IP is not
1336 already present in the ARP table:
1337 0 - don't create new entries in the ARP table
1338 1 - create new entries in the ARP table
1340 Both replies and requests type gratuitous arp will trigger the
1341 ARP table to be updated, if this setting is on.
1343 If the ARP table already contains the IP address of the
1344 gratuitous arp frame, the arp table will be updated regardless
1345 if this setting is on or off.
1347 mcast_solicit - INTEGER
1348 The maximum number of multicast probes in INCOMPLETE state,
1349 when the associated hardware address is unknown. Defaults
1352 ucast_solicit - INTEGER
1353 The maximum number of unicast probes in PROBE state, when
1354 the hardware address is being reconfirmed. Defaults to 3.
1356 app_solicit - INTEGER
1357 The maximum number of probes to send to the user space ARP daemon
1358 via netlink before dropping back to multicast probes (see
1359 mcast_resolicit). Defaults to 0.
1361 mcast_resolicit - INTEGER
1362 The maximum number of multicast probes after unicast and
1363 app probes in PROBE state. Defaults to 0.
1365 disable_policy - BOOLEAN
1366 Disable IPSEC policy (SPD) for this interface
1368 disable_xfrm - BOOLEAN
1369 Disable IPSEC encryption on this interface, whatever the policy
1371 igmpv2_unsolicited_report_interval - INTEGER
1372 The interval in milliseconds in which the next unsolicited
1373 IGMPv1 or IGMPv2 report retransmit will take place.
1374 Default: 10000 (10 seconds)
1376 igmpv3_unsolicited_report_interval - INTEGER
1377 The interval in milliseconds in which the next unsolicited
1378 IGMPv3 report retransmit will take place.
1379 Default: 1000 (1 seconds)
1381 promote_secondaries - BOOLEAN
1382 When a primary IP address is removed from this interface
1383 promote a corresponding secondary IP address instead of
1384 removing all the corresponding secondary IP addresses.
1386 drop_unicast_in_l2_multicast - BOOLEAN
1387 Drop any unicast IP packets that are received in link-layer
1388 multicast (or broadcast) frames.
1389 This behavior (for multicast) is actually a SHOULD in RFC
1390 1122, but is disabled by default for compatibility reasons.
1393 drop_gratuitous_arp - BOOLEAN
1394 Drop all gratuitous ARP frames, for example if there's a known
1395 good ARP proxy on the network and such frames need not be used
1396 (or in the case of 802.11, must not be used to prevent attacks.)
1401 Allows you to write a number, which can be used as required.
1404 xfrm4_gc_thresh - INTEGER
1405 (Obsolete since linux-4.14)
1406 The threshold at which we will start garbage collecting for IPv4
1407 destination cache entries. At twice this value the system will
1408 refuse new allocations.
1410 igmp_link_local_mcast_reports - BOOLEAN
1411 Enable IGMP reports for link local multicast groups in the
1416 kuznet@ms2.inr.ac.ru
1422 delon.nicolas@wanadoo.fr
1427 /proc/sys/net/ipv6/* Variables:
1429 IPv6 has no global variables such as tcp_*. tcp_* settings under ipv4/ also
1430 apply to IPv6 [XXX?].
1432 bindv6only - BOOLEAN
1433 Default value for IPV6_V6ONLY socket option,
1434 which restricts use of the IPv6 socket to IPv6 communication
1436 TRUE: disable IPv4-mapped address feature
1437 FALSE: enable IPv4-mapped address feature
1439 Default: FALSE (as specified in RFC3493)
1441 flowlabel_consistency - BOOLEAN
1442 Protect the consistency (and unicity) of flow label.
1443 You have to disable it to use IPV6_FL_F_REFLECT flag on the
1449 auto_flowlabels - INTEGER
1450 Automatically generate flow labels based on a flow hash of the
1451 packet. This allows intermediate devices, such as routers, to
1452 identify packet flows for mechanisms like Equal Cost Multipath
1453 Routing (see RFC 6438).
1454 0: automatic flow labels are completely disabled
1455 1: automatic flow labels are enabled by default, they can be
1456 disabled on a per socket basis using the IPV6_AUTOFLOWLABEL
1458 2: automatic flow labels are allowed, they may be enabled on a
1459 per socket basis using the IPV6_AUTOFLOWLABEL socket option
1460 3: automatic flow labels are enabled and enforced, they cannot
1461 be disabled by the socket option
1464 flowlabel_state_ranges - BOOLEAN
1465 Split the flow label number space into two ranges. 0-0x7FFFF is
1466 reserved for the IPv6 flow manager facility, 0x80000-0xFFFFF
1467 is reserved for stateless flow labels as described in RFC6437.
1472 flowlabel_reflect - INTEGER
1473 Control flow label reflection. Needed for Path MTU
1474 Discovery to work with Equal Cost Multipath Routing in anycast
1475 environments. See RFC 7690 and:
1476 https://tools.ietf.org/html/draft-wang-6man-flow-label-reflection-01
1479 1: enabled for established flows
1481 Note that this prevents automatic flowlabel changes, as done
1482 in "tcp: change IPv6 flow-label upon receiving spurious retransmission"
1483 and "tcp: Change txhash on every SYN and RTO retransmit"
1485 2: enabled for TCP RESET packets (no active listener)
1486 If set, a RST packet sent in response to a SYN packet on a closed
1487 port will reflect the incoming flow label.
1489 4: enabled for ICMPv6 echo reply messages.
1493 fib_multipath_hash_policy - INTEGER
1494 Controls which hash policy to use for multipath routes.
1495 Default: 0 (Layer 3)
1497 0 - Layer 3 (source and destination addresses plus flow label)
1498 1 - Layer 4 (standard 5-tuple)
1499 2 - Layer 3 or inner Layer 3 if present
1501 anycast_src_echo_reply - BOOLEAN
1502 Controls the use of anycast addresses as source addresses for ICMPv6
1508 idgen_delay - INTEGER
1509 Controls the delay in seconds after which time to retry
1510 privacy stable address generation if a DAD conflict is
1512 Default: 1 (as specified in RFC7217)
1514 idgen_retries - INTEGER
1515 Controls the number of retries to generate a stable privacy
1516 address if a DAD conflict is detected.
1517 Default: 3 (as specified in RFC7217)
1520 Controls the MLD query robustness variable (see RFC3810 9.1).
1521 Default: 2 (as specified by RFC3810 9.1)
1522 Minimum: 1 (as specified by RFC6636 4.5)
1524 max_dst_opts_number - INTEGER
1525 Maximum number of non-padding TLVs allowed in a Destination
1526 options extension header. If this value is less than zero
1527 then unknown options are disallowed and the number of known
1528 TLVs allowed is the absolute value of this number.
1531 max_hbh_opts_number - INTEGER
1532 Maximum number of non-padding TLVs allowed in a Hop-by-Hop
1533 options extension header. If this value is less than zero
1534 then unknown options are disallowed and the number of known
1535 TLVs allowed is the absolute value of this number.
1538 max_dst_opts_length - INTEGER
1539 Maximum length allowed for a Destination options extension
1541 Default: INT_MAX (unlimited)
1543 max_hbh_length - INTEGER
1544 Maximum length allowed for a Hop-by-Hop options extension
1546 Default: INT_MAX (unlimited)
1548 skip_notify_on_dev_down - BOOLEAN
1549 Controls whether an RTM_DELROUTE message is generated for routes
1550 removed when a device is taken down or deleted. IPv4 does not
1551 generate this message; IPv6 does by default. Setting this sysctl
1552 to true skips the message, making IPv4 and IPv6 on par in relying
1553 on userspace caches to track link events and evict routes.
1554 Default: false (generate message)
1558 ip6frag_high_thresh - INTEGER
1559 Maximum memory used to reassemble IPv6 fragments. When
1560 ip6frag_high_thresh bytes of memory is allocated for this purpose,
1561 the fragment handler will toss packets until ip6frag_low_thresh
1564 ip6frag_low_thresh - INTEGER
1565 See ip6frag_high_thresh
1567 ip6frag_time - INTEGER
1568 Time in seconds to keep an IPv6 fragment in memory.
1570 IPv6 Segment Routing:
1572 seg6_flowlabel - INTEGER
1573 Controls the behaviour of computing the flowlabel of outer
1574 IPv6 header in case of SR T.encaps
1576 -1 set flowlabel to zero.
1577 0 copy flowlabel from Inner packet in case of Inner IPv6
1578 (Set flowlabel to 0 in case IPv4/L2)
1579 1 Compute the flowlabel using seg6_make_flowlabel()
1584 Change the interface-specific default settings.
1588 Change all the interface-specific settings.
1590 [XXX: Other special features than forwarding?]
1592 conf/all/forwarding - BOOLEAN
1593 Enable global IPv6 forwarding between all interfaces.
1595 IPv4 and IPv6 work differently here; e.g. netfilter must be used
1596 to control which interfaces may forward packets and which not.
1598 This also sets all interfaces' Host/Router setting
1599 'forwarding' to the specified value. See below for details.
1601 This referred to as global forwarding.
1606 fwmark_reflect - BOOLEAN
1607 Controls the fwmark of kernel-generated IPv6 reply packets that are not
1608 associated with a socket for example, TCP RSTs or ICMPv6 echo replies).
1609 If unset, these packets have a fwmark of zero. If set, they have the
1610 fwmark of the packet they are replying to.
1614 Change special settings per interface.
1616 The functional behaviour for certain settings is different
1617 depending on whether local forwarding is enabled or not.
1620 Accept Router Advertisements; autoconfigure using them.
1622 It also determines whether or not to transmit Router
1623 Solicitations. If and only if the functional setting is to
1624 accept Router Advertisements, Router Solicitations will be
1627 Possible values are:
1628 0 Do not accept Router Advertisements.
1629 1 Accept Router Advertisements if forwarding is disabled.
1630 2 Overrule forwarding behaviour. Accept Router Advertisements
1631 even if forwarding is enabled.
1633 Functional default: enabled if local forwarding is disabled.
1634 disabled if local forwarding is enabled.
1636 accept_ra_defrtr - BOOLEAN
1637 Learn default router in Router Advertisement.
1639 Functional default: enabled if accept_ra is enabled.
1640 disabled if accept_ra is disabled.
1642 accept_ra_from_local - BOOLEAN
1643 Accept RA with source-address that is found on local machine
1644 if the RA is otherwise proper and able to be accepted.
1645 Default is to NOT accept these as it may be an un-intended
1649 enabled if accept_ra_from_local is enabled
1650 on a specific interface.
1651 disabled if accept_ra_from_local is disabled
1652 on a specific interface.
1654 accept_ra_min_hop_limit - INTEGER
1655 Minimum hop limit Information in Router Advertisement.
1657 Hop limit Information in Router Advertisement less than this
1658 variable shall be ignored.
1662 accept_ra_pinfo - BOOLEAN
1663 Learn Prefix Information in Router Advertisement.
1665 Functional default: enabled if accept_ra is enabled.
1666 disabled if accept_ra is disabled.
1668 accept_ra_rt_info_min_plen - INTEGER
1669 Minimum prefix length of Route Information in RA.
1671 Route Information w/ prefix smaller than this variable shall
1674 Functional default: 0 if accept_ra_rtr_pref is enabled.
1675 -1 if accept_ra_rtr_pref is disabled.
1677 accept_ra_rt_info_max_plen - INTEGER
1678 Maximum prefix length of Route Information in RA.
1680 Route Information w/ prefix larger than this variable shall
1683 Functional default: 0 if accept_ra_rtr_pref is enabled.
1684 -1 if accept_ra_rtr_pref is disabled.
1686 accept_ra_rtr_pref - BOOLEAN
1687 Accept Router Preference in RA.
1689 Functional default: enabled if accept_ra is enabled.
1690 disabled if accept_ra is disabled.
1692 accept_ra_mtu - BOOLEAN
1693 Apply the MTU value specified in RA option 5 (RFC4861). If
1694 disabled, the MTU specified in the RA will be ignored.
1696 Functional default: enabled if accept_ra is enabled.
1697 disabled if accept_ra is disabled.
1699 accept_redirects - BOOLEAN
1702 Functional default: enabled if local forwarding is disabled.
1703 disabled if local forwarding is enabled.
1705 accept_source_route - INTEGER
1706 Accept source routing (routing extension header).
1708 >= 0: Accept only routing header type 2.
1709 < 0: Do not accept routing header.
1714 Autoconfigure addresses using Prefix Information in Router
1717 Functional default: enabled if accept_ra_pinfo is enabled.
1718 disabled if accept_ra_pinfo is disabled.
1720 dad_transmits - INTEGER
1721 The amount of Duplicate Address Detection probes to send.
1724 forwarding - INTEGER
1725 Configure interface-specific Host/Router behaviour.
1727 Note: It is recommended to have the same setting on all
1728 interfaces; mixed router/host scenarios are rather uncommon.
1730 Possible values are:
1731 0 Forwarding disabled
1732 1 Forwarding enabled
1736 By default, Host behaviour is assumed. This means:
1738 1. IsRouter flag is not set in Neighbour Advertisements.
1739 2. If accept_ra is TRUE (default), transmit Router
1741 3. If accept_ra is TRUE (default), accept Router
1742 Advertisements (and do autoconfiguration).
1743 4. If accept_redirects is TRUE (default), accept Redirects.
1747 If local forwarding is enabled, Router behaviour is assumed.
1748 This means exactly the reverse from the above:
1750 1. IsRouter flag is set in Neighbour Advertisements.
1751 2. Router Solicitations are not sent unless accept_ra is 2.
1752 3. Router Advertisements are ignored unless accept_ra is 2.
1753 4. Redirects are ignored.
1755 Default: 0 (disabled) if global forwarding is disabled (default),
1756 otherwise 1 (enabled).
1759 Default Hop Limit to set.
1763 Default Maximum Transfer Unit
1764 Default: 1280 (IPv6 required minimum)
1766 ip_nonlocal_bind - BOOLEAN
1767 If set, allows processes to bind() to non-local IPv6 addresses,
1768 which can be quite useful - but may break some applications.
1771 router_probe_interval - INTEGER
1772 Minimum interval (in seconds) between Router Probing described
1777 router_solicitation_delay - INTEGER
1778 Number of seconds to wait after interface is brought up
1779 before sending Router Solicitations.
1782 router_solicitation_interval - INTEGER
1783 Number of seconds to wait between Router Solicitations.
1786 router_solicitations - INTEGER
1787 Number of Router Solicitations to send until assuming no
1788 routers are present.
1791 use_oif_addrs_only - BOOLEAN
1792 When enabled, the candidate source addresses for destinations
1793 routed via this interface are restricted to the set of addresses
1794 configured on this interface (vis. RFC 6724, section 4).
1798 use_tempaddr - INTEGER
1799 Preference for Privacy Extensions (RFC3041).
1800 <= 0 : disable Privacy Extensions
1801 == 1 : enable Privacy Extensions, but prefer public
1802 addresses over temporary addresses.
1803 > 1 : enable Privacy Extensions and prefer temporary
1804 addresses over public addresses.
1805 Default: 0 (for most devices)
1806 -1 (for point-to-point devices and loopback devices)
1808 temp_valid_lft - INTEGER
1809 valid lifetime (in seconds) for temporary addresses.
1810 Default: 604800 (7 days)
1812 temp_prefered_lft - INTEGER
1813 Preferred lifetime (in seconds) for temporary addresses.
1814 Default: 86400 (1 day)
1816 keep_addr_on_down - INTEGER
1817 Keep all IPv6 addresses on an interface down event. If set static
1818 global addresses with no expiration time are not flushed.
1823 Default: 0 (addresses are removed)
1825 max_desync_factor - INTEGER
1826 Maximum value for DESYNC_FACTOR, which is a random value
1827 that ensures that clients don't synchronize with each
1828 other and generate new addresses at exactly the same time.
1829 value is in seconds.
1832 regen_max_retry - INTEGER
1833 Number of attempts before give up attempting to generate
1834 valid temporary addresses.
1837 max_addresses - INTEGER
1838 Maximum number of autoconfigured addresses per interface. Setting
1839 to zero disables the limitation. It is not recommended to set this
1840 value too large (or to zero) because it would be an easy way to
1841 crash the kernel by allowing too many addresses to be created.
1844 disable_ipv6 - BOOLEAN
1845 Disable IPv6 operation. If accept_dad is set to 2, this value
1846 will be dynamically set to TRUE if DAD fails for the link-local
1848 Default: FALSE (enable IPv6 operation)
1850 When this value is changed from 1 to 0 (IPv6 is being enabled),
1851 it will dynamically create a link-local address on the given
1852 interface and start Duplicate Address Detection, if necessary.
1854 When this value is changed from 0 to 1 (IPv6 is being disabled),
1855 it will dynamically delete all addresses and routes on the given
1856 interface. From now on it will not possible to add addresses/routes
1857 to the selected interface.
1859 accept_dad - INTEGER
1860 Whether to accept DAD (Duplicate Address Detection).
1862 1: Enable DAD (default)
1863 2: Enable DAD, and disable IPv6 operation if MAC-based duplicate
1864 link-local address has been found.
1866 DAD operation and mode on a given interface will be selected according
1867 to the maximum value of conf/{all,interface}/accept_dad.
1869 force_tllao - BOOLEAN
1870 Enable sending the target link-layer address option even when
1871 responding to a unicast neighbor solicitation.
1874 Quoting from RFC 2461, section 4.4, Target link-layer address:
1876 "The option MUST be included for multicast solicitations in order to
1877 avoid infinite Neighbor Solicitation "recursion" when the peer node
1878 does not have a cache entry to return a Neighbor Advertisements
1879 message. When responding to unicast solicitations, the option can be
1880 omitted since the sender of the solicitation has the correct link-
1881 layer address; otherwise it would not have be able to send the unicast
1882 solicitation in the first place. However, including the link-layer
1883 address in this case adds little overhead and eliminates a potential
1884 race condition where the sender deletes the cached link-layer address
1885 prior to receiving a response to a previous solicitation."
1887 ndisc_notify - BOOLEAN
1888 Define mode for notification of address and device changes.
1889 0 - (default): do nothing
1890 1 - Generate unsolicited neighbour advertisements when device is brought
1891 up or hardware address changes.
1893 ndisc_tclass - INTEGER
1894 The IPv6 Traffic Class to use by default when sending IPv6 Neighbor
1895 Discovery (Router Solicitation, Router Advertisement, Neighbor
1896 Solicitation, Neighbor Advertisement, Redirect) messages.
1897 These 8 bits can be interpreted as 6 high order bits holding the DSCP
1898 value and 2 low order bits representing ECN (which you probably want
1902 mldv1_unsolicited_report_interval - INTEGER
1903 The interval in milliseconds in which the next unsolicited
1904 MLDv1 report retransmit will take place.
1905 Default: 10000 (10 seconds)
1907 mldv2_unsolicited_report_interval - INTEGER
1908 The interval in milliseconds in which the next unsolicited
1909 MLDv2 report retransmit will take place.
1910 Default: 1000 (1 second)
1912 force_mld_version - INTEGER
1913 0 - (default) No enforcement of a MLD version, MLDv1 fallback allowed
1914 1 - Enforce to use MLD version 1
1915 2 - Enforce to use MLD version 2
1917 suppress_frag_ndisc - INTEGER
1918 Control RFC 6980 (Security Implications of IPv6 Fragmentation
1919 with IPv6 Neighbor Discovery) behavior:
1920 1 - (default) discard fragmented neighbor discovery packets
1921 0 - allow fragmented neighbor discovery packets
1923 optimistic_dad - BOOLEAN
1924 Whether to perform Optimistic Duplicate Address Detection (RFC 4429).
1925 0: disabled (default)
1928 Optimistic Duplicate Address Detection for the interface will be enabled
1929 if at least one of conf/{all,interface}/optimistic_dad is set to 1,
1930 it will be disabled otherwise.
1932 use_optimistic - BOOLEAN
1933 If enabled, do not classify optimistic addresses as deprecated during
1934 source address selection. Preferred addresses will still be chosen
1935 before optimistic addresses, subject to other ranking in the source
1936 address selection algorithm.
1937 0: disabled (default)
1940 This will be enabled if at least one of
1941 conf/{all,interface}/use_optimistic is set to 1, disabled otherwise.
1943 stable_secret - IPv6 address
1944 This IPv6 address will be used as a secret to generate IPv6
1945 addresses for link-local addresses and autoconfigured
1946 ones. All addresses generated after setting this secret will
1947 be stable privacy ones by default. This can be changed via the
1948 addrgenmode ip-link. conf/default/stable_secret is used as the
1949 secret for the namespace, the interface specific ones can
1950 overwrite that. Writes to conf/all/stable_secret are refused.
1952 It is recommended to generate this secret during installation
1953 of a system and keep it stable after that.
1955 By default the stable secret is unset.
1957 addr_gen_mode - INTEGER
1958 Defines how link-local and autoconf addresses are generated.
1960 0: generate address based on EUI64 (default)
1961 1: do no generate a link-local address, use EUI64 for addresses generated
1963 2: generate stable privacy addresses, using the secret from
1964 stable_secret (RFC7217)
1965 3: generate stable privacy addresses, using a random secret if unset
1967 drop_unicast_in_l2_multicast - BOOLEAN
1968 Drop any unicast IPv6 packets that are received in link-layer
1969 multicast (or broadcast) frames.
1971 By default this is turned off.
1973 drop_unsolicited_na - BOOLEAN
1974 Drop all unsolicited neighbor advertisements, for example if there's
1975 a known good NA proxy on the network and such frames need not be used
1976 (or in the case of 802.11, must not be used to prevent attacks.)
1978 By default this is turned off.
1980 enhanced_dad - BOOLEAN
1981 Include a nonce option in the IPv6 neighbor solicitation messages used for
1982 duplicate address detection per RFC7527. A received DAD NS will only signal
1983 a duplicate address if the nonce is different. This avoids any false
1984 detection of duplicates due to loopback of the NS messages that we send.
1985 The nonce option will be sent on an interface unless both of
1986 conf/{all,interface}/enhanced_dad are set to FALSE.
1991 Limit the maximal rates for sending ICMPv6 messages.
1992 0 to disable any limiting,
1993 otherwise the minimal space between responses in milliseconds.
1996 ratemask - list of comma separated ranges
1997 For ICMPv6 message types matching the ranges in the ratemask, limit
1998 the sending of the message according to ratelimit parameter.
2000 The format used for both input and output is a comma separated
2001 list of ranges (e.g. "0-127,129" for ICMPv6 message type 0 to 127 and
2002 129). Writing to the file will clear all previous ranges of ICMPv6
2003 message types and update the current list with the input.
2005 Refer to: https://www.iana.org/assignments/icmpv6-parameters/icmpv6-parameters.xhtml
2006 for numerical values of ICMPv6 message types, e.g. echo request is 128
2007 and echo reply is 129.
2009 Default: 0-1,3-127 (rate limit ICMPv6 errors except Packet Too Big)
2011 echo_ignore_all - BOOLEAN
2012 If set non-zero, then the kernel will ignore all ICMP ECHO
2013 requests sent to it over the IPv6 protocol.
2016 echo_ignore_multicast - BOOLEAN
2017 If set non-zero, then the kernel will ignore all ICMP ECHO
2018 requests sent to it over the IPv6 protocol via multicast.
2021 echo_ignore_anycast - BOOLEAN
2022 If set non-zero, then the kernel will ignore all ICMP ECHO
2023 requests sent to it over the IPv6 protocol destined to anycast address.
2026 xfrm6_gc_thresh - INTEGER
2027 (Obsolete since linux-4.14)
2028 The threshold at which we will start garbage collecting for IPv6
2029 destination cache entries. At twice this value the system will
2030 refuse new allocations.
2034 Pekka Savola <pekkas@netcore.fi>
2035 YOSHIFUJI Hideaki / USAGI Project <yoshfuji@linux-ipv6.org>
2038 /proc/sys/net/bridge/* Variables:
2040 bridge-nf-call-arptables - BOOLEAN
2041 1 : pass bridged ARP traffic to arptables' FORWARD chain.
2045 bridge-nf-call-iptables - BOOLEAN
2046 1 : pass bridged IPv4 traffic to iptables' chains.
2050 bridge-nf-call-ip6tables - BOOLEAN
2051 1 : pass bridged IPv6 traffic to ip6tables' chains.
2055 bridge-nf-filter-vlan-tagged - BOOLEAN
2056 1 : pass bridged vlan-tagged ARP/IP/IPv6 traffic to {arp,ip,ip6}tables.
2060 bridge-nf-filter-pppoe-tagged - BOOLEAN
2061 1 : pass bridged pppoe-tagged IP/IPv6 traffic to {ip,ip6}tables.
2065 bridge-nf-pass-vlan-input-dev - BOOLEAN
2066 1: if bridge-nf-filter-vlan-tagged is enabled, try to find a vlan
2067 interface on the bridge and set the netfilter input device to the vlan.
2068 This allows use of e.g. "iptables -i br0.1" and makes the REDIRECT
2069 target work with vlan-on-top-of-bridge interfaces. When no matching
2070 vlan interface is found, or this switch is off, the input device is
2071 set to the bridge interface.
2072 0: disable bridge netfilter vlan interface lookup.
2075 proc/sys/net/sctp/* Variables:
2077 addip_enable - BOOLEAN
2078 Enable or disable extension of Dynamic Address Reconfiguration
2079 (ADD-IP) functionality specified in RFC5061. This extension provides
2080 the ability to dynamically add and remove new addresses for the SCTP
2083 1: Enable extension.
2085 0: Disable extension.
2090 Enable or disable pf (pf is short for potentially failed) state. A value
2091 of pf_retrans > path_max_retrans also disables pf state. That is, one of
2092 both pf_enable and pf_retrans > path_max_retrans can disable pf state.
2093 Since pf_retrans and path_max_retrans can be changed by userspace
2094 application, sometimes user expects to disable pf state by the value of
2095 pf_retrans > path_max_retrans, but occasionally the value of pf_retrans
2096 or path_max_retrans is changed by the user application, this pf state is
2097 enabled. As such, it is necessary to add this to dynamically enable
2098 and disable pf state. See:
2099 https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-failover for
2109 Unset or enable/disable pf (pf is short for potentially failed) state
2110 exposure. Applications can control the exposure of the PF path state
2111 in the SCTP_PEER_ADDR_CHANGE event and the SCTP_GET_PEER_ADDR_INFO
2112 sockopt. When it's unset, no SCTP_PEER_ADDR_CHANGE event with
2113 SCTP_ADDR_PF state will be sent and a SCTP_PF-state transport info
2114 can be got via SCTP_GET_PEER_ADDR_INFO sockopt; When it's enabled,
2115 a SCTP_PEER_ADDR_CHANGE event will be sent for a transport becoming
2116 SCTP_PF state and a SCTP_PF-state transport info can be got via
2117 SCTP_GET_PEER_ADDR_INFO sockopt; When it's diabled, no
2118 SCTP_PEER_ADDR_CHANGE event will be sent and it returns -EACCES when
2119 trying to get a SCTP_PF-state transport info via SCTP_GET_PEER_ADDR_INFO
2122 0: Unset pf state exposure, Compatible with old applications.
2124 1: Disable pf state exposure.
2126 2: Enable pf state exposure.
2130 addip_noauth_enable - BOOLEAN
2131 Dynamic Address Reconfiguration (ADD-IP) requires the use of
2132 authentication to protect the operations of adding or removing new
2133 addresses. This requirement is mandated so that unauthorized hosts
2134 would not be able to hijack associations. However, older
2135 implementations may not have implemented this requirement while
2136 allowing the ADD-IP extension. For reasons of interoperability,
2137 we provide this variable to control the enforcement of the
2138 authentication requirement.
2140 1: Allow ADD-IP extension to be used without authentication. This
2141 should only be set in a closed environment for interoperability
2142 with older implementations.
2144 0: Enforce the authentication requirement
2148 auth_enable - BOOLEAN
2149 Enable or disable Authenticated Chunks extension. This extension
2150 provides the ability to send and receive authenticated chunks and is
2151 required for secure operation of Dynamic Address Reconfiguration
2154 1: Enable this extension.
2155 0: Disable this extension.
2159 prsctp_enable - BOOLEAN
2160 Enable or disable the Partial Reliability extension (RFC3758) which
2161 is used to notify peers that a given DATA should no longer be expected.
2169 The limit of the number of new packets that can be initially sent. It
2170 controls how bursty the generated traffic can be.
2174 association_max_retrans - INTEGER
2175 Set the maximum number for retransmissions that an association can
2176 attempt deciding that the remote end is unreachable. If this value
2177 is exceeded, the association is terminated.
2181 max_init_retransmits - INTEGER
2182 The maximum number of retransmissions of INIT and COOKIE-ECHO chunks
2183 that an association will attempt before declaring the destination
2184 unreachable and terminating.
2188 path_max_retrans - INTEGER
2189 The maximum number of retransmissions that will be attempted on a given
2190 path. Once this threshold is exceeded, the path is considered
2191 unreachable, and new traffic will use a different path when the
2192 association is multihomed.
2196 pf_retrans - INTEGER
2197 The number of retransmissions that will be attempted on a given path
2198 before traffic is redirected to an alternate transport (should one
2199 exist). Note this is distinct from path_max_retrans, as a path that
2200 passes the pf_retrans threshold can still be used. Its only
2201 deprioritized when a transmission path is selected by the stack. This
2202 setting is primarily used to enable fast failover mechanisms without
2203 having to reduce path_max_retrans to a very low value. See:
2204 http://www.ietf.org/id/draft-nishida-tsvwg-sctp-failover-05.txt
2205 for details. Note also that a value of pf_retrans > path_max_retrans
2206 disables this feature. Since both pf_retrans and path_max_retrans can
2207 be changed by userspace application, a variable pf_enable is used to
2212 ps_retrans - INTEGER
2213 Primary.Switchover.Max.Retrans (PSMR), it's a tunable parameter coming
2214 from section-5 "Primary Path Switchover" in rfc7829. The primary path
2215 will be changed to another active path when the path error counter on
2216 the old primary path exceeds PSMR, so that "the SCTP sender is allowed
2217 to continue data transmission on a new working path even when the old
2218 primary destination address becomes active again". Note this feature
2219 is disabled by initializing 'ps_retrans' per netns as 0xffff by default,
2220 and its value can't be less than 'pf_retrans' when changing by sysctl.
2224 rto_initial - INTEGER
2225 The initial round trip timeout value in milliseconds that will be used
2226 in calculating round trip times. This is the initial time interval
2227 for retransmissions.
2232 The maximum value (in milliseconds) of the round trip timeout. This
2233 is the largest time interval that can elapse between retransmissions.
2238 The minimum value (in milliseconds) of the round trip timeout. This
2239 is the smallest time interval the can elapse between retransmissions.
2243 hb_interval - INTEGER
2244 The interval (in milliseconds) between HEARTBEAT chunks. These chunks
2245 are sent at the specified interval on idle paths to probe the state of
2246 a given path between 2 associations.
2250 sack_timeout - INTEGER
2251 The amount of time (in milliseconds) that the implementation will wait
2256 valid_cookie_life - INTEGER
2257 The default lifetime of the SCTP cookie (in milliseconds). The cookie
2258 is used during association establishment.
2262 cookie_preserve_enable - BOOLEAN
2263 Enable or disable the ability to extend the lifetime of the SCTP cookie
2264 that is used during the establishment phase of SCTP association
2266 1: Enable cookie lifetime extension.
2271 cookie_hmac_alg - STRING
2272 Select the hmac algorithm used when generating the cookie value sent by
2273 a listening sctp socket to a connecting client in the INIT-ACK chunk.
2278 Ability to assign md5 or sha1 as the selected alg is predicated on the
2279 configuration of those algorithms at build time (CONFIG_CRYPTO_MD5 and
2280 CONFIG_CRYPTO_SHA1).
2282 Default: Dependent on configuration. MD5 if available, else SHA1 if
2283 available, else none.
2285 rcvbuf_policy - INTEGER
2286 Determines if the receive buffer is attributed to the socket or to
2287 association. SCTP supports the capability to create multiple
2288 associations on a single socket. When using this capability, it is
2289 possible that a single stalled association that's buffering a lot
2290 of data may block other associations from delivering their data by
2291 consuming all of the receive buffer space. To work around this,
2292 the rcvbuf_policy could be set to attribute the receiver buffer space
2293 to each association instead of the socket. This prevents the described
2296 1: rcvbuf space is per association
2297 0: rcvbuf space is per socket
2301 sndbuf_policy - INTEGER
2302 Similar to rcvbuf_policy above, this applies to send buffer space.
2304 1: Send buffer is tracked per association
2305 0: Send buffer is tracked per socket.
2309 sctp_mem - vector of 3 INTEGERs: min, pressure, max
2310 Number of pages allowed for queueing by all SCTP sockets.
2312 min: Below this number of pages SCTP is not bothered about its
2313 memory appetite. When amount of memory allocated by SCTP exceeds
2314 this number, SCTP starts to moderate memory usage.
2316 pressure: This value was introduced to follow format of tcp_mem.
2318 max: Number of pages allowed for queueing by all SCTP sockets.
2320 Default is calculated at boot time from amount of available memory.
2322 sctp_rmem - vector of 3 INTEGERs: min, default, max
2323 Only the first value ("min") is used, "default" and "max" are
2326 min: Minimal size of receive buffer used by SCTP socket.
2327 It is guaranteed to each SCTP socket (but not association) even
2328 under moderate memory pressure.
2332 sctp_wmem - vector of 3 INTEGERs: min, default, max
2333 Currently this tunable has no effect.
2335 addr_scope_policy - INTEGER
2336 Control IPv4 address scoping - draft-stewart-tsvwg-sctp-ipv4-00
2338 0 - Disable IPv4 address scoping
2339 1 - Enable IPv4 address scoping
2340 2 - Follow draft but allow IPv4 private addresses
2341 3 - Follow draft but allow IPv4 link local addresses
2346 /proc/sys/net/core/*
2347 Please see: Documentation/admin-guide/sysctl/net.rst for descriptions of these entries.
2350 /proc/sys/net/unix/*
2351 max_dgram_qlen - INTEGER
2352 The maximum length of dgram socket receive queue