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 hardend 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 route/max_size - INTEGER
67 Maximum number of routes allowed in the kernel. Increase
68 this when using large numbers of interfaces and/or routes.
70 neigh/default/gc_thresh1 - INTEGER
71 Minimum number of entries to keep. Garbage collector will not
72 purge entries if there are fewer than this number.
75 neigh/default/gc_thresh2 - INTEGER
76 Threshold when garbage collector becomes more aggressive about
77 purging entries. Entries older than 5 seconds will be cleared
78 when over this number.
81 neigh/default/gc_thresh3 - INTEGER
82 Maximum number of neighbor entries allowed. Increase this
83 when using large numbers of interfaces and when communicating
84 with large numbers of directly-connected peers.
87 neigh/default/unres_qlen_bytes - INTEGER
88 The maximum number of bytes which may be used by packets
89 queued for each unresolved address by other network layers.
91 Setting negative value is meaningless and will return error.
92 Default: 65536 Bytes(64KB)
94 neigh/default/unres_qlen - INTEGER
95 The maximum number of packets which may be queued for each
96 unresolved address by other network layers.
97 (deprecated in linux 3.3) : use unres_qlen_bytes instead.
98 Prior to linux 3.3, the default value is 3 which may cause
99 unexpected packet loss. The current default value is calculated
100 according to default value of unres_qlen_bytes and true size of
104 mtu_expires - INTEGER
105 Time, in seconds, that cached PMTU information is kept.
107 min_adv_mss - INTEGER
108 The advertised MSS depends on the first hop route MTU, but will
109 never be lower than this setting.
113 ipfrag_high_thresh - INTEGER
114 Maximum memory used to reassemble IP fragments. When
115 ipfrag_high_thresh bytes of memory is allocated for this purpose,
116 the fragment handler will toss packets until ipfrag_low_thresh
117 is reached. This also serves as a maximum limit to namespaces
118 different from the initial one.
120 ipfrag_low_thresh - INTEGER
121 Maximum memory used to reassemble IP fragments before the kernel
122 begins to remove incomplete fragment queues to free up resources.
123 The kernel still accepts new fragments for defragmentation.
125 ipfrag_time - INTEGER
126 Time in seconds to keep an IP fragment in memory.
128 ipfrag_max_dist - INTEGER
129 ipfrag_max_dist is a non-negative integer value which defines the
130 maximum "disorder" which is allowed among fragments which share a
131 common IP source address. Note that reordering of packets is
132 not unusual, but if a large number of fragments arrive from a source
133 IP address while a particular fragment queue remains incomplete, it
134 probably indicates that one or more fragments belonging to that queue
135 have been lost. When ipfrag_max_dist is positive, an additional check
136 is done on fragments before they are added to a reassembly queue - if
137 ipfrag_max_dist (or more) fragments have arrived from a particular IP
138 address between additions to any IP fragment queue using that source
139 address, it's presumed that one or more fragments in the queue are
140 lost. The existing fragment queue will be dropped, and a new one
141 started. An ipfrag_max_dist value of zero disables this check.
143 Using a very small value, e.g. 1 or 2, for ipfrag_max_dist can
144 result in unnecessarily dropping fragment queues when normal
145 reordering of packets occurs, which could lead to poor application
146 performance. Using a very large value, e.g. 50000, increases the
147 likelihood of incorrectly reassembling IP fragments that originate
148 from different IP datagrams, which could result in data corruption.
153 inet_peer_threshold - INTEGER
154 The approximate size of the storage. Starting from this threshold
155 entries will be thrown aggressively. This threshold also determines
156 entries' time-to-live and time intervals between garbage collection
157 passes. More entries, less time-to-live, less GC interval.
159 inet_peer_minttl - INTEGER
160 Minimum time-to-live of entries. Should be enough to cover fragment
161 time-to-live on the reassembling side. This minimum time-to-live is
162 guaranteed if the pool size is less than inet_peer_threshold.
165 inet_peer_maxttl - INTEGER
166 Maximum time-to-live of entries. Unused entries will expire after
167 this period of time if there is no memory pressure on the pool (i.e.
168 when the number of entries in the pool is very small).
174 Limit of socket listen() backlog, known in userspace as SOMAXCONN.
175 Defaults to 128. See also tcp_max_syn_backlog for additional tuning
178 tcp_abort_on_overflow - BOOLEAN
179 If listening service is too slow to accept new connections,
180 reset them. Default state is FALSE. It means that if overflow
181 occurred due to a burst, connection will recover. Enable this
182 option _only_ if you are really sure that listening daemon
183 cannot be tuned to accept connections faster. Enabling this
184 option can harm clients of your server.
186 tcp_adv_win_scale - INTEGER
187 Count buffering overhead as bytes/2^tcp_adv_win_scale
188 (if tcp_adv_win_scale > 0) or bytes-bytes/2^(-tcp_adv_win_scale),
190 Possible values are [-31, 31], inclusive.
193 tcp_allowed_congestion_control - STRING
194 Show/set the congestion control choices available to non-privileged
195 processes. The list is a subset of those listed in
196 tcp_available_congestion_control.
197 Default is "reno" and the default setting (tcp_congestion_control).
199 tcp_app_win - INTEGER
200 Reserve max(window/2^tcp_app_win, mss) of window for application
201 buffer. Value 0 is special, it means that nothing is reserved.
204 tcp_autocorking - BOOLEAN
205 Enable TCP auto corking :
206 When applications do consecutive small write()/sendmsg() system calls,
207 we try to coalesce these small writes as much as possible, to lower
208 total amount of sent packets. This is done if at least one prior
209 packet for the flow is waiting in Qdisc queues or device transmit
210 queue. Applications can still use TCP_CORK for optimal behavior
211 when they know how/when to uncork their sockets.
214 tcp_available_congestion_control - STRING
215 Shows the available congestion control choices that are registered.
216 More congestion control algorithms may be available as modules,
219 tcp_base_mss - INTEGER
220 The initial value of search_low to be used by the packetization layer
221 Path MTU discovery (MTU probing). If MTU probing is enabled,
222 this is the initial MSS used by the connection.
224 tcp_congestion_control - STRING
225 Set the congestion control algorithm to be used for new
226 connections. The algorithm "reno" is always available, but
227 additional choices may be available based on kernel configuration.
228 Default is set as part of kernel configuration.
229 For passive connections, the listener congestion control choice
231 [see setsockopt(listenfd, SOL_TCP, TCP_CONGESTION, "name" ...) ]
234 Allows TCP to send "duplicate" SACKs.
236 tcp_early_retrans - INTEGER
237 Enable Early Retransmit (ER), per RFC 5827. ER lowers the threshold
238 for triggering fast retransmit when the amount of outstanding data is
239 small and when no previously unsent data can be transmitted (such
240 that limited transmit could be used). Also controls the use of
241 Tail loss probe (TLP) that converts RTOs occurring due to tail
242 losses into fast recovery (draft-dukkipati-tcpm-tcp-loss-probe-01).
246 2 enables ER but delays fast recovery and fast retransmit
247 by a fourth of RTT. This mitigates connection falsely
248 recovers when network has a small degree of reordering
249 (less than 3 packets).
250 3 enables delayed ER and TLP.
255 Control use of Explicit Congestion Notification (ECN) by TCP.
256 ECN is used only when both ends of the TCP connection indicate
257 support for it. This feature is useful in avoiding losses due
258 to congestion by allowing supporting routers to signal
259 congestion before having to drop packets.
261 0 Disable ECN. Neither initiate nor accept ECN.
262 1 Enable ECN when requested by incoming connections and
263 also request ECN on outgoing connection attempts.
264 2 Enable ECN when requested by incoming connections
265 but do not request ECN on outgoing connections.
269 Enable FACK congestion avoidance and fast retransmission.
270 The value is not used, if tcp_sack is not enabled.
272 tcp_fin_timeout - INTEGER
273 The length of time an orphaned (no longer referenced by any
274 application) connection will remain in the FIN_WAIT_2 state
275 before it is aborted at the local end. While a perfectly
276 valid "receive only" state for an un-orphaned connection, an
277 orphaned connection in FIN_WAIT_2 state could otherwise wait
278 forever for the remote to close its end of the connection.
283 Enables Forward RTO-Recovery (F-RTO) defined in RFC5682.
284 F-RTO is an enhanced recovery algorithm for TCP retransmission
285 timeouts. It is particularly beneficial in networks where the
286 RTT fluctuates (e.g., wireless). F-RTO is sender-side only
287 modification. It does not require any support from the peer.
289 By default it's enabled with a non-zero value. 0 disables F-RTO.
291 tcp_keepalive_time - INTEGER
292 How often TCP sends out keepalive messages when keepalive is enabled.
295 tcp_keepalive_probes - INTEGER
296 How many keepalive probes TCP sends out, until it decides that the
297 connection is broken. Default value: 9.
299 tcp_keepalive_intvl - INTEGER
300 How frequently the probes are send out. Multiplied by
301 tcp_keepalive_probes it is time to kill not responding connection,
302 after probes started. Default value: 75sec i.e. connection
303 will be aborted after ~11 minutes of retries.
305 tcp_low_latency - BOOLEAN
306 If set, the TCP stack makes decisions that prefer lower
307 latency as opposed to higher throughput. By default, this
308 option is not set meaning that higher throughput is preferred.
309 An example of an application where this default should be
310 changed would be a Beowulf compute cluster.
313 tcp_max_orphans - INTEGER
314 Maximal number of TCP sockets not attached to any user file handle,
315 held by system. If this number is exceeded orphaned connections are
316 reset immediately and warning is printed. This limit exists
317 only to prevent simple DoS attacks, you _must_ not rely on this
318 or lower the limit artificially, but rather increase it
319 (probably, after increasing installed memory),
320 if network conditions require more than default value,
321 and tune network services to linger and kill such states
322 more aggressively. Let me to remind again: each orphan eats
323 up to ~64K of unswappable memory.
325 tcp_max_syn_backlog - INTEGER
326 Maximal number of remembered connection requests, which have not
327 received an acknowledgment from connecting client.
328 The minimal value is 128 for low memory machines, and it will
329 increase in proportion to the memory of machine.
330 If server suffers from overload, try increasing this number.
332 tcp_max_tw_buckets - INTEGER
333 Maximal number of timewait sockets held by system simultaneously.
334 If this number is exceeded time-wait socket is immediately destroyed
335 and warning is printed. This limit exists only to prevent
336 simple DoS attacks, you _must_ not lower the limit artificially,
337 but rather increase it (probably, after increasing installed memory),
338 if network conditions require more than default value.
340 tcp_mem - vector of 3 INTEGERs: min, pressure, max
341 min: below this number of pages TCP is not bothered about its
344 pressure: when amount of memory allocated by TCP exceeds this number
345 of pages, TCP moderates its memory consumption and enters memory
346 pressure mode, which is exited when memory consumption falls
349 max: number of pages allowed for queueing by all TCP sockets.
351 Defaults are calculated at boot time from amount of available
354 tcp_moderate_rcvbuf - BOOLEAN
355 If set, TCP performs receive buffer auto-tuning, attempting to
356 automatically size the buffer (no greater than tcp_rmem[2]) to
357 match the size required by the path for full throughput. Enabled by
360 tcp_mtu_probing - INTEGER
361 Controls TCP Packetization-Layer Path MTU Discovery. Takes three
364 1 - Disabled by default, enabled when an ICMP black hole detected
365 2 - Always enabled, use initial MSS of tcp_base_mss.
367 tcp_no_metrics_save - BOOLEAN
368 By default, TCP saves various connection metrics in the route cache
369 when the connection closes, so that connections established in the
370 near future can use these to set initial conditions. Usually, this
371 increases overall performance, but may sometimes cause performance
372 degradation. If set, TCP will not cache metrics on closing
375 tcp_orphan_retries - INTEGER
376 This value influences the timeout of a locally closed TCP connection,
377 when RTO retransmissions remain unacknowledged.
378 See tcp_retries2 for more details.
380 The default value is 8.
381 If your machine is a loaded WEB server,
382 you should think about lowering this value, such sockets
383 may consume significant resources. Cf. tcp_max_orphans.
385 tcp_reordering - INTEGER
386 Maximal reordering of packets in a TCP stream.
389 tcp_retrans_collapse - BOOLEAN
390 Bug-to-bug compatibility with some broken printers.
391 On retransmit try to send bigger packets to work around bugs in
394 tcp_retries1 - INTEGER
395 This value influences the time, after which TCP decides, that
396 something is wrong due to unacknowledged RTO retransmissions,
397 and reports this suspicion to the network layer.
398 See tcp_retries2 for more details.
400 RFC 1122 recommends at least 3 retransmissions, which is the
403 tcp_retries2 - INTEGER
404 This value influences the timeout of an alive TCP connection,
405 when RTO retransmissions remain unacknowledged.
406 Given a value of N, a hypothetical TCP connection following
407 exponential backoff with an initial RTO of TCP_RTO_MIN would
408 retransmit N times before killing the connection at the (N+1)th RTO.
410 The default value of 15 yields a hypothetical timeout of 924.6
411 seconds and is a lower bound for the effective timeout.
412 TCP will effectively time out at the first RTO which exceeds the
413 hypothetical timeout.
415 RFC 1122 recommends at least 100 seconds for the timeout,
416 which corresponds to a value of at least 8.
418 tcp_rfc1337 - BOOLEAN
419 If set, the TCP stack behaves conforming to RFC1337. If unset,
420 we are not conforming to RFC, but prevent TCP TIME_WAIT
424 tcp_rmem - vector of 3 INTEGERs: min, default, max
425 min: Minimal size of receive buffer used by TCP sockets.
426 It is guaranteed to each TCP socket, even under moderate memory
430 default: initial size of receive buffer used by TCP sockets.
431 This value overrides net.core.rmem_default used by other protocols.
432 Default: 87380 bytes. This value results in window of 65535 with
433 default setting of tcp_adv_win_scale and tcp_app_win:0 and a bit
434 less for default tcp_app_win. See below about these variables.
436 max: maximal size of receive buffer allowed for automatically
437 selected receiver buffers for TCP socket. This value does not override
438 net.core.rmem_max. Calling setsockopt() with SO_RCVBUF disables
439 automatic tuning of that socket's receive buffer size, in which
440 case this value is ignored.
441 Default: between 87380B and 6MB, depending on RAM size.
444 Enable select acknowledgments (SACKS).
446 tcp_slow_start_after_idle - BOOLEAN
447 If set, provide RFC2861 behavior and time out the congestion
448 window after an idle period. An idle period is defined at
449 the current RTO. If unset, the congestion window will not
450 be timed out after an idle period.
454 Use the Host requirements interpretation of the TCP urgent pointer field.
455 Most hosts use the older BSD interpretation, so if you turn this on
456 Linux might not communicate correctly with them.
459 tcp_synack_retries - INTEGER
460 Number of times SYNACKs for a passive TCP connection attempt will
461 be retransmitted. Should not be higher than 255. Default value
462 is 5, which corresponds to 31seconds till the last retransmission
463 with the current initial RTO of 1second. With this the final timeout
464 for a passive TCP connection will happen after 63seconds.
466 tcp_syncookies - BOOLEAN
467 Only valid when the kernel was compiled with CONFIG_SYN_COOKIES
468 Send out syncookies when the syn backlog queue of a socket
469 overflows. This is to prevent against the common 'SYN flood attack'
472 Note, that syncookies is fallback facility.
473 It MUST NOT be used to help highly loaded servers to stand
474 against legal connection rate. If you see SYN flood warnings
475 in your logs, but investigation shows that they occur
476 because of overload with legal connections, you should tune
477 another parameters until this warning disappear.
478 See: tcp_max_syn_backlog, tcp_synack_retries, tcp_abort_on_overflow.
480 syncookies seriously violate TCP protocol, do not allow
481 to use TCP extensions, can result in serious degradation
482 of some services (f.e. SMTP relaying), visible not by you,
483 but your clients and relays, contacting you. While you see
484 SYN flood warnings in logs not being really flooded, your server
485 is seriously misconfigured.
487 If you want to test which effects syncookies have to your
488 network connections you can set this knob to 2 to enable
489 unconditionally generation of syncookies.
491 tcp_fastopen - INTEGER
492 Enable TCP Fast Open feature (draft-ietf-tcpm-fastopen) to send data
493 in the opening SYN packet. To use this feature, the client application
494 must use sendmsg() or sendto() with MSG_FASTOPEN flag rather than
495 connect() to perform a TCP handshake automatically.
497 The values (bitmap) are
498 1: Enables sending data in the opening SYN on the client w/ MSG_FASTOPEN.
499 2: Enables TCP Fast Open on the server side, i.e., allowing data in
500 a SYN packet to be accepted and passed to the application before
501 3-way hand shake finishes.
502 4: Send data in the opening SYN regardless of cookie availability and
503 without a cookie option.
504 0x100: Accept SYN data w/o validating the cookie.
505 0x200: Accept data-in-SYN w/o any cookie option present.
506 0x400/0x800: Enable Fast Open on all listeners regardless of the
507 TCP_FASTOPEN socket option. The two different flags designate two
508 different ways of setting max_qlen without the TCP_FASTOPEN socket
513 Note that the client & server side Fast Open flags (1 and 2
514 respectively) must be also enabled before the rest of flags can take
517 See include/net/tcp.h and the code for more details.
519 tcp_syn_retries - INTEGER
520 Number of times initial SYNs for an active TCP connection attempt
521 will be retransmitted. Should not be higher than 255. Default value
522 is 6, which corresponds to 63seconds till the last retransmission
523 with the current initial RTO of 1second. With this the final timeout
524 for an active TCP connection attempt will happen after 127seconds.
526 tcp_timestamps - BOOLEAN
527 Enable timestamps as defined in RFC1323.
529 tcp_min_tso_segs - INTEGER
530 Minimal number of segments per TSO frame.
531 Since linux-3.12, TCP does an automatic sizing of TSO frames,
532 depending on flow rate, instead of filling 64Kbytes packets.
533 For specific usages, it's possible to force TCP to build big
534 TSO frames. Note that TCP stack might split too big TSO packets
535 if available window is too small.
538 tcp_tso_win_divisor - INTEGER
539 This allows control over what percentage of the congestion window
540 can be consumed by a single TSO frame.
541 The setting of this parameter is a choice between burstiness and
542 building larger TSO frames.
545 tcp_tw_recycle - BOOLEAN
546 Enable fast recycling TIME-WAIT sockets. Default value is 0.
547 It should not be changed without advice/request of technical
550 tcp_tw_reuse - BOOLEAN
551 Allow to reuse TIME-WAIT sockets for new connections when it is
552 safe from protocol viewpoint. Default value is 0.
553 It should not be changed without advice/request of technical
556 tcp_window_scaling - BOOLEAN
557 Enable window scaling as defined in RFC1323.
559 tcp_wmem - vector of 3 INTEGERs: min, default, max
560 min: Amount of memory reserved for send buffers for TCP sockets.
561 Each TCP socket has rights to use it due to fact of its birth.
564 default: initial size of send buffer used by TCP sockets. This
565 value overrides net.core.wmem_default used by other protocols.
566 It is usually lower than net.core.wmem_default.
569 max: Maximal amount of memory allowed for automatically tuned
570 send buffers for TCP sockets. This value does not override
571 net.core.wmem_max. Calling setsockopt() with SO_SNDBUF disables
572 automatic tuning of that socket's send buffer size, in which case
573 this value is ignored.
574 Default: between 64K and 4MB, depending on RAM size.
576 tcp_notsent_lowat - UNSIGNED INTEGER
577 A TCP socket can control the amount of unsent bytes in its write queue,
578 thanks to TCP_NOTSENT_LOWAT socket option. poll()/select()/epoll()
579 reports POLLOUT events if the amount of unsent bytes is below a per
580 socket value, and if the write queue is not full. sendmsg() will
581 also not add new buffers if the limit is hit.
583 This global variable controls the amount of unsent data for
584 sockets not using TCP_NOTSENT_LOWAT. For these sockets, a change
585 to the global variable has immediate effect.
587 Default: UINT_MAX (0xFFFFFFFF)
589 tcp_workaround_signed_windows - BOOLEAN
590 If set, assume no receipt of a window scaling option means the
591 remote TCP is broken and treats the window as a signed quantity.
592 If unset, assume the remote TCP is not broken even if we do
593 not receive a window scaling option from them.
596 tcp_thin_linear_timeouts - BOOLEAN
597 Enable dynamic triggering of linear timeouts for thin streams.
598 If set, a check is performed upon retransmission by timeout to
599 determine if the stream is thin (less than 4 packets in flight).
600 As long as the stream is found to be thin, up to 6 linear
601 timeouts may be performed before exponential backoff mode is
602 initiated. This improves retransmission latency for
603 non-aggressive thin streams, often found to be time-dependent.
604 For more information on thin streams, see
605 Documentation/networking/tcp-thin.txt
608 tcp_thin_dupack - BOOLEAN
609 Enable dynamic triggering of retransmissions after one dupACK
610 for thin streams. If set, a check is performed upon reception
611 of a dupACK to determine if the stream is thin (less than 4
612 packets in flight). As long as the stream is found to be thin,
613 data is retransmitted on the first received dupACK. This
614 improves retransmission latency for non-aggressive thin
615 streams, often found to be time-dependent.
616 For more information on thin streams, see
617 Documentation/networking/tcp-thin.txt
620 tcp_limit_output_bytes - INTEGER
621 Controls TCP Small Queue limit per tcp socket.
622 TCP bulk sender tends to increase packets in flight until it
623 gets losses notifications. With SNDBUF autotuning, this can
624 result in a large amount of packets queued in qdisc/device
625 on the local machine, hurting latency of other flows, for
626 typical pfifo_fast qdiscs.
627 tcp_limit_output_bytes limits the number of bytes on qdisc
628 or device to reduce artificial RTT/cwnd and reduce bufferbloat.
631 tcp_challenge_ack_limit - INTEGER
632 Limits number of Challenge ACK sent per second, as recommended
633 in RFC 5961 (Improving TCP's Robustness to Blind In-Window Attacks)
638 udp_mem - vector of 3 INTEGERs: min, pressure, max
639 Number of pages allowed for queueing by all UDP sockets.
641 min: Below this number of pages UDP is not bothered about its
642 memory appetite. When amount of memory allocated by UDP exceeds
643 this number, UDP starts to moderate memory usage.
645 pressure: This value was introduced to follow format of tcp_mem.
647 max: Number of pages allowed for queueing by all UDP sockets.
649 Default is calculated at boot time from amount of available memory.
651 udp_rmem_min - INTEGER
652 Minimal size of receive buffer used by UDP sockets in moderation.
653 Each UDP socket is able to use the size for receiving data, even if
654 total pages of UDP sockets exceed udp_mem pressure. The unit is byte.
657 udp_wmem_min - INTEGER
658 Minimal size of send buffer used by UDP sockets in moderation.
659 Each UDP socket is able to use the size for sending data, even if
660 total pages of UDP sockets exceed udp_mem pressure. The unit is byte.
665 cipso_cache_enable - BOOLEAN
666 If set, enable additions to and lookups from the CIPSO label mapping
667 cache. If unset, additions are ignored and lookups always result in a
668 miss. However, regardless of the setting the cache is still
669 invalidated when required when means you can safely toggle this on and
670 off and the cache will always be "safe".
673 cipso_cache_bucket_size - INTEGER
674 The CIPSO label cache consists of a fixed size hash table with each
675 hash bucket containing a number of cache entries. This variable limits
676 the number of entries in each hash bucket; the larger the value the
677 more CIPSO label mappings that can be cached. When the number of
678 entries in a given hash bucket reaches this limit adding new entries
679 causes the oldest entry in the bucket to be removed to make room.
682 cipso_rbm_optfmt - BOOLEAN
683 Enable the "Optimized Tag 1 Format" as defined in section 3.4.2.6 of
684 the CIPSO draft specification (see Documentation/netlabel for details).
685 This means that when set the CIPSO tag will be padded with empty
686 categories in order to make the packet data 32-bit aligned.
689 cipso_rbm_structvalid - BOOLEAN
690 If set, do a very strict check of the CIPSO option when
691 ip_options_compile() is called. If unset, relax the checks done during
692 ip_options_compile(). Either way is "safe" as errors are caught else
693 where in the CIPSO processing code but setting this to 0 (False) should
694 result in less work (i.e. it should be faster) but could cause problems
695 with other implementations that require strict checking.
700 ip_local_port_range - 2 INTEGERS
701 Defines the local port range that is used by TCP and UDP to
702 choose the local port. The first number is the first, the
703 second the last local port number. The default values are
704 32768 and 61000 respectively.
706 ip_local_reserved_ports - list of comma separated ranges
707 Specify the ports which are reserved for known third-party
708 applications. These ports will not be used by automatic port
709 assignments (e.g. when calling connect() or bind() with port
710 number 0). Explicit port allocation behavior is unchanged.
712 The format used for both input and output is a comma separated
713 list of ranges (e.g. "1,2-4,10-10" for ports 1, 2, 3, 4 and
714 10). Writing to the file will clear all previously reserved
715 ports and update the current list with the one given in the
718 Note that ip_local_port_range and ip_local_reserved_ports
719 settings are independent and both are considered by the kernel
720 when determining which ports are available for automatic port
723 You can reserve ports which are not in the current
724 ip_local_port_range, e.g.:
726 $ cat /proc/sys/net/ipv4/ip_local_port_range
728 $ cat /proc/sys/net/ipv4/ip_local_reserved_ports
731 although this is redundant. However such a setting is useful
732 if later the port range is changed to a value that will
733 include the reserved ports.
737 ip_nonlocal_bind - BOOLEAN
738 If set, allows processes to bind() to non-local IP addresses,
739 which can be quite useful - but may break some applications.
743 If set non-zero, enables support for dynamic addresses.
744 If set to a non-zero value larger than 1, a kernel log
745 message will be printed when dynamic address rewriting
749 ip_early_demux - BOOLEAN
750 Optimize input packet processing down to one demux for
751 certain kinds of local sockets. Currently we only do this
752 for established TCP sockets.
754 It may add an additional cost for pure routing workloads that
755 reduces overall throughput, in such case you should disable it.
758 icmp_echo_ignore_all - BOOLEAN
759 If set non-zero, then the kernel will ignore all ICMP ECHO
763 icmp_echo_ignore_broadcasts - BOOLEAN
764 If set non-zero, then the kernel will ignore all ICMP ECHO and
765 TIMESTAMP requests sent to it via broadcast/multicast.
768 icmp_ratelimit - INTEGER
769 Limit the maximal rates for sending ICMP packets whose type matches
770 icmp_ratemask (see below) to specific targets.
771 0 to disable any limiting,
772 otherwise the minimal space between responses in milliseconds.
773 Note that another sysctl, icmp_msgs_per_sec limits the number
774 of ICMP packets sent on all targets.
777 icmp_msgs_per_sec - INTEGER
778 Limit maximal number of ICMP packets sent per second from this host.
779 Only messages whose type matches icmp_ratemask (see below) are
780 controlled by this limit.
783 icmp_msgs_burst - INTEGER
784 icmp_msgs_per_sec controls number of ICMP packets sent per second,
785 while icmp_msgs_burst controls the burst size of these packets.
788 icmp_ratemask - INTEGER
789 Mask made of ICMP types for which rates are being limited.
790 Significant bits: IHGFEDCBA9876543210
791 Default mask: 0000001100000011000 (6168)
793 Bit definitions (see include/linux/icmp.h):
795 3 Destination Unreachable *
800 C Parameter Problem *
805 H Address Mask Request
808 * These are rate limited by default (see default mask above)
810 icmp_ignore_bogus_error_responses - BOOLEAN
811 Some routers violate RFC1122 by sending bogus responses to broadcast
812 frames. Such violations are normally logged via a kernel warning.
813 If this is set to TRUE, the kernel will not give such warnings, which
814 will avoid log file clutter.
817 icmp_errors_use_inbound_ifaddr - BOOLEAN
819 If zero, icmp error messages are sent with the primary address of
820 the exiting interface.
822 If non-zero, the message will be sent with the primary address of
823 the interface that received the packet that caused the icmp error.
824 This is the behaviour network many administrators will expect from
825 a router. And it can make debugging complicated network layouts
828 Note that if no primary address exists for the interface selected,
829 then the primary address of the first non-loopback interface that
830 has one will be used regardless of this setting.
834 igmp_max_memberships - INTEGER
835 Change the maximum number of multicast groups we can subscribe to.
838 Theoretical maximum value is bounded by having to send a membership
839 report in a single datagram (i.e. the report can't span multiple
840 datagrams, or risk confusing the switch and leaving groups you don't
843 The number of supported groups 'M' is bounded by the number of group
844 report entries you can fit into a single datagram of 65535 bytes.
846 M = 65536-sizeof (ip header)/(sizeof(Group record))
848 Group records are variable length, with a minimum of 12 bytes.
849 So net.ipv4.igmp_max_memberships should not be set higher than:
851 (65536-24) / 12 = 5459
853 The value 5459 assumes no IP header options, so in practice
854 this number may be lower.
856 conf/interface/* changes special settings per interface (where
857 "interface" is the name of your network interface)
859 conf/all/* is special, changes the settings for all interfaces
862 Controls the IGMP query robustness variable (see RFC2236 8.1).
863 Default: 2 (as specified by RFC2236 8.1)
864 Minimum: 1 (as specified by RFC6636 4.5)
866 log_martians - BOOLEAN
867 Log packets with impossible addresses to kernel log.
868 log_martians for the interface will be enabled if at least one of
869 conf/{all,interface}/log_martians is set to TRUE,
870 it will be disabled otherwise
872 accept_redirects - BOOLEAN
873 Accept ICMP redirect messages.
874 accept_redirects for the interface will be enabled if:
875 - both conf/{all,interface}/accept_redirects are TRUE in the case
876 forwarding for the interface is enabled
878 - at least one of conf/{all,interface}/accept_redirects is TRUE in the
879 case forwarding for the interface is disabled
880 accept_redirects for the interface will be disabled otherwise
885 Enable IP forwarding on this interface.
887 mc_forwarding - BOOLEAN
888 Do multicast routing. The kernel needs to be compiled with CONFIG_MROUTE
889 and a multicast routing daemon is required.
890 conf/all/mc_forwarding must also be set to TRUE to enable multicast
891 routing for the interface
894 Integer value used to differentiate the devices by the medium they
895 are attached to. Two devices can have different id values when
896 the broadcast packets are received only on one of them.
897 The default value 0 means that the device is the only interface
898 to its medium, value of -1 means that medium is not known.
900 Currently, it is used to change the proxy_arp behavior:
901 the proxy_arp feature is enabled for packets forwarded between
902 two devices attached to different media.
906 proxy_arp for the interface will be enabled if at least one of
907 conf/{all,interface}/proxy_arp is set to TRUE,
908 it will be disabled otherwise
910 proxy_arp_pvlan - BOOLEAN
911 Private VLAN proxy arp.
912 Basically allow proxy arp replies back to the same interface
913 (from which the ARP request/solicitation was received).
915 This is done to support (ethernet) switch features, like RFC
916 3069, where the individual ports are NOT allowed to
917 communicate with each other, but they are allowed to talk to
918 the upstream router. As described in RFC 3069, it is possible
919 to allow these hosts to communicate through the upstream
920 router by proxy_arp'ing. Don't need to be used together with
923 This technology is known by different names:
924 In RFC 3069 it is called VLAN Aggregation.
925 Cisco and Allied Telesyn call it Private VLAN.
926 Hewlett-Packard call it Source-Port filtering or port-isolation.
927 Ericsson call it MAC-Forced Forwarding (RFC Draft).
929 shared_media - BOOLEAN
930 Send(router) or accept(host) RFC1620 shared media redirects.
931 Overrides ip_secure_redirects.
932 shared_media for the interface will be enabled if at least one of
933 conf/{all,interface}/shared_media is set to TRUE,
934 it will be disabled otherwise
937 secure_redirects - BOOLEAN
938 Accept ICMP redirect messages only for gateways,
939 listed in default gateway list.
940 secure_redirects for the interface will be enabled if at least one of
941 conf/{all,interface}/secure_redirects is set to TRUE,
942 it will be disabled otherwise
945 send_redirects - BOOLEAN
946 Send redirects, if router.
947 send_redirects for the interface will be enabled if at least one of
948 conf/{all,interface}/send_redirects is set to TRUE,
949 it will be disabled otherwise
952 bootp_relay - BOOLEAN
953 Accept packets with source address 0.b.c.d destined
954 not to this host as local ones. It is supposed, that
955 BOOTP relay daemon will catch and forward such packets.
956 conf/all/bootp_relay must also be set to TRUE to enable BOOTP relay
961 accept_source_route - BOOLEAN
962 Accept packets with SRR option.
963 conf/all/accept_source_route must also be set to TRUE to accept packets
964 with SRR option on the interface
965 default TRUE (router)
968 accept_local - BOOLEAN
969 Accept packets with local source addresses. In combination with
970 suitable routing, this can be used to direct packets between two
971 local interfaces over the wire and have them accepted properly.
974 route_localnet - BOOLEAN
975 Do not consider loopback addresses as martian source or destination
976 while routing. This enables the use of 127/8 for local routing purposes.
980 0 - No source validation.
981 1 - Strict mode as defined in RFC3704 Strict Reverse Path
982 Each incoming packet is tested against the FIB and if the interface
983 is not the best reverse path the packet check will fail.
984 By default failed packets are discarded.
985 2 - Loose mode as defined in RFC3704 Loose Reverse Path
986 Each incoming packet's source address is also tested against the FIB
987 and if the source address is not reachable via any interface
988 the packet check will fail.
990 Current recommended practice in RFC3704 is to enable strict mode
991 to prevent IP spoofing from DDos attacks. If using asymmetric routing
992 or other complicated routing, then loose mode is recommended.
994 The max value from conf/{all,interface}/rp_filter is used
995 when doing source validation on the {interface}.
997 Default value is 0. Note that some distributions enable it
1000 arp_filter - BOOLEAN
1001 1 - Allows you to have multiple network interfaces on the same
1002 subnet, and have the ARPs for each interface be answered
1003 based on whether or not the kernel would route a packet from
1004 the ARP'd IP out that interface (therefore you must use source
1005 based routing for this to work). In other words it allows control
1006 of which cards (usually 1) will respond to an arp request.
1008 0 - (default) The kernel can respond to arp requests with addresses
1009 from other interfaces. This may seem wrong but it usually makes
1010 sense, because it increases the chance of successful communication.
1011 IP addresses are owned by the complete host on Linux, not by
1012 particular interfaces. Only for more complex setups like load-
1013 balancing, does this behaviour cause problems.
1015 arp_filter for the interface will be enabled if at least one of
1016 conf/{all,interface}/arp_filter is set to TRUE,
1017 it will be disabled otherwise
1019 arp_announce - INTEGER
1020 Define different restriction levels for announcing the local
1021 source IP address from IP packets in ARP requests sent on
1023 0 - (default) Use any local address, configured on any interface
1024 1 - Try to avoid local addresses that are not in the target's
1025 subnet for this interface. This mode is useful when target
1026 hosts reachable via this interface require the source IP
1027 address in ARP requests to be part of their logical network
1028 configured on the receiving interface. When we generate the
1029 request we will check all our subnets that include the
1030 target IP and will preserve the source address if it is from
1031 such subnet. If there is no such subnet we select source
1032 address according to the rules for level 2.
1033 2 - Always use the best local address for this target.
1034 In this mode we ignore the source address in the IP packet
1035 and try to select local address that we prefer for talks with
1036 the target host. Such local address is selected by looking
1037 for primary IP addresses on all our subnets on the outgoing
1038 interface that include the target IP address. If no suitable
1039 local address is found we select the first local address
1040 we have on the outgoing interface or on all other interfaces,
1041 with the hope we will receive reply for our request and
1042 even sometimes no matter the source IP address we announce.
1044 The max value from conf/{all,interface}/arp_announce is used.
1046 Increasing the restriction level gives more chance for
1047 receiving answer from the resolved target while decreasing
1048 the level announces more valid sender's information.
1050 arp_ignore - INTEGER
1051 Define different modes for sending replies in response to
1052 received ARP requests that resolve local target IP addresses:
1053 0 - (default): reply for any local target IP address, configured
1055 1 - reply only if the target IP address is local address
1056 configured on the incoming interface
1057 2 - reply only if the target IP address is local address
1058 configured on the incoming interface and both with the
1059 sender's IP address are part from same subnet on this interface
1060 3 - do not reply for local addresses configured with scope host,
1061 only resolutions for global and link addresses are replied
1063 8 - do not reply for all local addresses
1065 The max value from conf/{all,interface}/arp_ignore is used
1066 when ARP request is received on the {interface}
1068 arp_notify - BOOLEAN
1069 Define mode for notification of address and device changes.
1070 0 - (default): do nothing
1071 1 - Generate gratuitous arp requests when device is brought up
1072 or hardware address changes.
1074 arp_accept - BOOLEAN
1075 Define behavior for gratuitous ARP frames who's IP is not
1076 already present in the ARP table:
1077 0 - don't create new entries in the ARP table
1078 1 - create new entries in the ARP table
1080 Both replies and requests type gratuitous arp will trigger the
1081 ARP table to be updated, if this setting is on.
1083 If the ARP table already contains the IP address of the
1084 gratuitous arp frame, the arp table will be updated regardless
1085 if this setting is on or off.
1088 app_solicit - INTEGER
1089 The maximum number of probes to send to the user space ARP daemon
1090 via netlink before dropping back to multicast probes (see
1091 mcast_solicit). Defaults to 0.
1093 disable_policy - BOOLEAN
1094 Disable IPSEC policy (SPD) for this interface
1096 disable_xfrm - BOOLEAN
1097 Disable IPSEC encryption on this interface, whatever the policy
1099 igmpv2_unsolicited_report_interval - INTEGER
1100 The interval in milliseconds in which the next unsolicited
1101 IGMPv1 or IGMPv2 report retransmit will take place.
1102 Default: 10000 (10 seconds)
1104 igmpv3_unsolicited_report_interval - INTEGER
1105 The interval in milliseconds in which the next unsolicited
1106 IGMPv3 report retransmit will take place.
1107 Default: 1000 (1 seconds)
1109 promote_secondaries - BOOLEAN
1110 When a primary IP address is removed from this interface
1111 promote a corresponding secondary IP address instead of
1112 removing all the corresponding secondary IP addresses.
1116 Allows you to write a number, which can be used as required.
1120 kuznet@ms2.inr.ac.ru
1126 delon.nicolas@wanadoo.fr
1131 /proc/sys/net/ipv6/* Variables:
1133 IPv6 has no global variables such as tcp_*. tcp_* settings under ipv4/ also
1134 apply to IPv6 [XXX?].
1136 bindv6only - BOOLEAN
1137 Default value for IPV6_V6ONLY socket option,
1138 which restricts use of the IPv6 socket to IPv6 communication
1140 TRUE: disable IPv4-mapped address feature
1141 FALSE: enable IPv4-mapped address feature
1143 Default: FALSE (as specified in RFC3493)
1145 flowlabel_consistency - BOOLEAN
1146 Protect the consistency (and unicity) of flow label.
1147 You have to disable it to use IPV6_FL_F_REFLECT flag on the
1153 auto_flowlabels - BOOLEAN
1154 Automatically generate flow labels based based on a flow hash
1155 of the packet. This allows intermediate devices, such as routers,
1156 to idenfify packet flows for mechanisms like Equal Cost Multipath
1157 Routing (see RFC 6438).
1162 anycast_src_echo_reply - BOOLEAN
1163 Controls the use of anycast addresses as source addresses for ICMPv6
1170 Controls the MLD query robustness variable (see RFC3810 9.1).
1171 Default: 2 (as specified by RFC3810 9.1)
1172 Minimum: 1 (as specified by RFC6636 4.5)
1176 ip6frag_high_thresh - INTEGER
1177 Maximum memory used to reassemble IPv6 fragments. When
1178 ip6frag_high_thresh bytes of memory is allocated for this purpose,
1179 the fragment handler will toss packets until ip6frag_low_thresh
1182 ip6frag_low_thresh - INTEGER
1183 See ip6frag_high_thresh
1185 ip6frag_time - INTEGER
1186 Time in seconds to keep an IPv6 fragment in memory.
1189 Change the interface-specific default settings.
1193 Change all the interface-specific settings.
1195 [XXX: Other special features than forwarding?]
1197 conf/all/forwarding - BOOLEAN
1198 Enable global IPv6 forwarding between all interfaces.
1200 IPv4 and IPv6 work differently here; e.g. netfilter must be used
1201 to control which interfaces may forward packets and which not.
1203 This also sets all interfaces' Host/Router setting
1204 'forwarding' to the specified value. See below for details.
1206 This referred to as global forwarding.
1211 fwmark_reflect - BOOLEAN
1212 Controls the fwmark of kernel-generated IPv6 reply packets that are not
1213 associated with a socket for example, TCP RSTs or ICMPv6 echo replies).
1214 If unset, these packets have a fwmark of zero. If set, they have the
1215 fwmark of the packet they are replying to.
1219 Change special settings per interface.
1221 The functional behaviour for certain settings is different
1222 depending on whether local forwarding is enabled or not.
1225 Accept Router Advertisements; autoconfigure using them.
1227 It also determines whether or not to transmit Router
1228 Solicitations. If and only if the functional setting is to
1229 accept Router Advertisements, Router Solicitations will be
1232 Possible values are:
1233 0 Do not accept Router Advertisements.
1234 1 Accept Router Advertisements if forwarding is disabled.
1235 2 Overrule forwarding behaviour. Accept Router Advertisements
1236 even if forwarding is enabled.
1238 Functional default: enabled if local forwarding is disabled.
1239 disabled if local forwarding is enabled.
1241 accept_ra_defrtr - BOOLEAN
1242 Learn default router in Router Advertisement.
1244 Functional default: enabled if accept_ra is enabled.
1245 disabled if accept_ra is disabled.
1247 accept_ra_from_local - BOOLEAN
1248 Accept RA with source-address that is found on local machine
1249 if the RA is otherwise proper and able to be accepted.
1250 Default is to NOT accept these as it may be an un-intended
1254 enabled if accept_ra_from_local is enabled
1255 on a specific interface.
1256 disabled if accept_ra_from_local is disabled
1257 on a specific interface.
1259 accept_ra_pinfo - BOOLEAN
1260 Learn Prefix Information in Router Advertisement.
1262 Functional default: enabled if accept_ra is enabled.
1263 disabled if accept_ra is disabled.
1265 accept_ra_rt_info_max_plen - INTEGER
1266 Maximum prefix length of Route Information in RA.
1268 Route Information w/ prefix larger than or equal to this
1269 variable shall be ignored.
1271 Functional default: 0 if accept_ra_rtr_pref is enabled.
1272 -1 if accept_ra_rtr_pref is disabled.
1274 accept_ra_rtr_pref - BOOLEAN
1275 Accept Router Preference in RA.
1277 Functional default: enabled if accept_ra is enabled.
1278 disabled if accept_ra is disabled.
1280 accept_redirects - BOOLEAN
1283 Functional default: enabled if local forwarding is disabled.
1284 disabled if local forwarding is enabled.
1286 accept_source_route - INTEGER
1287 Accept source routing (routing extension header).
1289 >= 0: Accept only routing header type 2.
1290 < 0: Do not accept routing header.
1295 Autoconfigure addresses using Prefix Information in Router
1298 Functional default: enabled if accept_ra_pinfo is enabled.
1299 disabled if accept_ra_pinfo is disabled.
1301 dad_transmits - INTEGER
1302 The amount of Duplicate Address Detection probes to send.
1305 forwarding - INTEGER
1306 Configure interface-specific Host/Router behaviour.
1308 Note: It is recommended to have the same setting on all
1309 interfaces; mixed router/host scenarios are rather uncommon.
1311 Possible values are:
1312 0 Forwarding disabled
1313 1 Forwarding enabled
1317 By default, Host behaviour is assumed. This means:
1319 1. IsRouter flag is not set in Neighbour Advertisements.
1320 2. If accept_ra is TRUE (default), transmit Router
1322 3. If accept_ra is TRUE (default), accept Router
1323 Advertisements (and do autoconfiguration).
1324 4. If accept_redirects is TRUE (default), accept Redirects.
1328 If local forwarding is enabled, Router behaviour is assumed.
1329 This means exactly the reverse from the above:
1331 1. IsRouter flag is set in Neighbour Advertisements.
1332 2. Router Solicitations are not sent unless accept_ra is 2.
1333 3. Router Advertisements are ignored unless accept_ra is 2.
1334 4. Redirects are ignored.
1336 Default: 0 (disabled) if global forwarding is disabled (default),
1337 otherwise 1 (enabled).
1340 Default Hop Limit to set.
1344 Default Maximum Transfer Unit
1345 Default: 1280 (IPv6 required minimum)
1347 router_probe_interval - INTEGER
1348 Minimum interval (in seconds) between Router Probing described
1353 router_solicitation_delay - INTEGER
1354 Number of seconds to wait after interface is brought up
1355 before sending Router Solicitations.
1358 router_solicitation_interval - INTEGER
1359 Number of seconds to wait between Router Solicitations.
1362 router_solicitations - INTEGER
1363 Number of Router Solicitations to send until assuming no
1364 routers are present.
1367 use_tempaddr - INTEGER
1368 Preference for Privacy Extensions (RFC3041).
1369 <= 0 : disable Privacy Extensions
1370 == 1 : enable Privacy Extensions, but prefer public
1371 addresses over temporary addresses.
1372 > 1 : enable Privacy Extensions and prefer temporary
1373 addresses over public addresses.
1374 Default: 0 (for most devices)
1375 -1 (for point-to-point devices and loopback devices)
1377 temp_valid_lft - INTEGER
1378 valid lifetime (in seconds) for temporary addresses.
1379 Default: 604800 (7 days)
1381 temp_prefered_lft - INTEGER
1382 Preferred lifetime (in seconds) for temporary addresses.
1383 Default: 86400 (1 day)
1385 max_desync_factor - INTEGER
1386 Maximum value for DESYNC_FACTOR, which is a random value
1387 that ensures that clients don't synchronize with each
1388 other and generate new addresses at exactly the same time.
1389 value is in seconds.
1392 regen_max_retry - INTEGER
1393 Number of attempts before give up attempting to generate
1394 valid temporary addresses.
1397 max_addresses - INTEGER
1398 Maximum number of autoconfigured addresses per interface. Setting
1399 to zero disables the limitation. It is not recommended to set this
1400 value too large (or to zero) because it would be an easy way to
1401 crash the kernel by allowing too many addresses to be created.
1404 disable_ipv6 - BOOLEAN
1405 Disable IPv6 operation. If accept_dad is set to 2, this value
1406 will be dynamically set to TRUE if DAD fails for the link-local
1408 Default: FALSE (enable IPv6 operation)
1410 When this value is changed from 1 to 0 (IPv6 is being enabled),
1411 it will dynamically create a link-local address on the given
1412 interface and start Duplicate Address Detection, if necessary.
1414 When this value is changed from 0 to 1 (IPv6 is being disabled),
1415 it will dynamically delete all address on the given interface.
1417 accept_dad - INTEGER
1418 Whether to accept DAD (Duplicate Address Detection).
1420 1: Enable DAD (default)
1421 2: Enable DAD, and disable IPv6 operation if MAC-based duplicate
1422 link-local address has been found.
1424 force_tllao - BOOLEAN
1425 Enable sending the target link-layer address option even when
1426 responding to a unicast neighbor solicitation.
1429 Quoting from RFC 2461, section 4.4, Target link-layer address:
1431 "The option MUST be included for multicast solicitations in order to
1432 avoid infinite Neighbor Solicitation "recursion" when the peer node
1433 does not have a cache entry to return a Neighbor Advertisements
1434 message. When responding to unicast solicitations, the option can be
1435 omitted since the sender of the solicitation has the correct link-
1436 layer address; otherwise it would not have be able to send the unicast
1437 solicitation in the first place. However, including the link-layer
1438 address in this case adds little overhead and eliminates a potential
1439 race condition where the sender deletes the cached link-layer address
1440 prior to receiving a response to a previous solicitation."
1442 ndisc_notify - BOOLEAN
1443 Define mode for notification of address and device changes.
1444 0 - (default): do nothing
1445 1 - Generate unsolicited neighbour advertisements when device is brought
1446 up or hardware address changes.
1448 mldv1_unsolicited_report_interval - INTEGER
1449 The interval in milliseconds in which the next unsolicited
1450 MLDv1 report retransmit will take place.
1451 Default: 10000 (10 seconds)
1453 mldv2_unsolicited_report_interval - INTEGER
1454 The interval in milliseconds in which the next unsolicited
1455 MLDv2 report retransmit will take place.
1456 Default: 1000 (1 second)
1458 force_mld_version - INTEGER
1459 0 - (default) No enforcement of a MLD version, MLDv1 fallback allowed
1460 1 - Enforce to use MLD version 1
1461 2 - Enforce to use MLD version 2
1463 suppress_frag_ndisc - INTEGER
1464 Control RFC 6980 (Security Implications of IPv6 Fragmentation
1465 with IPv6 Neighbor Discovery) behavior:
1466 1 - (default) discard fragmented neighbor discovery packets
1467 0 - allow fragmented neighbor discovery packets
1471 Limit the maximal rates for sending ICMPv6 packets.
1472 0 to disable any limiting,
1473 otherwise the minimal space between responses in milliseconds.
1478 Pekka Savola <pekkas@netcore.fi>
1479 YOSHIFUJI Hideaki / USAGI Project <yoshfuji@linux-ipv6.org>
1482 /proc/sys/net/bridge/* Variables:
1484 bridge-nf-call-arptables - BOOLEAN
1485 1 : pass bridged ARP traffic to arptables' FORWARD chain.
1489 bridge-nf-call-iptables - BOOLEAN
1490 1 : pass bridged IPv4 traffic to iptables' chains.
1494 bridge-nf-call-ip6tables - BOOLEAN
1495 1 : pass bridged IPv6 traffic to ip6tables' chains.
1499 bridge-nf-filter-vlan-tagged - BOOLEAN
1500 1 : pass bridged vlan-tagged ARP/IP/IPv6 traffic to {arp,ip,ip6}tables.
1504 bridge-nf-filter-pppoe-tagged - BOOLEAN
1505 1 : pass bridged pppoe-tagged IP/IPv6 traffic to {ip,ip6}tables.
1509 bridge-nf-pass-vlan-input-dev - BOOLEAN
1510 1: if bridge-nf-filter-vlan-tagged is enabled, try to find a vlan
1511 interface on the bridge and set the netfilter input device to the vlan.
1512 This allows use of e.g. "iptables -i br0.1" and makes the REDIRECT
1513 target work with vlan-on-top-of-bridge interfaces. When no matching
1514 vlan interface is found, or this switch is off, the input device is
1515 set to the bridge interface.
1516 0: disable bridge netfilter vlan interface lookup.
1519 proc/sys/net/sctp/* Variables:
1521 addip_enable - BOOLEAN
1522 Enable or disable extension of Dynamic Address Reconfiguration
1523 (ADD-IP) functionality specified in RFC5061. This extension provides
1524 the ability to dynamically add and remove new addresses for the SCTP
1527 1: Enable extension.
1529 0: Disable extension.
1533 addip_noauth_enable - BOOLEAN
1534 Dynamic Address Reconfiguration (ADD-IP) requires the use of
1535 authentication to protect the operations of adding or removing new
1536 addresses. This requirement is mandated so that unauthorized hosts
1537 would not be able to hijack associations. However, older
1538 implementations may not have implemented this requirement while
1539 allowing the ADD-IP extension. For reasons of interoperability,
1540 we provide this variable to control the enforcement of the
1541 authentication requirement.
1543 1: Allow ADD-IP extension to be used without authentication. This
1544 should only be set in a closed environment for interoperability
1545 with older implementations.
1547 0: Enforce the authentication requirement
1551 auth_enable - BOOLEAN
1552 Enable or disable Authenticated Chunks extension. This extension
1553 provides the ability to send and receive authenticated chunks and is
1554 required for secure operation of Dynamic Address Reconfiguration
1557 1: Enable this extension.
1558 0: Disable this extension.
1562 prsctp_enable - BOOLEAN
1563 Enable or disable the Partial Reliability extension (RFC3758) which
1564 is used to notify peers that a given DATA should no longer be expected.
1572 The limit of the number of new packets that can be initially sent. It
1573 controls how bursty the generated traffic can be.
1577 association_max_retrans - INTEGER
1578 Set the maximum number for retransmissions that an association can
1579 attempt deciding that the remote end is unreachable. If this value
1580 is exceeded, the association is terminated.
1584 max_init_retransmits - INTEGER
1585 The maximum number of retransmissions of INIT and COOKIE-ECHO chunks
1586 that an association will attempt before declaring the destination
1587 unreachable and terminating.
1591 path_max_retrans - INTEGER
1592 The maximum number of retransmissions that will be attempted on a given
1593 path. Once this threshold is exceeded, the path is considered
1594 unreachable, and new traffic will use a different path when the
1595 association is multihomed.
1599 pf_retrans - INTEGER
1600 The number of retransmissions that will be attempted on a given path
1601 before traffic is redirected to an alternate transport (should one
1602 exist). Note this is distinct from path_max_retrans, as a path that
1603 passes the pf_retrans threshold can still be used. Its only
1604 deprioritized when a transmission path is selected by the stack. This
1605 setting is primarily used to enable fast failover mechanisms without
1606 having to reduce path_max_retrans to a very low value. See:
1607 http://www.ietf.org/id/draft-nishida-tsvwg-sctp-failover-05.txt
1608 for details. Note also that a value of pf_retrans > path_max_retrans
1609 disables this feature
1613 rto_initial - INTEGER
1614 The initial round trip timeout value in milliseconds that will be used
1615 in calculating round trip times. This is the initial time interval
1616 for retransmissions.
1621 The maximum value (in milliseconds) of the round trip timeout. This
1622 is the largest time interval that can elapse between retransmissions.
1627 The minimum value (in milliseconds) of the round trip timeout. This
1628 is the smallest time interval the can elapse between retransmissions.
1632 hb_interval - INTEGER
1633 The interval (in milliseconds) between HEARTBEAT chunks. These chunks
1634 are sent at the specified interval on idle paths to probe the state of
1635 a given path between 2 associations.
1639 sack_timeout - INTEGER
1640 The amount of time (in milliseconds) that the implementation will wait
1645 valid_cookie_life - INTEGER
1646 The default lifetime of the SCTP cookie (in milliseconds). The cookie
1647 is used during association establishment.
1651 cookie_preserve_enable - BOOLEAN
1652 Enable or disable the ability to extend the lifetime of the SCTP cookie
1653 that is used during the establishment phase of SCTP association
1655 1: Enable cookie lifetime extension.
1660 cookie_hmac_alg - STRING
1661 Select the hmac algorithm used when generating the cookie value sent by
1662 a listening sctp socket to a connecting client in the INIT-ACK chunk.
1667 Ability to assign md5 or sha1 as the selected alg is predicated on the
1668 configuration of those algorithms at build time (CONFIG_CRYPTO_MD5 and
1669 CONFIG_CRYPTO_SHA1).
1671 Default: Dependent on configuration. MD5 if available, else SHA1 if
1672 available, else none.
1674 rcvbuf_policy - INTEGER
1675 Determines if the receive buffer is attributed to the socket or to
1676 association. SCTP supports the capability to create multiple
1677 associations on a single socket. When using this capability, it is
1678 possible that a single stalled association that's buffering a lot
1679 of data may block other associations from delivering their data by
1680 consuming all of the receive buffer space. To work around this,
1681 the rcvbuf_policy could be set to attribute the receiver buffer space
1682 to each association instead of the socket. This prevents the described
1685 1: rcvbuf space is per association
1686 0: rcvbuf space is per socket
1690 sndbuf_policy - INTEGER
1691 Similar to rcvbuf_policy above, this applies to send buffer space.
1693 1: Send buffer is tracked per association
1694 0: Send buffer is tracked per socket.
1698 sctp_mem - vector of 3 INTEGERs: min, pressure, max
1699 Number of pages allowed for queueing by all SCTP sockets.
1701 min: Below this number of pages SCTP is not bothered about its
1702 memory appetite. When amount of memory allocated by SCTP exceeds
1703 this number, SCTP starts to moderate memory usage.
1705 pressure: This value was introduced to follow format of tcp_mem.
1707 max: Number of pages allowed for queueing by all SCTP sockets.
1709 Default is calculated at boot time from amount of available memory.
1711 sctp_rmem - vector of 3 INTEGERs: min, default, max
1712 Only the first value ("min") is used, "default" and "max" are
1715 min: Minimal size of receive buffer used by SCTP socket.
1716 It is guaranteed to each SCTP socket (but not association) even
1717 under moderate memory pressure.
1721 sctp_wmem - vector of 3 INTEGERs: min, default, max
1722 Currently this tunable has no effect.
1724 addr_scope_policy - INTEGER
1725 Control IPv4 address scoping - draft-stewart-tsvwg-sctp-ipv4-00
1727 0 - Disable IPv4 address scoping
1728 1 - Enable IPv4 address scoping
1729 2 - Follow draft but allow IPv4 private addresses
1730 3 - Follow draft but allow IPv4 link local addresses
1735 /proc/sys/net/core/*
1736 Please see: Documentation/sysctl/net.txt for descriptions of these entries.
1739 /proc/sys/net/unix/*
1740 max_dgram_qlen - INTEGER
1741 The maximum length of dgram socket receive queue
1748 /proc/sys/net/irda/*
1749 fast_poll_increase FIXME
1750 warn_noreply_time FIXME
1751 discovery_slots FIXME
1754 discovery_timeout FIXME
1755 lap_keepalive_time FIXME
1756 max_noreply_time FIXME
1757 max_tx_data_size FIXME
1759 min_tx_turn_time FIXME