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.
84 route/max_size - INTEGER
85 Maximum number of routes allowed in the kernel. Increase
86 this when using large numbers of interfaces and/or routes.
87 From linux kernel 3.6 onwards, this is deprecated for ipv4
88 as route cache is no longer used.
90 neigh/default/gc_thresh1 - INTEGER
91 Minimum number of entries to keep. Garbage collector will not
92 purge entries if there are fewer than this number.
95 neigh/default/gc_thresh2 - INTEGER
96 Threshold when garbage collector becomes more aggressive about
97 purging entries. Entries older than 5 seconds will be cleared
98 when over this number.
101 neigh/default/gc_thresh3 - INTEGER
102 Maximum number of neighbor entries allowed. Increase this
103 when using large numbers of interfaces and when communicating
104 with large numbers of directly-connected peers.
107 neigh/default/unres_qlen_bytes - INTEGER
108 The maximum number of bytes which may be used by packets
109 queued for each unresolved address by other network layers.
111 Setting negative value is meaningless and will return error.
112 Default: SK_WMEM_MAX, (same as net.core.wmem_default).
113 Exact value depends on architecture and kernel options,
114 but should be enough to allow queuing 256 packets
117 neigh/default/unres_qlen - INTEGER
118 The maximum number of packets which may be queued for each
119 unresolved address by other network layers.
120 (deprecated in linux 3.3) : use unres_qlen_bytes instead.
121 Prior to linux 3.3, the default value is 3 which may cause
122 unexpected packet loss. The current default value is calculated
123 according to default value of unres_qlen_bytes and true size of
127 mtu_expires - INTEGER
128 Time, in seconds, that cached PMTU information is kept.
130 min_adv_mss - INTEGER
131 The advertised MSS depends on the first hop route MTU, but will
132 never be lower than this setting.
136 ipfrag_high_thresh - LONG INTEGER
137 Maximum memory used to reassemble IP fragments.
139 ipfrag_low_thresh - LONG INTEGER
140 (Obsolete since linux-4.17)
141 Maximum memory used to reassemble IP fragments before the kernel
142 begins to remove incomplete fragment queues to free up resources.
143 The kernel still accepts new fragments for defragmentation.
145 ipfrag_time - INTEGER
146 Time in seconds to keep an IP fragment in memory.
148 ipfrag_max_dist - INTEGER
149 ipfrag_max_dist is a non-negative integer value which defines the
150 maximum "disorder" which is allowed among fragments which share a
151 common IP source address. Note that reordering of packets is
152 not unusual, but if a large number of fragments arrive from a source
153 IP address while a particular fragment queue remains incomplete, it
154 probably indicates that one or more fragments belonging to that queue
155 have been lost. When ipfrag_max_dist is positive, an additional check
156 is done on fragments before they are added to a reassembly queue - if
157 ipfrag_max_dist (or more) fragments have arrived from a particular IP
158 address between additions to any IP fragment queue using that source
159 address, it's presumed that one or more fragments in the queue are
160 lost. The existing fragment queue will be dropped, and a new one
161 started. An ipfrag_max_dist value of zero disables this check.
163 Using a very small value, e.g. 1 or 2, for ipfrag_max_dist can
164 result in unnecessarily dropping fragment queues when normal
165 reordering of packets occurs, which could lead to poor application
166 performance. Using a very large value, e.g. 50000, increases the
167 likelihood of incorrectly reassembling IP fragments that originate
168 from different IP datagrams, which could result in data corruption.
173 inet_peer_threshold - INTEGER
174 The approximate size of the storage. Starting from this threshold
175 entries will be thrown aggressively. This threshold also determines
176 entries' time-to-live and time intervals between garbage collection
177 passes. More entries, less time-to-live, less GC interval.
179 inet_peer_minttl - INTEGER
180 Minimum time-to-live of entries. Should be enough to cover fragment
181 time-to-live on the reassembling side. This minimum time-to-live is
182 guaranteed if the pool size is less than inet_peer_threshold.
185 inet_peer_maxttl - INTEGER
186 Maximum time-to-live of entries. Unused entries will expire after
187 this period of time if there is no memory pressure on the pool (i.e.
188 when the number of entries in the pool is very small).
194 Limit of socket listen() backlog, known in userspace as SOMAXCONN.
195 Defaults to 128. See also tcp_max_syn_backlog for additional tuning
198 tcp_abort_on_overflow - BOOLEAN
199 If listening service is too slow to accept new connections,
200 reset them. Default state is FALSE. It means that if overflow
201 occurred due to a burst, connection will recover. Enable this
202 option _only_ if you are really sure that listening daemon
203 cannot be tuned to accept connections faster. Enabling this
204 option can harm clients of your server.
206 tcp_adv_win_scale - INTEGER
207 Count buffering overhead as bytes/2^tcp_adv_win_scale
208 (if tcp_adv_win_scale > 0) or bytes-bytes/2^(-tcp_adv_win_scale),
210 Possible values are [-31, 31], inclusive.
213 tcp_allowed_congestion_control - STRING
214 Show/set the congestion control choices available to non-privileged
215 processes. The list is a subset of those listed in
216 tcp_available_congestion_control.
217 Default is "reno" and the default setting (tcp_congestion_control).
219 tcp_app_win - INTEGER
220 Reserve max(window/2^tcp_app_win, mss) of window for application
221 buffer. Value 0 is special, it means that nothing is reserved.
224 tcp_autocorking - BOOLEAN
225 Enable TCP auto corking :
226 When applications do consecutive small write()/sendmsg() system calls,
227 we try to coalesce these small writes as much as possible, to lower
228 total amount of sent packets. This is done if at least one prior
229 packet for the flow is waiting in Qdisc queues or device transmit
230 queue. Applications can still use TCP_CORK for optimal behavior
231 when they know how/when to uncork their sockets.
234 tcp_available_congestion_control - STRING
235 Shows the available congestion control choices that are registered.
236 More congestion control algorithms may be available as modules,
239 tcp_base_mss - INTEGER
240 The initial value of search_low to be used by the packetization layer
241 Path MTU discovery (MTU probing). If MTU probing is enabled,
242 this is the initial MSS used by the connection.
244 tcp_congestion_control - STRING
245 Set the congestion control algorithm to be used for new
246 connections. The algorithm "reno" is always available, but
247 additional choices may be available based on kernel configuration.
248 Default is set as part of kernel configuration.
249 For passive connections, the listener congestion control choice
251 [see setsockopt(listenfd, SOL_TCP, TCP_CONGESTION, "name" ...) ]
254 Allows TCP to send "duplicate" SACKs.
256 tcp_early_retrans - INTEGER
257 Tail loss probe (TLP) converts RTOs occurring due to tail
258 losses into fast recovery (draft-ietf-tcpm-rack). Note that
259 TLP requires RACK to function properly (see tcp_recovery below)
266 Control use of Explicit Congestion Notification (ECN) by TCP.
267 ECN is used only when both ends of the TCP connection indicate
268 support for it. This feature is useful in avoiding losses due
269 to congestion by allowing supporting routers to signal
270 congestion before having to drop packets.
272 0 Disable ECN. Neither initiate nor accept ECN.
273 1 Enable ECN when requested by incoming connections and
274 also request ECN on outgoing connection attempts.
275 2 Enable ECN when requested by incoming connections
276 but do not request ECN on outgoing connections.
279 tcp_ecn_fallback - BOOLEAN
280 If the kernel detects that ECN connection misbehaves, enable fall
281 back to non-ECN. Currently, this knob implements the fallback
282 from RFC3168, section 6.1.1.1., but we reserve that in future,
283 additional detection mechanisms could be implemented under this
284 knob. The value is not used, if tcp_ecn or per route (or congestion
285 control) ECN settings are disabled.
286 Default: 1 (fallback enabled)
289 This is a legacy option, it has no effect anymore.
291 tcp_fin_timeout - INTEGER
292 The length of time an orphaned (no longer referenced by any
293 application) connection will remain in the FIN_WAIT_2 state
294 before it is aborted at the local end. While a perfectly
295 valid "receive only" state for an un-orphaned connection, an
296 orphaned connection in FIN_WAIT_2 state could otherwise wait
297 forever for the remote to close its end of the connection.
302 Enables Forward RTO-Recovery (F-RTO) defined in RFC5682.
303 F-RTO is an enhanced recovery algorithm for TCP retransmission
304 timeouts. It is particularly beneficial in networks where the
305 RTT fluctuates (e.g., wireless). F-RTO is sender-side only
306 modification. It does not require any support from the peer.
308 By default it's enabled with a non-zero value. 0 disables F-RTO.
310 tcp_invalid_ratelimit - INTEGER
311 Limit the maximal rate for sending duplicate acknowledgments
312 in response to incoming TCP packets that are for an existing
313 connection but that are invalid due to any of these reasons:
315 (a) out-of-window sequence number,
316 (b) out-of-window acknowledgment number, or
317 (c) PAWS (Protection Against Wrapped Sequence numbers) check failure
319 This can help mitigate simple "ack loop" DoS attacks, wherein
320 a buggy or malicious middlebox or man-in-the-middle can
321 rewrite TCP header fields in manner that causes each endpoint
322 to think that the other is sending invalid TCP segments, thus
323 causing each side to send an unterminating stream of duplicate
324 acknowledgments for invalid segments.
326 Using 0 disables rate-limiting of dupacks in response to
327 invalid segments; otherwise this value specifies the minimal
328 space between sending such dupacks, in milliseconds.
330 Default: 500 (milliseconds).
332 tcp_keepalive_time - INTEGER
333 How often TCP sends out keepalive messages when keepalive is enabled.
336 tcp_keepalive_probes - INTEGER
337 How many keepalive probes TCP sends out, until it decides that the
338 connection is broken. Default value: 9.
340 tcp_keepalive_intvl - INTEGER
341 How frequently the probes are send out. Multiplied by
342 tcp_keepalive_probes it is time to kill not responding connection,
343 after probes started. Default value: 75sec i.e. connection
344 will be aborted after ~11 minutes of retries.
346 tcp_l3mdev_accept - BOOLEAN
347 Enables child sockets to inherit the L3 master device index.
348 Enabling this option allows a "global" listen socket to work
349 across L3 master domains (e.g., VRFs) with connected sockets
350 derived from the listen socket to be bound to the L3 domain in
351 which the packets originated. Only valid when the kernel was
352 compiled with CONFIG_NET_L3_MASTER_DEV.
354 tcp_low_latency - BOOLEAN
355 This is a legacy option, it has no effect anymore.
357 tcp_max_orphans - INTEGER
358 Maximal number of TCP sockets not attached to any user file handle,
359 held by system. If this number is exceeded orphaned connections are
360 reset immediately and warning is printed. This limit exists
361 only to prevent simple DoS attacks, you _must_ not rely on this
362 or lower the limit artificially, but rather increase it
363 (probably, after increasing installed memory),
364 if network conditions require more than default value,
365 and tune network services to linger and kill such states
366 more aggressively. Let me to remind again: each orphan eats
367 up to ~64K of unswappable memory.
369 tcp_max_syn_backlog - INTEGER
370 Maximal number of remembered connection requests, which have not
371 received an acknowledgment from connecting client.
372 The minimal value is 128 for low memory machines, and it will
373 increase in proportion to the memory of machine.
374 If server suffers from overload, try increasing this number.
376 tcp_max_tw_buckets - INTEGER
377 Maximal number of timewait sockets held by system simultaneously.
378 If this number is exceeded time-wait socket is immediately destroyed
379 and warning is printed. This limit exists only to prevent
380 simple DoS attacks, you _must_ not lower the limit artificially,
381 but rather increase it (probably, after increasing installed memory),
382 if network conditions require more than default value.
384 tcp_mem - vector of 3 INTEGERs: min, pressure, max
385 min: below this number of pages TCP is not bothered about its
388 pressure: when amount of memory allocated by TCP exceeds this number
389 of pages, TCP moderates its memory consumption and enters memory
390 pressure mode, which is exited when memory consumption falls
393 max: number of pages allowed for queueing by all TCP sockets.
395 Defaults are calculated at boot time from amount of available
398 tcp_min_rtt_wlen - INTEGER
399 The window length of the windowed min filter to track the minimum RTT.
400 A shorter window lets a flow more quickly pick up new (higher)
401 minimum RTT when it is moved to a longer path (e.g., due to traffic
402 engineering). A longer window makes the filter more resistant to RTT
403 inflations such as transient congestion. The unit is seconds.
406 tcp_moderate_rcvbuf - BOOLEAN
407 If set, TCP performs receive buffer auto-tuning, attempting to
408 automatically size the buffer (no greater than tcp_rmem[2]) to
409 match the size required by the path for full throughput. Enabled by
412 tcp_mtu_probing - INTEGER
413 Controls TCP Packetization-Layer Path MTU Discovery. Takes three
416 1 - Disabled by default, enabled when an ICMP black hole detected
417 2 - Always enabled, use initial MSS of tcp_base_mss.
419 tcp_probe_interval - INTEGER
420 Controls how often to start TCP Packetization-Layer Path MTU
421 Discovery reprobe. The default is reprobing every 10 minutes as
424 tcp_probe_threshold - INTEGER
425 Controls when TCP Packetization-Layer Path MTU Discovery probing
426 will stop in respect to the width of search range in bytes. Default
429 tcp_no_metrics_save - BOOLEAN
430 By default, TCP saves various connection metrics in the route cache
431 when the connection closes, so that connections established in the
432 near future can use these to set initial conditions. Usually, this
433 increases overall performance, but may sometimes cause performance
434 degradation. If set, TCP will not cache metrics on closing
437 tcp_orphan_retries - INTEGER
438 This value influences the timeout of a locally closed TCP connection,
439 when RTO retransmissions remain unacknowledged.
440 See tcp_retries2 for more details.
442 The default value is 8.
443 If your machine is a loaded WEB server,
444 you should think about lowering this value, such sockets
445 may consume significant resources. Cf. tcp_max_orphans.
447 tcp_recovery - INTEGER
448 This value is a bitmap to enable various experimental loss recovery
451 RACK: 0x1 enables the RACK loss detection for fast detection of lost
452 retransmissions and tail drops. It also subsumes and disables
453 RFC6675 recovery for SACK connections.
454 RACK: 0x2 makes RACK's reordering window static (min_rtt/4).
455 RACK: 0x4 disables RACK's DUPACK threshold heuristic
459 tcp_reordering - INTEGER
460 Initial reordering level of packets in a TCP stream.
461 TCP stack can then dynamically adjust flow reordering level
462 between this initial value and tcp_max_reordering
465 tcp_max_reordering - INTEGER
466 Maximal reordering level of packets in a TCP stream.
467 300 is a fairly conservative value, but you might increase it
468 if paths are using per packet load balancing (like bonding rr mode)
471 tcp_retrans_collapse - BOOLEAN
472 Bug-to-bug compatibility with some broken printers.
473 On retransmit try to send bigger packets to work around bugs in
476 tcp_retries1 - INTEGER
477 This value influences the time, after which TCP decides, that
478 something is wrong due to unacknowledged RTO retransmissions,
479 and reports this suspicion to the network layer.
480 See tcp_retries2 for more details.
482 RFC 1122 recommends at least 3 retransmissions, which is the
485 tcp_retries2 - INTEGER
486 This value influences the timeout of an alive TCP connection,
487 when RTO retransmissions remain unacknowledged.
488 Given a value of N, a hypothetical TCP connection following
489 exponential backoff with an initial RTO of TCP_RTO_MIN would
490 retransmit N times before killing the connection at the (N+1)th RTO.
492 The default value of 15 yields a hypothetical timeout of 924.6
493 seconds and is a lower bound for the effective timeout.
494 TCP will effectively time out at the first RTO which exceeds the
495 hypothetical timeout.
497 RFC 1122 recommends at least 100 seconds for the timeout,
498 which corresponds to a value of at least 8.
500 tcp_rfc1337 - BOOLEAN
501 If set, the TCP stack behaves conforming to RFC1337. If unset,
502 we are not conforming to RFC, but prevent TCP TIME_WAIT
506 tcp_rmem - vector of 3 INTEGERs: min, default, max
507 min: Minimal size of receive buffer used by TCP sockets.
508 It is guaranteed to each TCP socket, even under moderate memory
512 default: initial size of receive buffer used by TCP sockets.
513 This value overrides net.core.rmem_default used by other protocols.
514 Default: 87380 bytes. This value results in window of 65535 with
515 default setting of tcp_adv_win_scale and tcp_app_win:0 and a bit
516 less for default tcp_app_win. See below about these variables.
518 max: maximal size of receive buffer allowed for automatically
519 selected receiver buffers for TCP socket. This value does not override
520 net.core.rmem_max. Calling setsockopt() with SO_RCVBUF disables
521 automatic tuning of that socket's receive buffer size, in which
522 case this value is ignored.
523 Default: between 87380B and 6MB, depending on RAM size.
526 Enable select acknowledgments (SACKS).
528 tcp_comp_sack_delay_ns - LONG INTEGER
529 TCP tries to reduce number of SACK sent, using a timer
530 based on 5% of SRTT, capped by this sysctl, in nano seconds.
531 The default is 1ms, based on TSO autosizing period.
533 Default : 1,000,000 ns (1 ms)
535 tcp_comp_sack_nr - INTEGER
536 Max numer of SACK that can be compressed.
537 Using 0 disables SACK compression.
541 tcp_slow_start_after_idle - BOOLEAN
542 If set, provide RFC2861 behavior and time out the congestion
543 window after an idle period. An idle period is defined at
544 the current RTO. If unset, the congestion window will not
545 be timed out after an idle period.
549 Use the Host requirements interpretation of the TCP urgent pointer field.
550 Most hosts use the older BSD interpretation, so if you turn this on
551 Linux might not communicate correctly with them.
554 tcp_synack_retries - INTEGER
555 Number of times SYNACKs for a passive TCP connection attempt will
556 be retransmitted. Should not be higher than 255. Default value
557 is 5, which corresponds to 31seconds till the last retransmission
558 with the current initial RTO of 1second. With this the final timeout
559 for a passive TCP connection will happen after 63seconds.
561 tcp_syncookies - BOOLEAN
562 Only valid when the kernel was compiled with CONFIG_SYN_COOKIES
563 Send out syncookies when the syn backlog queue of a socket
564 overflows. This is to prevent against the common 'SYN flood attack'
567 Note, that syncookies is fallback facility.
568 It MUST NOT be used to help highly loaded servers to stand
569 against legal connection rate. If you see SYN flood warnings
570 in your logs, but investigation shows that they occur
571 because of overload with legal connections, you should tune
572 another parameters until this warning disappear.
573 See: tcp_max_syn_backlog, tcp_synack_retries, tcp_abort_on_overflow.
575 syncookies seriously violate TCP protocol, do not allow
576 to use TCP extensions, can result in serious degradation
577 of some services (f.e. SMTP relaying), visible not by you,
578 but your clients and relays, contacting you. While you see
579 SYN flood warnings in logs not being really flooded, your server
580 is seriously misconfigured.
582 If you want to test which effects syncookies have to your
583 network connections you can set this knob to 2 to enable
584 unconditionally generation of syncookies.
586 tcp_fastopen - INTEGER
587 Enable TCP Fast Open (RFC7413) to send and accept data in the opening
590 The client support is enabled by flag 0x1 (on by default). The client
591 then must use sendmsg() or sendto() with the MSG_FASTOPEN flag,
592 rather than connect() to send data in SYN.
594 The server support is enabled by flag 0x2 (off by default). Then
595 either enable for all listeners with another flag (0x400) or
596 enable individual listeners via TCP_FASTOPEN socket option with
597 the option value being the length of the syn-data backlog.
599 The values (bitmap) are
600 0x1: (client) enables sending data in the opening SYN on the client.
601 0x2: (server) enables the server support, i.e., allowing data in
602 a SYN packet to be accepted and passed to the
603 application before 3-way handshake finishes.
604 0x4: (client) send data in the opening SYN regardless of cookie
605 availability and without a cookie option.
606 0x200: (server) accept data-in-SYN w/o any cookie option present.
607 0x400: (server) enable all listeners to support Fast Open by
608 default without explicit TCP_FASTOPEN socket option.
612 Note that that additional client or server features are only
613 effective if the basic support (0x1 and 0x2) are enabled respectively.
615 tcp_fastopen_blackhole_timeout_sec - INTEGER
616 Initial time period in second to disable Fastopen on active TCP sockets
617 when a TFO firewall blackhole issue happens.
618 This time period will grow exponentially when more blackhole issues
619 get detected right after Fastopen is re-enabled and will reset to
620 initial value when the blackhole issue goes away.
621 0 to disable the blackhole detection.
622 By default, it is set to 1hr.
624 tcp_syn_retries - INTEGER
625 Number of times initial SYNs for an active TCP connection attempt
626 will be retransmitted. Should not be higher than 127. Default value
627 is 6, which corresponds to 63seconds till the last retransmission
628 with the current initial RTO of 1second. With this the final timeout
629 for an active TCP connection attempt will happen after 127seconds.
631 tcp_timestamps - INTEGER
632 Enable timestamps as defined in RFC1323.
634 1: Enable timestamps as defined in RFC1323 and use random offset for
635 each connection rather than only using the current time.
636 2: Like 1, but without random offsets.
639 tcp_min_tso_segs - INTEGER
640 Minimal number of segments per TSO frame.
641 Since linux-3.12, TCP does an automatic sizing of TSO frames,
642 depending on flow rate, instead of filling 64Kbytes packets.
643 For specific usages, it's possible to force TCP to build big
644 TSO frames. Note that TCP stack might split too big TSO packets
645 if available window is too small.
648 tcp_pacing_ss_ratio - INTEGER
649 sk->sk_pacing_rate is set by TCP stack using a ratio applied
650 to current rate. (current_rate = cwnd * mss / srtt)
651 If TCP is in slow start, tcp_pacing_ss_ratio is applied
652 to let TCP probe for bigger speeds, assuming cwnd can be
653 doubled every other RTT.
656 tcp_pacing_ca_ratio - INTEGER
657 sk->sk_pacing_rate is set by TCP stack using a ratio applied
658 to current rate. (current_rate = cwnd * mss / srtt)
659 If TCP is in congestion avoidance phase, tcp_pacing_ca_ratio
660 is applied to conservatively probe for bigger throughput.
663 tcp_tso_win_divisor - INTEGER
664 This allows control over what percentage of the congestion window
665 can be consumed by a single TSO frame.
666 The setting of this parameter is a choice between burstiness and
667 building larger TSO frames.
670 tcp_tw_reuse - INTEGER
671 Enable reuse of TIME-WAIT sockets for new connections when it is
672 safe from protocol viewpoint.
675 2 - enable for loopback traffic only
676 It should not be changed without advice/request of technical
680 tcp_window_scaling - BOOLEAN
681 Enable window scaling as defined in RFC1323.
683 tcp_wmem - vector of 3 INTEGERs: min, default, max
684 min: Amount of memory reserved for send buffers for TCP sockets.
685 Each TCP socket has rights to use it due to fact of its birth.
688 default: initial size of send buffer used by TCP sockets. This
689 value overrides net.core.wmem_default used by other protocols.
690 It is usually lower than net.core.wmem_default.
693 max: Maximal amount of memory allowed for automatically tuned
694 send buffers for TCP sockets. This value does not override
695 net.core.wmem_max. Calling setsockopt() with SO_SNDBUF disables
696 automatic tuning of that socket's send buffer size, in which case
697 this value is ignored.
698 Default: between 64K and 4MB, depending on RAM size.
700 tcp_notsent_lowat - UNSIGNED INTEGER
701 A TCP socket can control the amount of unsent bytes in its write queue,
702 thanks to TCP_NOTSENT_LOWAT socket option. poll()/select()/epoll()
703 reports POLLOUT events if the amount of unsent bytes is below a per
704 socket value, and if the write queue is not full. sendmsg() will
705 also not add new buffers if the limit is hit.
707 This global variable controls the amount of unsent data for
708 sockets not using TCP_NOTSENT_LOWAT. For these sockets, a change
709 to the global variable has immediate effect.
711 Default: UINT_MAX (0xFFFFFFFF)
713 tcp_workaround_signed_windows - BOOLEAN
714 If set, assume no receipt of a window scaling option means the
715 remote TCP is broken and treats the window as a signed quantity.
716 If unset, assume the remote TCP is not broken even if we do
717 not receive a window scaling option from them.
720 tcp_thin_linear_timeouts - BOOLEAN
721 Enable dynamic triggering of linear timeouts for thin streams.
722 If set, a check is performed upon retransmission by timeout to
723 determine if the stream is thin (less than 4 packets in flight).
724 As long as the stream is found to be thin, up to 6 linear
725 timeouts may be performed before exponential backoff mode is
726 initiated. This improves retransmission latency for
727 non-aggressive thin streams, often found to be time-dependent.
728 For more information on thin streams, see
729 Documentation/networking/tcp-thin.txt
732 tcp_limit_output_bytes - INTEGER
733 Controls TCP Small Queue limit per tcp socket.
734 TCP bulk sender tends to increase packets in flight until it
735 gets losses notifications. With SNDBUF autotuning, this can
736 result in a large amount of packets queued on the local machine
737 (e.g.: qdiscs, CPU backlog, or device) hurting latency of other
738 flows, for typical pfifo_fast qdiscs. tcp_limit_output_bytes
739 limits the number of bytes on qdisc or device to reduce artificial
740 RTT/cwnd and reduce bufferbloat.
743 tcp_challenge_ack_limit - INTEGER
744 Limits number of Challenge ACK sent per second, as recommended
745 in RFC 5961 (Improving TCP's Robustness to Blind In-Window Attacks)
750 udp_l3mdev_accept - BOOLEAN
751 Enabling this option allows a "global" bound socket to work
752 across L3 master domains (e.g., VRFs) with packets capable of
753 being received regardless of the L3 domain in which they
754 originated. Only valid when the kernel was compiled with
755 CONFIG_NET_L3_MASTER_DEV.
757 udp_mem - vector of 3 INTEGERs: min, pressure, max
758 Number of pages allowed for queueing by all UDP sockets.
760 min: Below this number of pages UDP is not bothered about its
761 memory appetite. When amount of memory allocated by UDP exceeds
762 this number, UDP starts to moderate memory usage.
764 pressure: This value was introduced to follow format of tcp_mem.
766 max: Number of pages allowed for queueing by all UDP sockets.
768 Default is calculated at boot time from amount of available memory.
770 udp_rmem_min - INTEGER
771 Minimal size of receive buffer used by UDP sockets in moderation.
772 Each UDP socket is able to use the size for receiving data, even if
773 total pages of UDP sockets exceed udp_mem pressure. The unit is byte.
776 udp_wmem_min - INTEGER
777 Minimal size of send buffer used by UDP sockets in moderation.
778 Each UDP socket is able to use the size for sending data, even if
779 total pages of UDP sockets exceed udp_mem pressure. The unit is byte.
784 cipso_cache_enable - BOOLEAN
785 If set, enable additions to and lookups from the CIPSO label mapping
786 cache. If unset, additions are ignored and lookups always result in a
787 miss. However, regardless of the setting the cache is still
788 invalidated when required when means you can safely toggle this on and
789 off and the cache will always be "safe".
792 cipso_cache_bucket_size - INTEGER
793 The CIPSO label cache consists of a fixed size hash table with each
794 hash bucket containing a number of cache entries. This variable limits
795 the number of entries in each hash bucket; the larger the value the
796 more CIPSO label mappings that can be cached. When the number of
797 entries in a given hash bucket reaches this limit adding new entries
798 causes the oldest entry in the bucket to be removed to make room.
801 cipso_rbm_optfmt - BOOLEAN
802 Enable the "Optimized Tag 1 Format" as defined in section 3.4.2.6 of
803 the CIPSO draft specification (see Documentation/netlabel for details).
804 This means that when set the CIPSO tag will be padded with empty
805 categories in order to make the packet data 32-bit aligned.
808 cipso_rbm_structvalid - BOOLEAN
809 If set, do a very strict check of the CIPSO option when
810 ip_options_compile() is called. If unset, relax the checks done during
811 ip_options_compile(). Either way is "safe" as errors are caught else
812 where in the CIPSO processing code but setting this to 0 (False) should
813 result in less work (i.e. it should be faster) but could cause problems
814 with other implementations that require strict checking.
819 ip_local_port_range - 2 INTEGERS
820 Defines the local port range that is used by TCP and UDP to
821 choose the local port. The first number is the first, the
822 second the last local port number.
823 If possible, it is better these numbers have different parity.
824 (one even and one odd values)
825 The default values are 32768 and 60999 respectively.
827 ip_local_reserved_ports - list of comma separated ranges
828 Specify the ports which are reserved for known third-party
829 applications. These ports will not be used by automatic port
830 assignments (e.g. when calling connect() or bind() with port
831 number 0). Explicit port allocation behavior is unchanged.
833 The format used for both input and output is a comma separated
834 list of ranges (e.g. "1,2-4,10-10" for ports 1, 2, 3, 4 and
835 10). Writing to the file will clear all previously reserved
836 ports and update the current list with the one given in the
839 Note that ip_local_port_range and ip_local_reserved_ports
840 settings are independent and both are considered by the kernel
841 when determining which ports are available for automatic port
844 You can reserve ports which are not in the current
845 ip_local_port_range, e.g.:
847 $ cat /proc/sys/net/ipv4/ip_local_port_range
849 $ cat /proc/sys/net/ipv4/ip_local_reserved_ports
852 although this is redundant. However such a setting is useful
853 if later the port range is changed to a value that will
854 include the reserved ports.
858 ip_unprivileged_port_start - INTEGER
859 This is a per-namespace sysctl. It defines the first
860 unprivileged port in the network namespace. Privileged ports
861 require root or CAP_NET_BIND_SERVICE in order to bind to them.
862 To disable all privileged ports, set this to 0. It may not
863 overlap with the ip_local_reserved_ports range.
867 ip_nonlocal_bind - BOOLEAN
868 If set, allows processes to bind() to non-local IP addresses,
869 which can be quite useful - but may break some applications.
873 If set non-zero, enables support for dynamic addresses.
874 If set to a non-zero value larger than 1, a kernel log
875 message will be printed when dynamic address rewriting
879 ip_early_demux - BOOLEAN
880 Optimize input packet processing down to one demux for
881 certain kinds of local sockets. Currently we only do this
882 for established TCP and connected UDP sockets.
884 It may add an additional cost for pure routing workloads that
885 reduces overall throughput, in such case you should disable it.
888 tcp_early_demux - BOOLEAN
889 Enable early demux for established TCP sockets.
892 udp_early_demux - BOOLEAN
893 Enable early demux for connected UDP sockets. Disable this if
894 your system could experience more unconnected load.
897 icmp_echo_ignore_all - BOOLEAN
898 If set non-zero, then the kernel will ignore all ICMP ECHO
902 icmp_echo_ignore_broadcasts - BOOLEAN
903 If set non-zero, then the kernel will ignore all ICMP ECHO and
904 TIMESTAMP requests sent to it via broadcast/multicast.
907 icmp_ratelimit - INTEGER
908 Limit the maximal rates for sending ICMP packets whose type matches
909 icmp_ratemask (see below) to specific targets.
910 0 to disable any limiting,
911 otherwise the minimal space between responses in milliseconds.
912 Note that another sysctl, icmp_msgs_per_sec limits the number
913 of ICMP packets sent on all targets.
916 icmp_msgs_per_sec - INTEGER
917 Limit maximal number of ICMP packets sent per second from this host.
918 Only messages whose type matches icmp_ratemask (see below) are
919 controlled by this limit.
922 icmp_msgs_burst - INTEGER
923 icmp_msgs_per_sec controls number of ICMP packets sent per second,
924 while icmp_msgs_burst controls the burst size of these packets.
927 icmp_ratemask - INTEGER
928 Mask made of ICMP types for which rates are being limited.
929 Significant bits: IHGFEDCBA9876543210
930 Default mask: 0000001100000011000 (6168)
932 Bit definitions (see include/linux/icmp.h):
934 3 Destination Unreachable *
939 C Parameter Problem *
944 H Address Mask Request
947 * These are rate limited by default (see default mask above)
949 icmp_ignore_bogus_error_responses - BOOLEAN
950 Some routers violate RFC1122 by sending bogus responses to broadcast
951 frames. Such violations are normally logged via a kernel warning.
952 If this is set to TRUE, the kernel will not give such warnings, which
953 will avoid log file clutter.
956 icmp_errors_use_inbound_ifaddr - BOOLEAN
958 If zero, icmp error messages are sent with the primary address of
959 the exiting interface.
961 If non-zero, the message will be sent with the primary address of
962 the interface that received the packet that caused the icmp error.
963 This is the behaviour network many administrators will expect from
964 a router. And it can make debugging complicated network layouts
967 Note that if no primary address exists for the interface selected,
968 then the primary address of the first non-loopback interface that
969 has one will be used regardless of this setting.
973 igmp_max_memberships - INTEGER
974 Change the maximum number of multicast groups we can subscribe to.
977 Theoretical maximum value is bounded by having to send a membership
978 report in a single datagram (i.e. the report can't span multiple
979 datagrams, or risk confusing the switch and leaving groups you don't
982 The number of supported groups 'M' is bounded by the number of group
983 report entries you can fit into a single datagram of 65535 bytes.
985 M = 65536-sizeof (ip header)/(sizeof(Group record))
987 Group records are variable length, with a minimum of 12 bytes.
988 So net.ipv4.igmp_max_memberships should not be set higher than:
990 (65536-24) / 12 = 5459
992 The value 5459 assumes no IP header options, so in practice
993 this number may be lower.
995 igmp_max_msf - INTEGER
996 Maximum number of addresses allowed in the source filter list for a
1001 Controls the IGMP query robustness variable (see RFC2236 8.1).
1002 Default: 2 (as specified by RFC2236 8.1)
1003 Minimum: 1 (as specified by RFC6636 4.5)
1005 force_igmp_version - INTEGER
1006 0 - (default) No enforcement of a IGMP version, IGMPv1/v2 fallback
1007 allowed. Will back to IGMPv3 mode again if all IGMPv1/v2 Querier
1008 Present timer expires.
1009 1 - Enforce to use IGMP version 1. Will also reply IGMPv1 report if
1010 receive IGMPv2/v3 query.
1011 2 - Enforce to use IGMP version 2. Will fallback to IGMPv1 if receive
1012 IGMPv1 query message. Will reply report if receive IGMPv3 query.
1013 3 - Enforce to use IGMP version 3. The same react with default 0.
1015 Note: this is not the same with force_mld_version because IGMPv3 RFC3376
1016 Security Considerations does not have clear description that we could
1017 ignore other version messages completely as MLDv2 RFC3810. So make
1018 this value as default 0 is recommended.
1020 conf/interface/* changes special settings per interface (where
1021 "interface" is the name of your network interface)
1023 conf/all/* is special, changes the settings for all interfaces
1025 log_martians - BOOLEAN
1026 Log packets with impossible addresses to kernel log.
1027 log_martians for the interface will be enabled if at least one of
1028 conf/{all,interface}/log_martians is set to TRUE,
1029 it will be disabled otherwise
1031 accept_redirects - BOOLEAN
1032 Accept ICMP redirect messages.
1033 accept_redirects for the interface will be enabled if:
1034 - both conf/{all,interface}/accept_redirects are TRUE in the case
1035 forwarding for the interface is enabled
1037 - at least one of conf/{all,interface}/accept_redirects is TRUE in the
1038 case forwarding for the interface is disabled
1039 accept_redirects for the interface will be disabled otherwise
1043 forwarding - BOOLEAN
1044 Enable IP forwarding on this interface. This controls whether packets
1045 received _on_ this interface can be forwarded.
1047 mc_forwarding - BOOLEAN
1048 Do multicast routing. The kernel needs to be compiled with CONFIG_MROUTE
1049 and a multicast routing daemon is required.
1050 conf/all/mc_forwarding must also be set to TRUE to enable multicast
1051 routing for the interface
1054 Integer value used to differentiate the devices by the medium they
1055 are attached to. Two devices can have different id values when
1056 the broadcast packets are received only on one of them.
1057 The default value 0 means that the device is the only interface
1058 to its medium, value of -1 means that medium is not known.
1060 Currently, it is used to change the proxy_arp behavior:
1061 the proxy_arp feature is enabled for packets forwarded between
1062 two devices attached to different media.
1066 proxy_arp for the interface will be enabled if at least one of
1067 conf/{all,interface}/proxy_arp is set to TRUE,
1068 it will be disabled otherwise
1070 proxy_arp_pvlan - BOOLEAN
1071 Private VLAN proxy arp.
1072 Basically allow proxy arp replies back to the same interface
1073 (from which the ARP request/solicitation was received).
1075 This is done to support (ethernet) switch features, like RFC
1076 3069, where the individual ports are NOT allowed to
1077 communicate with each other, but they are allowed to talk to
1078 the upstream router. As described in RFC 3069, it is possible
1079 to allow these hosts to communicate through the upstream
1080 router by proxy_arp'ing. Don't need to be used together with
1083 This technology is known by different names:
1084 In RFC 3069 it is called VLAN Aggregation.
1085 Cisco and Allied Telesyn call it Private VLAN.
1086 Hewlett-Packard call it Source-Port filtering or port-isolation.
1087 Ericsson call it MAC-Forced Forwarding (RFC Draft).
1089 shared_media - BOOLEAN
1090 Send(router) or accept(host) RFC1620 shared media redirects.
1091 Overrides secure_redirects.
1092 shared_media for the interface will be enabled if at least one of
1093 conf/{all,interface}/shared_media is set to TRUE,
1094 it will be disabled otherwise
1097 secure_redirects - BOOLEAN
1098 Accept ICMP redirect messages only to gateways listed in the
1099 interface's current gateway list. Even if disabled, RFC1122 redirect
1101 Overridden by shared_media.
1102 secure_redirects for the interface will be enabled if at least one of
1103 conf/{all,interface}/secure_redirects is set to TRUE,
1104 it will be disabled otherwise
1107 send_redirects - BOOLEAN
1108 Send redirects, if router.
1109 send_redirects for the interface will be enabled if at least one of
1110 conf/{all,interface}/send_redirects is set to TRUE,
1111 it will be disabled otherwise
1114 bootp_relay - BOOLEAN
1115 Accept packets with source address 0.b.c.d destined
1116 not to this host as local ones. It is supposed, that
1117 BOOTP relay daemon will catch and forward such packets.
1118 conf/all/bootp_relay must also be set to TRUE to enable BOOTP relay
1121 Not Implemented Yet.
1123 accept_source_route - BOOLEAN
1124 Accept packets with SRR option.
1125 conf/all/accept_source_route must also be set to TRUE to accept packets
1126 with SRR option on the interface
1127 default TRUE (router)
1130 accept_local - BOOLEAN
1131 Accept packets with local source addresses. In combination with
1132 suitable routing, this can be used to direct packets between two
1133 local interfaces over the wire and have them accepted properly.
1136 route_localnet - BOOLEAN
1137 Do not consider loopback addresses as martian source or destination
1138 while routing. This enables the use of 127/8 for local routing purposes.
1142 0 - No source validation.
1143 1 - Strict mode as defined in RFC3704 Strict Reverse Path
1144 Each incoming packet is tested against the FIB and if the interface
1145 is not the best reverse path the packet check will fail.
1146 By default failed packets are discarded.
1147 2 - Loose mode as defined in RFC3704 Loose Reverse Path
1148 Each incoming packet's source address is also tested against the FIB
1149 and if the source address is not reachable via any interface
1150 the packet check will fail.
1152 Current recommended practice in RFC3704 is to enable strict mode
1153 to prevent IP spoofing from DDos attacks. If using asymmetric routing
1154 or other complicated routing, then loose mode is recommended.
1156 The max value from conf/{all,interface}/rp_filter is used
1157 when doing source validation on the {interface}.
1159 Default value is 0. Note that some distributions enable it
1162 arp_filter - BOOLEAN
1163 1 - Allows you to have multiple network interfaces on the same
1164 subnet, and have the ARPs for each interface be answered
1165 based on whether or not the kernel would route a packet from
1166 the ARP'd IP out that interface (therefore you must use source
1167 based routing for this to work). In other words it allows control
1168 of which cards (usually 1) will respond to an arp request.
1170 0 - (default) The kernel can respond to arp requests with addresses
1171 from other interfaces. This may seem wrong but it usually makes
1172 sense, because it increases the chance of successful communication.
1173 IP addresses are owned by the complete host on Linux, not by
1174 particular interfaces. Only for more complex setups like load-
1175 balancing, does this behaviour cause problems.
1177 arp_filter for the interface will be enabled if at least one of
1178 conf/{all,interface}/arp_filter is set to TRUE,
1179 it will be disabled otherwise
1181 arp_announce - INTEGER
1182 Define different restriction levels for announcing the local
1183 source IP address from IP packets in ARP requests sent on
1185 0 - (default) Use any local address, configured on any interface
1186 1 - Try to avoid local addresses that are not in the target's
1187 subnet for this interface. This mode is useful when target
1188 hosts reachable via this interface require the source IP
1189 address in ARP requests to be part of their logical network
1190 configured on the receiving interface. When we generate the
1191 request we will check all our subnets that include the
1192 target IP and will preserve the source address if it is from
1193 such subnet. If there is no such subnet we select source
1194 address according to the rules for level 2.
1195 2 - Always use the best local address for this target.
1196 In this mode we ignore the source address in the IP packet
1197 and try to select local address that we prefer for talks with
1198 the target host. Such local address is selected by looking
1199 for primary IP addresses on all our subnets on the outgoing
1200 interface that include the target IP address. If no suitable
1201 local address is found we select the first local address
1202 we have on the outgoing interface or on all other interfaces,
1203 with the hope we will receive reply for our request and
1204 even sometimes no matter the source IP address we announce.
1206 The max value from conf/{all,interface}/arp_announce is used.
1208 Increasing the restriction level gives more chance for
1209 receiving answer from the resolved target while decreasing
1210 the level announces more valid sender's information.
1212 arp_ignore - INTEGER
1213 Define different modes for sending replies in response to
1214 received ARP requests that resolve local target IP addresses:
1215 0 - (default): reply for any local target IP address, configured
1217 1 - reply only if the target IP address is local address
1218 configured on the incoming interface
1219 2 - reply only if the target IP address is local address
1220 configured on the incoming interface and both with the
1221 sender's IP address are part from same subnet on this interface
1222 3 - do not reply for local addresses configured with scope host,
1223 only resolutions for global and link addresses are replied
1225 8 - do not reply for all local addresses
1227 The max value from conf/{all,interface}/arp_ignore is used
1228 when ARP request is received on the {interface}
1230 arp_notify - BOOLEAN
1231 Define mode for notification of address and device changes.
1232 0 - (default): do nothing
1233 1 - Generate gratuitous arp requests when device is brought up
1234 or hardware address changes.
1236 arp_accept - BOOLEAN
1237 Define behavior for gratuitous ARP frames who's IP is not
1238 already present in the ARP table:
1239 0 - don't create new entries in the ARP table
1240 1 - create new entries in the ARP table
1242 Both replies and requests type gratuitous arp will trigger the
1243 ARP table to be updated, if this setting is on.
1245 If the ARP table already contains the IP address of the
1246 gratuitous arp frame, the arp table will be updated regardless
1247 if this setting is on or off.
1249 mcast_solicit - INTEGER
1250 The maximum number of multicast probes in INCOMPLETE state,
1251 when the associated hardware address is unknown. Defaults
1254 ucast_solicit - INTEGER
1255 The maximum number of unicast probes in PROBE state, when
1256 the hardware address is being reconfirmed. Defaults to 3.
1258 app_solicit - INTEGER
1259 The maximum number of probes to send to the user space ARP daemon
1260 via netlink before dropping back to multicast probes (see
1261 mcast_resolicit). Defaults to 0.
1263 mcast_resolicit - INTEGER
1264 The maximum number of multicast probes after unicast and
1265 app probes in PROBE state. Defaults to 0.
1267 disable_policy - BOOLEAN
1268 Disable IPSEC policy (SPD) for this interface
1270 disable_xfrm - BOOLEAN
1271 Disable IPSEC encryption on this interface, whatever the policy
1273 igmpv2_unsolicited_report_interval - INTEGER
1274 The interval in milliseconds in which the next unsolicited
1275 IGMPv1 or IGMPv2 report retransmit will take place.
1276 Default: 10000 (10 seconds)
1278 igmpv3_unsolicited_report_interval - INTEGER
1279 The interval in milliseconds in which the next unsolicited
1280 IGMPv3 report retransmit will take place.
1281 Default: 1000 (1 seconds)
1283 promote_secondaries - BOOLEAN
1284 When a primary IP address is removed from this interface
1285 promote a corresponding secondary IP address instead of
1286 removing all the corresponding secondary IP addresses.
1288 drop_unicast_in_l2_multicast - BOOLEAN
1289 Drop any unicast IP packets that are received in link-layer
1290 multicast (or broadcast) frames.
1291 This behavior (for multicast) is actually a SHOULD in RFC
1292 1122, but is disabled by default for compatibility reasons.
1295 drop_gratuitous_arp - BOOLEAN
1296 Drop all gratuitous ARP frames, for example if there's a known
1297 good ARP proxy on the network and such frames need not be used
1298 (or in the case of 802.11, must not be used to prevent attacks.)
1303 Allows you to write a number, which can be used as required.
1306 xfrm4_gc_thresh - INTEGER
1307 The threshold at which we will start garbage collecting for IPv4
1308 destination cache entries. At twice this value the system will
1309 refuse new allocations.
1311 igmp_link_local_mcast_reports - BOOLEAN
1312 Enable IGMP reports for link local multicast groups in the
1317 kuznet@ms2.inr.ac.ru
1323 delon.nicolas@wanadoo.fr
1328 /proc/sys/net/ipv6/* Variables:
1330 IPv6 has no global variables such as tcp_*. tcp_* settings under ipv4/ also
1331 apply to IPv6 [XXX?].
1333 bindv6only - BOOLEAN
1334 Default value for IPV6_V6ONLY socket option,
1335 which restricts use of the IPv6 socket to IPv6 communication
1337 TRUE: disable IPv4-mapped address feature
1338 FALSE: enable IPv4-mapped address feature
1340 Default: FALSE (as specified in RFC3493)
1342 flowlabel_consistency - BOOLEAN
1343 Protect the consistency (and unicity) of flow label.
1344 You have to disable it to use IPV6_FL_F_REFLECT flag on the
1350 auto_flowlabels - INTEGER
1351 Automatically generate flow labels based on a flow hash of the
1352 packet. This allows intermediate devices, such as routers, to
1353 identify packet flows for mechanisms like Equal Cost Multipath
1354 Routing (see RFC 6438).
1355 0: automatic flow labels are completely disabled
1356 1: automatic flow labels are enabled by default, they can be
1357 disabled on a per socket basis using the IPV6_AUTOFLOWLABEL
1359 2: automatic flow labels are allowed, they may be enabled on a
1360 per socket basis using the IPV6_AUTOFLOWLABEL socket option
1361 3: automatic flow labels are enabled and enforced, they cannot
1362 be disabled by the socket option
1365 flowlabel_state_ranges - BOOLEAN
1366 Split the flow label number space into two ranges. 0-0x7FFFF is
1367 reserved for the IPv6 flow manager facility, 0x80000-0xFFFFF
1368 is reserved for stateless flow labels as described in RFC6437.
1373 flowlabel_reflect - BOOLEAN
1374 Automatically reflect the flow label. Needed for Path MTU
1375 Discovery to work with Equal Cost Multipath Routing in anycast
1376 environments. See RFC 7690 and:
1377 https://tools.ietf.org/html/draft-wang-6man-flow-label-reflection-01
1382 fib_multipath_hash_policy - INTEGER
1383 Controls which hash policy to use for multipath routes.
1384 Default: 0 (Layer 3)
1386 0 - Layer 3 (source and destination addresses plus flow label)
1387 1 - Layer 4 (standard 5-tuple)
1389 anycast_src_echo_reply - BOOLEAN
1390 Controls the use of anycast addresses as source addresses for ICMPv6
1396 idgen_delay - INTEGER
1397 Controls the delay in seconds after which time to retry
1398 privacy stable address generation if a DAD conflict is
1400 Default: 1 (as specified in RFC7217)
1402 idgen_retries - INTEGER
1403 Controls the number of retries to generate a stable privacy
1404 address if a DAD conflict is detected.
1405 Default: 3 (as specified in RFC7217)
1408 Controls the MLD query robustness variable (see RFC3810 9.1).
1409 Default: 2 (as specified by RFC3810 9.1)
1410 Minimum: 1 (as specified by RFC6636 4.5)
1412 max_dst_opts_number - INTEGER
1413 Maximum number of non-padding TLVs allowed in a Destination
1414 options extension header. If this value is less than zero
1415 then unknown options are disallowed and the number of known
1416 TLVs allowed is the absolute value of this number.
1419 max_hbh_opts_number - INTEGER
1420 Maximum number of non-padding TLVs allowed in a Hop-by-Hop
1421 options extension header. If this value is less than zero
1422 then unknown options are disallowed and the number of known
1423 TLVs allowed is the absolute value of this number.
1426 max_dst_opts_length - INTEGER
1427 Maximum length allowed for a Destination options extension
1429 Default: INT_MAX (unlimited)
1431 max_hbh_length - INTEGER
1432 Maximum length allowed for a Hop-by-Hop options extension
1434 Default: INT_MAX (unlimited)
1438 ip6frag_high_thresh - INTEGER
1439 Maximum memory used to reassemble IPv6 fragments. When
1440 ip6frag_high_thresh bytes of memory is allocated for this purpose,
1441 the fragment handler will toss packets until ip6frag_low_thresh
1444 ip6frag_low_thresh - INTEGER
1445 See ip6frag_high_thresh
1447 ip6frag_time - INTEGER
1448 Time in seconds to keep an IPv6 fragment in memory.
1450 IPv6 Segment Routing:
1452 seg6_flowlabel - INTEGER
1453 Controls the behaviour of computing the flowlabel of outer
1454 IPv6 header in case of SR T.encaps
1456 -1 set flowlabel to zero.
1457 0 copy flowlabel from Inner packet in case of Inner IPv6
1458 (Set flowlabel to 0 in case IPv4/L2)
1459 1 Compute the flowlabel using seg6_make_flowlabel()
1464 Change the interface-specific default settings.
1468 Change all the interface-specific settings.
1470 [XXX: Other special features than forwarding?]
1472 conf/all/forwarding - BOOLEAN
1473 Enable global IPv6 forwarding between all interfaces.
1475 IPv4 and IPv6 work differently here; e.g. netfilter must be used
1476 to control which interfaces may forward packets and which not.
1478 This also sets all interfaces' Host/Router setting
1479 'forwarding' to the specified value. See below for details.
1481 This referred to as global forwarding.
1486 fwmark_reflect - BOOLEAN
1487 Controls the fwmark of kernel-generated IPv6 reply packets that are not
1488 associated with a socket for example, TCP RSTs or ICMPv6 echo replies).
1489 If unset, these packets have a fwmark of zero. If set, they have the
1490 fwmark of the packet they are replying to.
1494 Change special settings per interface.
1496 The functional behaviour for certain settings is different
1497 depending on whether local forwarding is enabled or not.
1500 Accept Router Advertisements; autoconfigure using them.
1502 It also determines whether or not to transmit Router
1503 Solicitations. If and only if the functional setting is to
1504 accept Router Advertisements, Router Solicitations will be
1507 Possible values are:
1508 0 Do not accept Router Advertisements.
1509 1 Accept Router Advertisements if forwarding is disabled.
1510 2 Overrule forwarding behaviour. Accept Router Advertisements
1511 even if forwarding is enabled.
1513 Functional default: enabled if local forwarding is disabled.
1514 disabled if local forwarding is enabled.
1516 accept_ra_defrtr - BOOLEAN
1517 Learn default router in Router Advertisement.
1519 Functional default: enabled if accept_ra is enabled.
1520 disabled if accept_ra is disabled.
1522 accept_ra_from_local - BOOLEAN
1523 Accept RA with source-address that is found on local machine
1524 if the RA is otherwise proper and able to be accepted.
1525 Default is to NOT accept these as it may be an un-intended
1529 enabled if accept_ra_from_local is enabled
1530 on a specific interface.
1531 disabled if accept_ra_from_local is disabled
1532 on a specific interface.
1534 accept_ra_min_hop_limit - INTEGER
1535 Minimum hop limit Information in Router Advertisement.
1537 Hop limit Information in Router Advertisement less than this
1538 variable shall be ignored.
1542 accept_ra_pinfo - BOOLEAN
1543 Learn Prefix Information in Router Advertisement.
1545 Functional default: enabled if accept_ra is enabled.
1546 disabled if accept_ra is disabled.
1548 accept_ra_rt_info_min_plen - INTEGER
1549 Minimum prefix length of Route Information in RA.
1551 Route Information w/ prefix smaller than this variable shall
1554 Functional default: 0 if accept_ra_rtr_pref is enabled.
1555 -1 if accept_ra_rtr_pref is disabled.
1557 accept_ra_rt_info_max_plen - INTEGER
1558 Maximum prefix length of Route Information in RA.
1560 Route Information w/ prefix larger than this variable shall
1563 Functional default: 0 if accept_ra_rtr_pref is enabled.
1564 -1 if accept_ra_rtr_pref is disabled.
1566 accept_ra_rtr_pref - BOOLEAN
1567 Accept Router Preference in RA.
1569 Functional default: enabled if accept_ra is enabled.
1570 disabled if accept_ra is disabled.
1572 accept_ra_mtu - BOOLEAN
1573 Apply the MTU value specified in RA option 5 (RFC4861). If
1574 disabled, the MTU specified in the RA will be ignored.
1576 Functional default: enabled if accept_ra is enabled.
1577 disabled if accept_ra is disabled.
1579 accept_redirects - BOOLEAN
1582 Functional default: enabled if local forwarding is disabled.
1583 disabled if local forwarding is enabled.
1585 accept_source_route - INTEGER
1586 Accept source routing (routing extension header).
1588 >= 0: Accept only routing header type 2.
1589 < 0: Do not accept routing header.
1594 Autoconfigure addresses using Prefix Information in Router
1597 Functional default: enabled if accept_ra_pinfo is enabled.
1598 disabled if accept_ra_pinfo is disabled.
1600 dad_transmits - INTEGER
1601 The amount of Duplicate Address Detection probes to send.
1604 forwarding - INTEGER
1605 Configure interface-specific Host/Router behaviour.
1607 Note: It is recommended to have the same setting on all
1608 interfaces; mixed router/host scenarios are rather uncommon.
1610 Possible values are:
1611 0 Forwarding disabled
1612 1 Forwarding enabled
1616 By default, Host behaviour is assumed. This means:
1618 1. IsRouter flag is not set in Neighbour Advertisements.
1619 2. If accept_ra is TRUE (default), transmit Router
1621 3. If accept_ra is TRUE (default), accept Router
1622 Advertisements (and do autoconfiguration).
1623 4. If accept_redirects is TRUE (default), accept Redirects.
1627 If local forwarding is enabled, Router behaviour is assumed.
1628 This means exactly the reverse from the above:
1630 1. IsRouter flag is set in Neighbour Advertisements.
1631 2. Router Solicitations are not sent unless accept_ra is 2.
1632 3. Router Advertisements are ignored unless accept_ra is 2.
1633 4. Redirects are ignored.
1635 Default: 0 (disabled) if global forwarding is disabled (default),
1636 otherwise 1 (enabled).
1639 Default Hop Limit to set.
1643 Default Maximum Transfer Unit
1644 Default: 1280 (IPv6 required minimum)
1646 ip_nonlocal_bind - BOOLEAN
1647 If set, allows processes to bind() to non-local IPv6 addresses,
1648 which can be quite useful - but may break some applications.
1651 router_probe_interval - INTEGER
1652 Minimum interval (in seconds) between Router Probing described
1657 router_solicitation_delay - INTEGER
1658 Number of seconds to wait after interface is brought up
1659 before sending Router Solicitations.
1662 router_solicitation_interval - INTEGER
1663 Number of seconds to wait between Router Solicitations.
1666 router_solicitations - INTEGER
1667 Number of Router Solicitations to send until assuming no
1668 routers are present.
1671 use_oif_addrs_only - BOOLEAN
1672 When enabled, the candidate source addresses for destinations
1673 routed via this interface are restricted to the set of addresses
1674 configured on this interface (vis. RFC 6724, section 4).
1678 use_tempaddr - INTEGER
1679 Preference for Privacy Extensions (RFC3041).
1680 <= 0 : disable Privacy Extensions
1681 == 1 : enable Privacy Extensions, but prefer public
1682 addresses over temporary addresses.
1683 > 1 : enable Privacy Extensions and prefer temporary
1684 addresses over public addresses.
1685 Default: 0 (for most devices)
1686 -1 (for point-to-point devices and loopback devices)
1688 temp_valid_lft - INTEGER
1689 valid lifetime (in seconds) for temporary addresses.
1690 Default: 604800 (7 days)
1692 temp_prefered_lft - INTEGER
1693 Preferred lifetime (in seconds) for temporary addresses.
1694 Default: 86400 (1 day)
1696 keep_addr_on_down - INTEGER
1697 Keep all IPv6 addresses on an interface down event. If set static
1698 global addresses with no expiration time are not flushed.
1703 Default: 0 (addresses are removed)
1705 max_desync_factor - INTEGER
1706 Maximum value for DESYNC_FACTOR, which is a random value
1707 that ensures that clients don't synchronize with each
1708 other and generate new addresses at exactly the same time.
1709 value is in seconds.
1712 regen_max_retry - INTEGER
1713 Number of attempts before give up attempting to generate
1714 valid temporary addresses.
1717 max_addresses - INTEGER
1718 Maximum number of autoconfigured addresses per interface. Setting
1719 to zero disables the limitation. It is not recommended to set this
1720 value too large (or to zero) because it would be an easy way to
1721 crash the kernel by allowing too many addresses to be created.
1724 disable_ipv6 - BOOLEAN
1725 Disable IPv6 operation. If accept_dad is set to 2, this value
1726 will be dynamically set to TRUE if DAD fails for the link-local
1728 Default: FALSE (enable IPv6 operation)
1730 When this value is changed from 1 to 0 (IPv6 is being enabled),
1731 it will dynamically create a link-local address on the given
1732 interface and start Duplicate Address Detection, if necessary.
1734 When this value is changed from 0 to 1 (IPv6 is being disabled),
1735 it will dynamically delete all addresses and routes on the given
1736 interface. From now on it will not possible to add addresses/routes
1737 to the selected interface.
1739 accept_dad - INTEGER
1740 Whether to accept DAD (Duplicate Address Detection).
1742 1: Enable DAD (default)
1743 2: Enable DAD, and disable IPv6 operation if MAC-based duplicate
1744 link-local address has been found.
1746 DAD operation and mode on a given interface will be selected according
1747 to the maximum value of conf/{all,interface}/accept_dad.
1749 force_tllao - BOOLEAN
1750 Enable sending the target link-layer address option even when
1751 responding to a unicast neighbor solicitation.
1754 Quoting from RFC 2461, section 4.4, Target link-layer address:
1756 "The option MUST be included for multicast solicitations in order to
1757 avoid infinite Neighbor Solicitation "recursion" when the peer node
1758 does not have a cache entry to return a Neighbor Advertisements
1759 message. When responding to unicast solicitations, the option can be
1760 omitted since the sender of the solicitation has the correct link-
1761 layer address; otherwise it would not have be able to send the unicast
1762 solicitation in the first place. However, including the link-layer
1763 address in this case adds little overhead and eliminates a potential
1764 race condition where the sender deletes the cached link-layer address
1765 prior to receiving a response to a previous solicitation."
1767 ndisc_notify - BOOLEAN
1768 Define mode for notification of address and device changes.
1769 0 - (default): do nothing
1770 1 - Generate unsolicited neighbour advertisements when device is brought
1771 up or hardware address changes.
1773 ndisc_tclass - INTEGER
1774 The IPv6 Traffic Class to use by default when sending IPv6 Neighbor
1775 Discovery (Router Solicitation, Router Advertisement, Neighbor
1776 Solicitation, Neighbor Advertisement, Redirect) messages.
1777 These 8 bits can be interpreted as 6 high order bits holding the DSCP
1778 value and 2 low order bits representing ECN (which you probably want
1782 mldv1_unsolicited_report_interval - INTEGER
1783 The interval in milliseconds in which the next unsolicited
1784 MLDv1 report retransmit will take place.
1785 Default: 10000 (10 seconds)
1787 mldv2_unsolicited_report_interval - INTEGER
1788 The interval in milliseconds in which the next unsolicited
1789 MLDv2 report retransmit will take place.
1790 Default: 1000 (1 second)
1792 force_mld_version - INTEGER
1793 0 - (default) No enforcement of a MLD version, MLDv1 fallback allowed
1794 1 - Enforce to use MLD version 1
1795 2 - Enforce to use MLD version 2
1797 suppress_frag_ndisc - INTEGER
1798 Control RFC 6980 (Security Implications of IPv6 Fragmentation
1799 with IPv6 Neighbor Discovery) behavior:
1800 1 - (default) discard fragmented neighbor discovery packets
1801 0 - allow fragmented neighbor discovery packets
1803 optimistic_dad - BOOLEAN
1804 Whether to perform Optimistic Duplicate Address Detection (RFC 4429).
1805 0: disabled (default)
1808 Optimistic Duplicate Address Detection for the interface will be enabled
1809 if at least one of conf/{all,interface}/optimistic_dad is set to 1,
1810 it will be disabled otherwise.
1812 use_optimistic - BOOLEAN
1813 If enabled, do not classify optimistic addresses as deprecated during
1814 source address selection. Preferred addresses will still be chosen
1815 before optimistic addresses, subject to other ranking in the source
1816 address selection algorithm.
1817 0: disabled (default)
1820 This will be enabled if at least one of
1821 conf/{all,interface}/use_optimistic is set to 1, disabled otherwise.
1823 stable_secret - IPv6 address
1824 This IPv6 address will be used as a secret to generate IPv6
1825 addresses for link-local addresses and autoconfigured
1826 ones. All addresses generated after setting this secret will
1827 be stable privacy ones by default. This can be changed via the
1828 addrgenmode ip-link. conf/default/stable_secret is used as the
1829 secret for the namespace, the interface specific ones can
1830 overwrite that. Writes to conf/all/stable_secret are refused.
1832 It is recommended to generate this secret during installation
1833 of a system and keep it stable after that.
1835 By default the stable secret is unset.
1837 addr_gen_mode - INTEGER
1838 Defines how link-local and autoconf addresses are generated.
1840 0: generate address based on EUI64 (default)
1841 1: do no generate a link-local address, use EUI64 for addresses generated
1843 2: generate stable privacy addresses, using the secret from
1844 stable_secret (RFC7217)
1845 3: generate stable privacy addresses, using a random secret if unset
1847 drop_unicast_in_l2_multicast - BOOLEAN
1848 Drop any unicast IPv6 packets that are received in link-layer
1849 multicast (or broadcast) frames.
1851 By default this is turned off.
1853 drop_unsolicited_na - BOOLEAN
1854 Drop all unsolicited neighbor advertisements, for example if there's
1855 a known good NA proxy on the network and such frames need not be used
1856 (or in the case of 802.11, must not be used to prevent attacks.)
1858 By default this is turned off.
1860 enhanced_dad - BOOLEAN
1861 Include a nonce option in the IPv6 neighbor solicitation messages used for
1862 duplicate address detection per RFC7527. A received DAD NS will only signal
1863 a duplicate address if the nonce is different. This avoids any false
1864 detection of duplicates due to loopback of the NS messages that we send.
1865 The nonce option will be sent on an interface unless both of
1866 conf/{all,interface}/enhanced_dad are set to FALSE.
1871 Limit the maximal rates for sending ICMPv6 packets.
1872 0 to disable any limiting,
1873 otherwise the minimal space between responses in milliseconds.
1876 xfrm6_gc_thresh - INTEGER
1877 The threshold at which we will start garbage collecting for IPv6
1878 destination cache entries. At twice this value the system will
1879 refuse new allocations.
1883 Pekka Savola <pekkas@netcore.fi>
1884 YOSHIFUJI Hideaki / USAGI Project <yoshfuji@linux-ipv6.org>
1887 /proc/sys/net/bridge/* Variables:
1889 bridge-nf-call-arptables - BOOLEAN
1890 1 : pass bridged ARP traffic to arptables' FORWARD chain.
1894 bridge-nf-call-iptables - BOOLEAN
1895 1 : pass bridged IPv4 traffic to iptables' chains.
1899 bridge-nf-call-ip6tables - BOOLEAN
1900 1 : pass bridged IPv6 traffic to ip6tables' chains.
1904 bridge-nf-filter-vlan-tagged - BOOLEAN
1905 1 : pass bridged vlan-tagged ARP/IP/IPv6 traffic to {arp,ip,ip6}tables.
1909 bridge-nf-filter-pppoe-tagged - BOOLEAN
1910 1 : pass bridged pppoe-tagged IP/IPv6 traffic to {ip,ip6}tables.
1914 bridge-nf-pass-vlan-input-dev - BOOLEAN
1915 1: if bridge-nf-filter-vlan-tagged is enabled, try to find a vlan
1916 interface on the bridge and set the netfilter input device to the vlan.
1917 This allows use of e.g. "iptables -i br0.1" and makes the REDIRECT
1918 target work with vlan-on-top-of-bridge interfaces. When no matching
1919 vlan interface is found, or this switch is off, the input device is
1920 set to the bridge interface.
1921 0: disable bridge netfilter vlan interface lookup.
1924 proc/sys/net/sctp/* Variables:
1926 addip_enable - BOOLEAN
1927 Enable or disable extension of Dynamic Address Reconfiguration
1928 (ADD-IP) functionality specified in RFC5061. This extension provides
1929 the ability to dynamically add and remove new addresses for the SCTP
1932 1: Enable extension.
1934 0: Disable extension.
1939 Enable or disable pf (pf is short for potentially failed) state. A value
1940 of pf_retrans > path_max_retrans also disables pf state. That is, one of
1941 both pf_enable and pf_retrans > path_max_retrans can disable pf state.
1942 Since pf_retrans and path_max_retrans can be changed by userspace
1943 application, sometimes user expects to disable pf state by the value of
1944 pf_retrans > path_max_retrans, but occasionally the value of pf_retrans
1945 or path_max_retrans is changed by the user application, this pf state is
1946 enabled. As such, it is necessary to add this to dynamically enable
1947 and disable pf state. See:
1948 https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-failover for
1957 addip_noauth_enable - BOOLEAN
1958 Dynamic Address Reconfiguration (ADD-IP) requires the use of
1959 authentication to protect the operations of adding or removing new
1960 addresses. This requirement is mandated so that unauthorized hosts
1961 would not be able to hijack associations. However, older
1962 implementations may not have implemented this requirement while
1963 allowing the ADD-IP extension. For reasons of interoperability,
1964 we provide this variable to control the enforcement of the
1965 authentication requirement.
1967 1: Allow ADD-IP extension to be used without authentication. This
1968 should only be set in a closed environment for interoperability
1969 with older implementations.
1971 0: Enforce the authentication requirement
1975 auth_enable - BOOLEAN
1976 Enable or disable Authenticated Chunks extension. This extension
1977 provides the ability to send and receive authenticated chunks and is
1978 required for secure operation of Dynamic Address Reconfiguration
1981 1: Enable this extension.
1982 0: Disable this extension.
1986 prsctp_enable - BOOLEAN
1987 Enable or disable the Partial Reliability extension (RFC3758) which
1988 is used to notify peers that a given DATA should no longer be expected.
1996 The limit of the number of new packets that can be initially sent. It
1997 controls how bursty the generated traffic can be.
2001 association_max_retrans - INTEGER
2002 Set the maximum number for retransmissions that an association can
2003 attempt deciding that the remote end is unreachable. If this value
2004 is exceeded, the association is terminated.
2008 max_init_retransmits - INTEGER
2009 The maximum number of retransmissions of INIT and COOKIE-ECHO chunks
2010 that an association will attempt before declaring the destination
2011 unreachable and terminating.
2015 path_max_retrans - INTEGER
2016 The maximum number of retransmissions that will be attempted on a given
2017 path. Once this threshold is exceeded, the path is considered
2018 unreachable, and new traffic will use a different path when the
2019 association is multihomed.
2023 pf_retrans - INTEGER
2024 The number of retransmissions that will be attempted on a given path
2025 before traffic is redirected to an alternate transport (should one
2026 exist). Note this is distinct from path_max_retrans, as a path that
2027 passes the pf_retrans threshold can still be used. Its only
2028 deprioritized when a transmission path is selected by the stack. This
2029 setting is primarily used to enable fast failover mechanisms without
2030 having to reduce path_max_retrans to a very low value. See:
2031 http://www.ietf.org/id/draft-nishida-tsvwg-sctp-failover-05.txt
2032 for details. Note also that a value of pf_retrans > path_max_retrans
2033 disables this feature. Since both pf_retrans and path_max_retrans can
2034 be changed by userspace application, a variable pf_enable is used to
2039 rto_initial - INTEGER
2040 The initial round trip timeout value in milliseconds that will be used
2041 in calculating round trip times. This is the initial time interval
2042 for retransmissions.
2047 The maximum value (in milliseconds) of the round trip timeout. This
2048 is the largest time interval that can elapse between retransmissions.
2053 The minimum value (in milliseconds) of the round trip timeout. This
2054 is the smallest time interval the can elapse between retransmissions.
2058 hb_interval - INTEGER
2059 The interval (in milliseconds) between HEARTBEAT chunks. These chunks
2060 are sent at the specified interval on idle paths to probe the state of
2061 a given path between 2 associations.
2065 sack_timeout - INTEGER
2066 The amount of time (in milliseconds) that the implementation will wait
2071 valid_cookie_life - INTEGER
2072 The default lifetime of the SCTP cookie (in milliseconds). The cookie
2073 is used during association establishment.
2077 cookie_preserve_enable - BOOLEAN
2078 Enable or disable the ability to extend the lifetime of the SCTP cookie
2079 that is used during the establishment phase of SCTP association
2081 1: Enable cookie lifetime extension.
2086 cookie_hmac_alg - STRING
2087 Select the hmac algorithm used when generating the cookie value sent by
2088 a listening sctp socket to a connecting client in the INIT-ACK chunk.
2093 Ability to assign md5 or sha1 as the selected alg is predicated on the
2094 configuration of those algorithms at build time (CONFIG_CRYPTO_MD5 and
2095 CONFIG_CRYPTO_SHA1).
2097 Default: Dependent on configuration. MD5 if available, else SHA1 if
2098 available, else none.
2100 rcvbuf_policy - INTEGER
2101 Determines if the receive buffer is attributed to the socket or to
2102 association. SCTP supports the capability to create multiple
2103 associations on a single socket. When using this capability, it is
2104 possible that a single stalled association that's buffering a lot
2105 of data may block other associations from delivering their data by
2106 consuming all of the receive buffer space. To work around this,
2107 the rcvbuf_policy could be set to attribute the receiver buffer space
2108 to each association instead of the socket. This prevents the described
2111 1: rcvbuf space is per association
2112 0: rcvbuf space is per socket
2116 sndbuf_policy - INTEGER
2117 Similar to rcvbuf_policy above, this applies to send buffer space.
2119 1: Send buffer is tracked per association
2120 0: Send buffer is tracked per socket.
2124 sctp_mem - vector of 3 INTEGERs: min, pressure, max
2125 Number of pages allowed for queueing by all SCTP sockets.
2127 min: Below this number of pages SCTP is not bothered about its
2128 memory appetite. When amount of memory allocated by SCTP exceeds
2129 this number, SCTP starts to moderate memory usage.
2131 pressure: This value was introduced to follow format of tcp_mem.
2133 max: Number of pages allowed for queueing by all SCTP sockets.
2135 Default is calculated at boot time from amount of available memory.
2137 sctp_rmem - vector of 3 INTEGERs: min, default, max
2138 Only the first value ("min") is used, "default" and "max" are
2141 min: Minimal size of receive buffer used by SCTP socket.
2142 It is guaranteed to each SCTP socket (but not association) even
2143 under moderate memory pressure.
2147 sctp_wmem - vector of 3 INTEGERs: min, default, max
2148 Currently this tunable has no effect.
2150 addr_scope_policy - INTEGER
2151 Control IPv4 address scoping - draft-stewart-tsvwg-sctp-ipv4-00
2153 0 - Disable IPv4 address scoping
2154 1 - Enable IPv4 address scoping
2155 2 - Follow draft but allow IPv4 private addresses
2156 3 - Follow draft but allow IPv4 link local addresses
2161 /proc/sys/net/core/*
2162 Please see: Documentation/sysctl/net.txt for descriptions of these entries.
2165 /proc/sys/net/unix/*
2166 max_dgram_qlen - INTEGER
2167 The maximum length of dgram socket receive queue