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
16 ip_no_pmtu_disc - BOOLEAN
17 Disable Path MTU Discovery.
21 default 562 - minimum discovered Path MTU
24 Time, in seconds, that cached PMTU information is kept.
27 The advertised MSS depends on the first hop route MTU, but will
28 never be lower than this setting.
30 rt_cache_rebuild_count - INTEGER
31 The per net-namespace route cache emergency rebuild threshold.
32 Any net-namespace having its route cache rebuilt due to
33 a hash bucket chain being too long more than this many times
34 will have its route caching disabled
38 ipfrag_high_thresh - INTEGER
39 Maximum memory used to reassemble IP fragments. When
40 ipfrag_high_thresh bytes of memory is allocated for this purpose,
41 the fragment handler will toss packets until ipfrag_low_thresh
44 ipfrag_low_thresh - INTEGER
45 See ipfrag_high_thresh
48 Time in seconds to keep an IP fragment in memory.
50 ipfrag_secret_interval - INTEGER
51 Regeneration interval (in seconds) of the hash secret (or lifetime
52 for the hash secret) for IP fragments.
55 ipfrag_max_dist - INTEGER
56 ipfrag_max_dist is a non-negative integer value which defines the
57 maximum "disorder" which is allowed among fragments which share a
58 common IP source address. Note that reordering of packets is
59 not unusual, but if a large number of fragments arrive from a source
60 IP address while a particular fragment queue remains incomplete, it
61 probably indicates that one or more fragments belonging to that queue
62 have been lost. When ipfrag_max_dist is positive, an additional check
63 is done on fragments before they are added to a reassembly queue - if
64 ipfrag_max_dist (or more) fragments have arrived from a particular IP
65 address between additions to any IP fragment queue using that source
66 address, it's presumed that one or more fragments in the queue are
67 lost. The existing fragment queue will be dropped, and a new one
68 started. An ipfrag_max_dist value of zero disables this check.
70 Using a very small value, e.g. 1 or 2, for ipfrag_max_dist can
71 result in unnecessarily dropping fragment queues when normal
72 reordering of packets occurs, which could lead to poor application
73 performance. Using a very large value, e.g. 50000, increases the
74 likelihood of incorrectly reassembling IP fragments that originate
75 from different IP datagrams, which could result in data corruption.
80 inet_peer_threshold - INTEGER
81 The approximate size of the storage. Starting from this threshold
82 entries will be thrown aggressively. This threshold also determines
83 entries' time-to-live and time intervals between garbage collection
84 passes. More entries, less time-to-live, less GC interval.
86 inet_peer_minttl - INTEGER
87 Minimum time-to-live of entries. Should be enough to cover fragment
88 time-to-live on the reassembling side. This minimum time-to-live is
89 guaranteed if the pool size is less than inet_peer_threshold.
92 inet_peer_maxttl - INTEGER
93 Maximum time-to-live of entries. Unused entries will expire after
94 this period of time if there is no memory pressure on the pool (i.e.
95 when the number of entries in the pool is very small).
98 inet_peer_gc_mintime - INTEGER
99 Minimum interval between garbage collection passes. This interval is
100 in effect under high memory pressure on the pool.
103 inet_peer_gc_maxtime - INTEGER
104 Minimum interval between garbage collection passes. This interval is
105 in effect under low (or absent) memory pressure on the pool.
111 Limit of socket listen() backlog, known in userspace as SOMAXCONN.
112 Defaults to 128. See also tcp_max_syn_backlog for additional tuning
116 Controls Appropriate Byte Count (ABC) defined in RFC3465.
117 ABC is a way of increasing congestion window (cwnd) more slowly
118 in response to partial acknowledgments.
120 0 increase cwnd once per acknowledgment (no ABC)
121 1 increase cwnd once per acknowledgment of full sized segment
122 2 allow increase cwnd by two if acknowledgment is
123 of two segments to compensate for delayed acknowledgments.
126 tcp_abort_on_overflow - BOOLEAN
127 If listening service is too slow to accept new connections,
128 reset them. Default state is FALSE. It means that if overflow
129 occurred due to a burst, connection will recover. Enable this
130 option _only_ if you are really sure that listening daemon
131 cannot be tuned to accept connections faster. Enabling this
132 option can harm clients of your server.
134 tcp_adv_win_scale - INTEGER
135 Count buffering overhead as bytes/2^tcp_adv_win_scale
136 (if tcp_adv_win_scale > 0) or bytes-bytes/2^(-tcp_adv_win_scale),
140 tcp_allowed_congestion_control - STRING
141 Show/set the congestion control choices available to non-privileged
142 processes. The list is a subset of those listed in
143 tcp_available_congestion_control.
144 Default is "reno" and the default setting (tcp_congestion_control).
146 tcp_app_win - INTEGER
147 Reserve max(window/2^tcp_app_win, mss) of window for application
148 buffer. Value 0 is special, it means that nothing is reserved.
151 tcp_available_congestion_control - STRING
152 Shows the available congestion control choices that are registered.
153 More congestion control algorithms may be available as modules,
156 tcp_base_mss - INTEGER
157 The initial value of search_low to be used by the packetization layer
158 Path MTU discovery (MTU probing). If MTU probing is enabled,
159 this is the initial MSS used by the connection.
161 tcp_congestion_control - STRING
162 Set the congestion control algorithm to be used for new
163 connections. The algorithm "reno" is always available, but
164 additional choices may be available based on kernel configuration.
165 Default is set as part of kernel configuration.
167 tcp_cookie_size - INTEGER
168 Default size of TCP Cookie Transactions (TCPCT) option, that may be
169 overridden on a per socket basis by the TCPCT socket option.
170 Values greater than the maximum (16) are interpreted as the maximum.
171 Values greater than zero and less than the minimum (8) are interpreted
172 as the minimum. Odd values are interpreted as the next even value.
176 Allows TCP to send "duplicate" SACKs.
179 Enable Explicit Congestion Notification (ECN) in TCP. ECN is only
180 used when both ends of the TCP flow support it. It is useful to
181 avoid losses due to congestion (when the bottleneck router supports
186 2 Only server-side ECN enabled. If the other end does
187 not support ECN, behavior is like with ECN disabled.
191 Enable FACK congestion avoidance and fast retransmission.
192 The value is not used, if tcp_sack is not enabled.
194 tcp_fin_timeout - INTEGER
195 Time to hold socket in state FIN-WAIT-2, if it was closed
196 by our side. Peer can be broken and never close its side,
197 or even died unexpectedly. Default value is 60sec.
198 Usual value used in 2.2 was 180 seconds, you may restore
199 it, but remember that if your machine is even underloaded WEB server,
200 you risk to overflow memory with kilotons of dead sockets,
201 FIN-WAIT-2 sockets are less dangerous than FIN-WAIT-1,
202 because they eat maximum 1.5K of memory, but they tend
203 to live longer. Cf. tcp_max_orphans.
206 Enables Forward RTO-Recovery (F-RTO) defined in RFC4138.
207 F-RTO is an enhanced recovery algorithm for TCP retransmission
208 timeouts. It is particularly beneficial in wireless environments
209 where packet loss is typically due to random radio interference
210 rather than intermediate router congestion. F-RTO is sender-side
211 only modification. Therefore it does not require any support from
214 If set to 1, basic version is enabled. 2 enables SACK enhanced
215 F-RTO if flow uses SACK. The basic version can be used also when
216 SACK is in use though scenario(s) with it exists where F-RTO
217 interacts badly with the packet counting of the SACK enabled TCP
220 tcp_frto_response - INTEGER
221 When F-RTO has detected that a TCP retransmission timeout was
222 spurious (i.e, the timeout would have been avoided had TCP set a
223 longer retransmission timeout), TCP has several options what to do
224 next. Possible values are:
225 0 Rate halving based; a smooth and conservative response,
226 results in halved cwnd and ssthresh after one RTT
227 1 Very conservative response; not recommended because even
228 though being valid, it interacts poorly with the rest of
229 Linux TCP, halves cwnd and ssthresh immediately
230 2 Aggressive response; undoes congestion control measures
231 that are now known to be unnecessary (ignoring the
232 possibility of a lost retransmission that would require
233 TCP to be more cautious), cwnd and ssthresh are restored
234 to the values prior timeout
235 Default: 0 (rate halving based)
237 tcp_keepalive_time - INTEGER
238 How often TCP sends out keepalive messages when keepalive is enabled.
241 tcp_keepalive_probes - INTEGER
242 How many keepalive probes TCP sends out, until it decides that the
243 connection is broken. Default value: 9.
245 tcp_keepalive_intvl - INTEGER
246 How frequently the probes are send out. Multiplied by
247 tcp_keepalive_probes it is time to kill not responding connection,
248 after probes started. Default value: 75sec i.e. connection
249 will be aborted after ~11 minutes of retries.
251 tcp_low_latency - BOOLEAN
252 If set, the TCP stack makes decisions that prefer lower
253 latency as opposed to higher throughput. By default, this
254 option is not set meaning that higher throughput is preferred.
255 An example of an application where this default should be
256 changed would be a Beowulf compute cluster.
259 tcp_max_orphans - INTEGER
260 Maximal number of TCP sockets not attached to any user file handle,
261 held by system. If this number is exceeded orphaned connections are
262 reset immediately and warning is printed. This limit exists
263 only to prevent simple DoS attacks, you _must_ not rely on this
264 or lower the limit artificially, but rather increase it
265 (probably, after increasing installed memory),
266 if network conditions require more than default value,
267 and tune network services to linger and kill such states
268 more aggressively. Let me to remind again: each orphan eats
269 up to ~64K of unswappable memory.
271 tcp_max_syn_backlog - INTEGER
272 Maximal number of remembered connection requests, which are
273 still did not receive an acknowledgment from connecting client.
274 Default value is 1024 for systems with more than 128Mb of memory,
275 and 128 for low memory machines. If server suffers of overload,
276 try to increase this number.
278 tcp_max_tw_buckets - INTEGER
279 Maximal number of timewait sockets held by system simultaneously.
280 If this number is exceeded time-wait socket is immediately destroyed
281 and warning is printed. This limit exists only to prevent
282 simple DoS attacks, you _must_ not lower the limit artificially,
283 but rather increase it (probably, after increasing installed memory),
284 if network conditions require more than default value.
286 tcp_mem - vector of 3 INTEGERs: min, pressure, max
287 min: below this number of pages TCP is not bothered about its
290 pressure: when amount of memory allocated by TCP exceeds this number
291 of pages, TCP moderates its memory consumption and enters memory
292 pressure mode, which is exited when memory consumption falls
295 max: number of pages allowed for queueing by all TCP sockets.
297 Defaults are calculated at boot time from amount of available
300 tcp_moderate_rcvbuf - BOOLEAN
301 If set, TCP performs receive buffer auto-tuning, attempting to
302 automatically size the buffer (no greater than tcp_rmem[2]) to
303 match the size required by the path for full throughput. Enabled by
306 tcp_mtu_probing - INTEGER
307 Controls TCP Packetization-Layer Path MTU Discovery. Takes three
310 1 - Disabled by default, enabled when an ICMP black hole detected
311 2 - Always enabled, use initial MSS of tcp_base_mss.
313 tcp_no_metrics_save - BOOLEAN
314 By default, TCP saves various connection metrics in the route cache
315 when the connection closes, so that connections established in the
316 near future can use these to set initial conditions. Usually, this
317 increases overall performance, but may sometimes cause performance
318 degradation. If set, TCP will not cache metrics on closing
321 tcp_orphan_retries - INTEGER
322 This value influences the timeout of a locally closed TCP connection,
323 when RTO retransmissions remain unacknowledged.
324 See tcp_retries2 for more details.
326 The default value is 7.
327 If your machine is a loaded WEB server,
328 you should think about lowering this value, such sockets
329 may consume significant resources. Cf. tcp_max_orphans.
331 tcp_reordering - INTEGER
332 Maximal reordering of packets in a TCP stream.
335 tcp_retrans_collapse - BOOLEAN
336 Bug-to-bug compatibility with some broken printers.
337 On retransmit try to send bigger packets to work around bugs in
340 tcp_retries1 - INTEGER
341 This value influences the time, after which TCP decides, that
342 something is wrong due to unacknowledged RTO retransmissions,
343 and reports this suspicion to the network layer.
344 See tcp_retries2 for more details.
346 RFC 1122 recommends at least 3 retransmissions, which is the
349 tcp_retries2 - INTEGER
350 This value influences the timeout of an alive TCP connection,
351 when RTO retransmissions remain unacknowledged.
352 Given a value of N, a hypothetical TCP connection following
353 exponential backoff with an initial RTO of TCP_RTO_MIN would
354 retransmit N times before killing the connection at the (N+1)th RTO.
356 The default value of 15 yields a hypothetical timeout of 924.6
357 seconds and is a lower bound for the effective timeout.
358 TCP will effectively time out at the first RTO which exceeds the
359 hypothetical timeout.
361 RFC 1122 recommends at least 100 seconds for the timeout,
362 which corresponds to a value of at least 8.
364 tcp_rfc1337 - BOOLEAN
365 If set, the TCP stack behaves conforming to RFC1337. If unset,
366 we are not conforming to RFC, but prevent TCP TIME_WAIT
370 tcp_rmem - vector of 3 INTEGERs: min, default, max
371 min: Minimal size of receive buffer used by TCP sockets.
372 It is guaranteed to each TCP socket, even under moderate memory
376 default: initial size of receive buffer used by TCP sockets.
377 This value overrides net.core.rmem_default used by other protocols.
378 Default: 87380 bytes. This value results in window of 65535 with
379 default setting of tcp_adv_win_scale and tcp_app_win:0 and a bit
380 less for default tcp_app_win. See below about these variables.
382 max: maximal size of receive buffer allowed for automatically
383 selected receiver buffers for TCP socket. This value does not override
384 net.core.rmem_max. Calling setsockopt() with SO_RCVBUF disables
385 automatic tuning of that socket's receive buffer size, in which
386 case this value is ignored.
387 Default: between 87380B and 4MB, depending on RAM size.
390 Enable select acknowledgments (SACKS).
392 tcp_slow_start_after_idle - BOOLEAN
393 If set, provide RFC2861 behavior and time out the congestion
394 window after an idle period. An idle period is defined at
395 the current RTO. If unset, the congestion window will not
396 be timed out after an idle period.
400 Use the Host requirements interpretation of the TCP urgent pointer field.
401 Most hosts use the older BSD interpretation, so if you turn this on
402 Linux might not communicate correctly with them.
405 tcp_synack_retries - INTEGER
406 Number of times SYNACKs for a passive TCP connection attempt will
407 be retransmitted. Should not be higher than 255. Default value
408 is 5, which corresponds to ~180seconds.
410 tcp_syncookies - BOOLEAN
411 Only valid when the kernel was compiled with CONFIG_SYNCOOKIES
412 Send out syncookies when the syn backlog queue of a socket
413 overflows. This is to prevent against the common 'SYN flood attack'
416 Note, that syncookies is fallback facility.
417 It MUST NOT be used to help highly loaded servers to stand
418 against legal connection rate. If you see SYN flood warnings
419 in your logs, but investigation shows that they occur
420 because of overload with legal connections, you should tune
421 another parameters until this warning disappear.
422 See: tcp_max_syn_backlog, tcp_synack_retries, tcp_abort_on_overflow.
424 syncookies seriously violate TCP protocol, do not allow
425 to use TCP extensions, can result in serious degradation
426 of some services (f.e. SMTP relaying), visible not by you,
427 but your clients and relays, contacting you. While you see
428 SYN flood warnings in logs not being really flooded, your server
429 is seriously misconfigured.
431 tcp_syn_retries - INTEGER
432 Number of times initial SYNs for an active TCP connection attempt
433 will be retransmitted. Should not be higher than 255. Default value
434 is 5, which corresponds to ~180seconds.
436 tcp_timestamps - BOOLEAN
437 Enable timestamps as defined in RFC1323.
439 tcp_tso_win_divisor - INTEGER
440 This allows control over what percentage of the congestion window
441 can be consumed by a single TSO frame.
442 The setting of this parameter is a choice between burstiness and
443 building larger TSO frames.
446 tcp_tw_recycle - BOOLEAN
447 Enable fast recycling TIME-WAIT sockets. Default value is 0.
448 It should not be changed without advice/request of technical
451 tcp_tw_reuse - BOOLEAN
452 Allow to reuse TIME-WAIT sockets for new connections when it is
453 safe from protocol viewpoint. Default value is 0.
454 It should not be changed without advice/request of technical
457 tcp_window_scaling - BOOLEAN
458 Enable window scaling as defined in RFC1323.
460 tcp_wmem - vector of 3 INTEGERs: min, default, max
461 min: Amount of memory reserved for send buffers for TCP sockets.
462 Each TCP socket has rights to use it due to fact of its birth.
465 default: initial size of send buffer used by TCP sockets. This
466 value overrides net.core.wmem_default used by other protocols.
467 It is usually lower than net.core.wmem_default.
470 max: Maximal amount of memory allowed for automatically tuned
471 send buffers for TCP sockets. This value does not override
472 net.core.wmem_max. Calling setsockopt() with SO_SNDBUF disables
473 automatic tuning of that socket's send buffer size, in which case
474 this value is ignored.
475 Default: between 64K and 4MB, depending on RAM size.
477 tcp_workaround_signed_windows - BOOLEAN
478 If set, assume no receipt of a window scaling option means the
479 remote TCP is broken and treats the window as a signed quantity.
480 If unset, assume the remote TCP is not broken even if we do
481 not receive a window scaling option from them.
484 tcp_dma_copybreak - INTEGER
485 Lower limit, in bytes, of the size of socket reads that will be
486 offloaded to a DMA copy engine, if one is present in the system
487 and CONFIG_NET_DMA is enabled.
492 udp_mem - vector of 3 INTEGERs: min, pressure, max
493 Number of pages allowed for queueing by all UDP sockets.
495 min: Below this number of pages UDP is not bothered about its
496 memory appetite. When amount of memory allocated by UDP exceeds
497 this number, UDP starts to moderate memory usage.
499 pressure: This value was introduced to follow format of tcp_mem.
501 max: Number of pages allowed for queueing by all UDP sockets.
503 Default is calculated at boot time from amount of available memory.
505 udp_rmem_min - INTEGER
506 Minimal size of receive buffer used by UDP sockets in moderation.
507 Each UDP socket is able to use the size for receiving data, even if
508 total pages of UDP sockets exceed udp_mem pressure. The unit is byte.
511 udp_wmem_min - INTEGER
512 Minimal size of send buffer used by UDP sockets in moderation.
513 Each UDP socket is able to use the size for sending data, even if
514 total pages of UDP sockets exceed udp_mem pressure. The unit is byte.
519 cipso_cache_enable - BOOLEAN
520 If set, enable additions to and lookups from the CIPSO label mapping
521 cache. If unset, additions are ignored and lookups always result in a
522 miss. However, regardless of the setting the cache is still
523 invalidated when required when means you can safely toggle this on and
524 off and the cache will always be "safe".
527 cipso_cache_bucket_size - INTEGER
528 The CIPSO label cache consists of a fixed size hash table with each
529 hash bucket containing a number of cache entries. This variable limits
530 the number of entries in each hash bucket; the larger the value the
531 more CIPSO label mappings that can be cached. When the number of
532 entries in a given hash bucket reaches this limit adding new entries
533 causes the oldest entry in the bucket to be removed to make room.
536 cipso_rbm_optfmt - BOOLEAN
537 Enable the "Optimized Tag 1 Format" as defined in section 3.4.2.6 of
538 the CIPSO draft specification (see Documentation/netlabel for details).
539 This means that when set the CIPSO tag will be padded with empty
540 categories in order to make the packet data 32-bit aligned.
543 cipso_rbm_structvalid - BOOLEAN
544 If set, do a very strict check of the CIPSO option when
545 ip_options_compile() is called. If unset, relax the checks done during
546 ip_options_compile(). Either way is "safe" as errors are caught else
547 where in the CIPSO processing code but setting this to 0 (False) should
548 result in less work (i.e. it should be faster) but could cause problems
549 with other implementations that require strict checking.
554 ip_local_port_range - 2 INTEGERS
555 Defines the local port range that is used by TCP and UDP to
556 choose the local port. The first number is the first, the
557 second the last local port number. Default value depends on
558 amount of memory available on the system:
560 < 128Mb 1024-4999 or even less.
561 This number defines number of active connections, which this
562 system can issue simultaneously to systems not supporting
563 TCP extensions (timestamps). With tcp_tw_recycle enabled
564 (i.e. by default) range 1024-4999 is enough to issue up to
565 2000 connections per second to systems supporting timestamps.
567 ip_nonlocal_bind - BOOLEAN
568 If set, allows processes to bind() to non-local IP addresses,
569 which can be quite useful - but may break some applications.
573 If set non-zero, enables support for dynamic addresses.
574 If set to a non-zero value larger than 1, a kernel log
575 message will be printed when dynamic address rewriting
579 icmp_echo_ignore_all - BOOLEAN
580 If set non-zero, then the kernel will ignore all ICMP ECHO
584 icmp_echo_ignore_broadcasts - BOOLEAN
585 If set non-zero, then the kernel will ignore all ICMP ECHO and
586 TIMESTAMP requests sent to it via broadcast/multicast.
589 icmp_ratelimit - INTEGER
590 Limit the maximal rates for sending ICMP packets whose type matches
591 icmp_ratemask (see below) to specific targets.
592 0 to disable any limiting,
593 otherwise the minimal space between responses in milliseconds.
596 icmp_ratemask - INTEGER
597 Mask made of ICMP types for which rates are being limited.
598 Significant bits: IHGFEDCBA9876543210
599 Default mask: 0000001100000011000 (6168)
601 Bit definitions (see include/linux/icmp.h):
603 3 Destination Unreachable *
608 C Parameter Problem *
613 H Address Mask Request
616 * These are rate limited by default (see default mask above)
618 icmp_ignore_bogus_error_responses - BOOLEAN
619 Some routers violate RFC1122 by sending bogus responses to broadcast
620 frames. Such violations are normally logged via a kernel warning.
621 If this is set to TRUE, the kernel will not give such warnings, which
622 will avoid log file clutter.
625 icmp_errors_use_inbound_ifaddr - BOOLEAN
627 If zero, icmp error messages are sent with the primary address of
628 the exiting interface.
630 If non-zero, the message will be sent with the primary address of
631 the interface that received the packet that caused the icmp error.
632 This is the behaviour network many administrators will expect from
633 a router. And it can make debugging complicated network layouts
636 Note that if no primary address exists for the interface selected,
637 then the primary address of the first non-loopback interface that
638 has one will be used regardless of this setting.
642 igmp_max_memberships - INTEGER
643 Change the maximum number of multicast groups we can subscribe to.
646 conf/interface/* changes special settings per interface (where "interface" is
647 the name of your network interface)
648 conf/all/* is special, changes the settings for all interfaces
651 log_martians - BOOLEAN
652 Log packets with impossible addresses to kernel log.
653 log_martians for the interface will be enabled if at least one of
654 conf/{all,interface}/log_martians is set to TRUE,
655 it will be disabled otherwise
657 accept_redirects - BOOLEAN
658 Accept ICMP redirect messages.
659 accept_redirects for the interface will be enabled if:
660 - both conf/{all,interface}/accept_redirects are TRUE in the case
661 forwarding for the interface is enabled
663 - at least one of conf/{all,interface}/accept_redirects is TRUE in the
664 case forwarding for the interface is disabled
665 accept_redirects for the interface will be disabled otherwise
670 Enable IP forwarding on this interface.
672 mc_forwarding - BOOLEAN
673 Do multicast routing. The kernel needs to be compiled with CONFIG_MROUTE
674 and a multicast routing daemon is required.
675 conf/all/mc_forwarding must also be set to TRUE to enable multicast
676 routing for the interface
679 Integer value used to differentiate the devices by the medium they
680 are attached to. Two devices can have different id values when
681 the broadcast packets are received only on one of them.
682 The default value 0 means that the device is the only interface
683 to its medium, value of -1 means that medium is not known.
685 Currently, it is used to change the proxy_arp behavior:
686 the proxy_arp feature is enabled for packets forwarded between
687 two devices attached to different media.
691 proxy_arp for the interface will be enabled if at least one of
692 conf/{all,interface}/proxy_arp is set to TRUE,
693 it will be disabled otherwise
695 shared_media - BOOLEAN
696 Send(router) or accept(host) RFC1620 shared media redirects.
697 Overrides ip_secure_redirects.
698 shared_media for the interface will be enabled if at least one of
699 conf/{all,interface}/shared_media is set to TRUE,
700 it will be disabled otherwise
703 secure_redirects - BOOLEAN
704 Accept ICMP redirect messages only for gateways,
705 listed in default gateway list.
706 secure_redirects for the interface will be enabled if at least one of
707 conf/{all,interface}/secure_redirects is set to TRUE,
708 it will be disabled otherwise
711 send_redirects - BOOLEAN
712 Send redirects, if router.
713 send_redirects for the interface will be enabled if at least one of
714 conf/{all,interface}/send_redirects is set to TRUE,
715 it will be disabled otherwise
718 bootp_relay - BOOLEAN
719 Accept packets with source address 0.b.c.d destined
720 not to this host as local ones. It is supposed, that
721 BOOTP relay daemon will catch and forward such packets.
722 conf/all/bootp_relay must also be set to TRUE to enable BOOTP relay
727 accept_source_route - BOOLEAN
728 Accept packets with SRR option.
729 conf/all/accept_source_route must also be set to TRUE to accept packets
730 with SRR option on the interface
731 default TRUE (router)
734 accept_local - BOOLEAN
735 Accept packets with local source addresses. In combination with
736 suitable routing, this can be used to direct packets between two
737 local interfaces over the wire and have them accepted properly.
741 0 - No source validation.
742 1 - Strict mode as defined in RFC3704 Strict Reverse Path
743 Each incoming packet is tested against the FIB and if the interface
744 is not the best reverse path the packet check will fail.
745 By default failed packets are discarded.
746 2 - Loose mode as defined in RFC3704 Loose Reverse Path
747 Each incoming packet's source address is also tested against the FIB
748 and if the source address is not reachable via any interface
749 the packet check will fail.
751 Current recommended practice in RFC3704 is to enable strict mode
752 to prevent IP spoofing from DDos attacks. If using asymmetric routing
753 or other complicated routing, then loose mode is recommended.
755 The max value from conf/{all,interface}/rp_filter is used
756 when doing source validation on the {interface}.
758 Default value is 0. Note that some distributions enable it
762 1 - Allows you to have multiple network interfaces on the same
763 subnet, and have the ARPs for each interface be answered
764 based on whether or not the kernel would route a packet from
765 the ARP'd IP out that interface (therefore you must use source
766 based routing for this to work). In other words it allows control
767 of which cards (usually 1) will respond to an arp request.
769 0 - (default) The kernel can respond to arp requests with addresses
770 from other interfaces. This may seem wrong but it usually makes
771 sense, because it increases the chance of successful communication.
772 IP addresses are owned by the complete host on Linux, not by
773 particular interfaces. Only for more complex setups like load-
774 balancing, does this behaviour cause problems.
776 arp_filter for the interface will be enabled if at least one of
777 conf/{all,interface}/arp_filter is set to TRUE,
778 it will be disabled otherwise
780 arp_announce - INTEGER
781 Define different restriction levels for announcing the local
782 source IP address from IP packets in ARP requests sent on
784 0 - (default) Use any local address, configured on any interface
785 1 - Try to avoid local addresses that are not in the target's
786 subnet for this interface. This mode is useful when target
787 hosts reachable via this interface require the source IP
788 address in ARP requests to be part of their logical network
789 configured on the receiving interface. When we generate the
790 request we will check all our subnets that include the
791 target IP and will preserve the source address if it is from
792 such subnet. If there is no such subnet we select source
793 address according to the rules for level 2.
794 2 - Always use the best local address for this target.
795 In this mode we ignore the source address in the IP packet
796 and try to select local address that we prefer for talks with
797 the target host. Such local address is selected by looking
798 for primary IP addresses on all our subnets on the outgoing
799 interface that include the target IP address. If no suitable
800 local address is found we select the first local address
801 we have on the outgoing interface or on all other interfaces,
802 with the hope we will receive reply for our request and
803 even sometimes no matter the source IP address we announce.
805 The max value from conf/{all,interface}/arp_announce is used.
807 Increasing the restriction level gives more chance for
808 receiving answer from the resolved target while decreasing
809 the level announces more valid sender's information.
812 Define different modes for sending replies in response to
813 received ARP requests that resolve local target IP addresses:
814 0 - (default): reply for any local target IP address, configured
816 1 - reply only if the target IP address is local address
817 configured on the incoming interface
818 2 - reply only if the target IP address is local address
819 configured on the incoming interface and both with the
820 sender's IP address are part from same subnet on this interface
821 3 - do not reply for local addresses configured with scope host,
822 only resolutions for global and link addresses are replied
824 8 - do not reply for all local addresses
826 The max value from conf/{all,interface}/arp_ignore is used
827 when ARP request is received on the {interface}
830 Define mode for notification of address and device changes.
831 0 - (default): do nothing
832 1 - Generate gratuitous arp replies when device is brought up
833 or hardware address changes.
836 Define behavior when gratuitous arp replies are received:
837 0 - drop gratuitous arp frames
838 1 - accept gratuitous arp frames
840 app_solicit - INTEGER
841 The maximum number of probes to send to the user space ARP daemon
842 via netlink before dropping back to multicast probes (see
843 mcast_solicit). Defaults to 0.
845 disable_policy - BOOLEAN
846 Disable IPSEC policy (SPD) for this interface
848 disable_xfrm - BOOLEAN
849 Disable IPSEC encryption on this interface, whatever the policy
854 Allows you to write a number, which can be used as required.
864 delon.nicolas@wanadoo.fr
869 /proc/sys/net/ipv6/* Variables:
871 IPv6 has no global variables such as tcp_*. tcp_* settings under ipv4/ also
872 apply to IPv6 [XXX?].
875 Default value for IPV6_V6ONLY socket option,
876 which restricts use of the IPv6 socket to IPv6 communication
878 TRUE: disable IPv4-mapped address feature
879 FALSE: enable IPv4-mapped address feature
881 Default: FALSE (as specified in RFC2553bis)
885 ip6frag_high_thresh - INTEGER
886 Maximum memory used to reassemble IPv6 fragments. When
887 ip6frag_high_thresh bytes of memory is allocated for this purpose,
888 the fragment handler will toss packets until ip6frag_low_thresh
891 ip6frag_low_thresh - INTEGER
892 See ip6frag_high_thresh
894 ip6frag_time - INTEGER
895 Time in seconds to keep an IPv6 fragment in memory.
897 ip6frag_secret_interval - INTEGER
898 Regeneration interval (in seconds) of the hash secret (or lifetime
899 for the hash secret) for IPv6 fragments.
903 Change the interface-specific default settings.
907 Change all the interface-specific settings.
909 [XXX: Other special features than forwarding?]
911 conf/all/forwarding - BOOLEAN
912 Enable global IPv6 forwarding between all interfaces.
914 IPv4 and IPv6 work differently here; e.g. netfilter must be used
915 to control which interfaces may forward packets and which not.
917 This also sets all interfaces' Host/Router setting
918 'forwarding' to the specified value. See below for details.
920 This referred to as global forwarding.
926 Change special settings per interface.
928 The functional behaviour for certain settings is different
929 depending on whether local forwarding is enabled or not.
932 Accept Router Advertisements; autoconfigure using them.
934 Functional default: enabled if local forwarding is disabled.
935 disabled if local forwarding is enabled.
937 accept_ra_defrtr - BOOLEAN
938 Learn default router in Router Advertisement.
940 Functional default: enabled if accept_ra is enabled.
941 disabled if accept_ra is disabled.
943 accept_ra_pinfo - BOOLEAN
944 Learn Prefix Information in Router Advertisement.
946 Functional default: enabled if accept_ra is enabled.
947 disabled if accept_ra is disabled.
949 accept_ra_rt_info_max_plen - INTEGER
950 Maximum prefix length of Route Information in RA.
952 Route Information w/ prefix larger than or equal to this
953 variable shall be ignored.
955 Functional default: 0 if accept_ra_rtr_pref is enabled.
956 -1 if accept_ra_rtr_pref is disabled.
958 accept_ra_rtr_pref - BOOLEAN
959 Accept Router Preference in RA.
961 Functional default: enabled if accept_ra is enabled.
962 disabled if accept_ra is disabled.
964 accept_redirects - BOOLEAN
967 Functional default: enabled if local forwarding is disabled.
968 disabled if local forwarding is enabled.
970 accept_source_route - INTEGER
971 Accept source routing (routing extension header).
973 >= 0: Accept only routing header type 2.
974 < 0: Do not accept routing header.
979 Autoconfigure addresses using Prefix Information in Router
982 Functional default: enabled if accept_ra_pinfo is enabled.
983 disabled if accept_ra_pinfo is disabled.
985 dad_transmits - INTEGER
986 The amount of Duplicate Address Detection probes to send.
990 Configure interface-specific Host/Router behaviour.
992 Note: It is recommended to have the same setting on all
993 interfaces; mixed router/host scenarios are rather uncommon.
997 By default, Host behaviour is assumed. This means:
999 1. IsRouter flag is not set in Neighbour Advertisements.
1000 2. Router Solicitations are being sent when necessary.
1001 3. If accept_ra is TRUE (default), accept Router
1002 Advertisements (and do autoconfiguration).
1003 4. If accept_redirects is TRUE (default), accept Redirects.
1007 If local forwarding is enabled, Router behaviour is assumed.
1008 This means exactly the reverse from the above:
1010 1. IsRouter flag is set in Neighbour Advertisements.
1011 2. Router Solicitations are not sent.
1012 3. Router Advertisements are ignored.
1013 4. Redirects are ignored.
1015 Default: FALSE if global forwarding is disabled (default),
1019 Default Hop Limit to set.
1023 Default Maximum Transfer Unit
1024 Default: 1280 (IPv6 required minimum)
1026 router_probe_interval - INTEGER
1027 Minimum interval (in seconds) between Router Probing described
1032 router_solicitation_delay - INTEGER
1033 Number of seconds to wait after interface is brought up
1034 before sending Router Solicitations.
1037 router_solicitation_interval - INTEGER
1038 Number of seconds to wait between Router Solicitations.
1041 router_solicitations - INTEGER
1042 Number of Router Solicitations to send until assuming no
1043 routers are present.
1046 use_tempaddr - INTEGER
1047 Preference for Privacy Extensions (RFC3041).
1048 <= 0 : disable Privacy Extensions
1049 == 1 : enable Privacy Extensions, but prefer public
1050 addresses over temporary addresses.
1051 > 1 : enable Privacy Extensions and prefer temporary
1052 addresses over public addresses.
1053 Default: 0 (for most devices)
1054 -1 (for point-to-point devices and loopback devices)
1056 temp_valid_lft - INTEGER
1057 valid lifetime (in seconds) for temporary addresses.
1058 Default: 604800 (7 days)
1060 temp_prefered_lft - INTEGER
1061 Preferred lifetime (in seconds) for temporary addresses.
1062 Default: 86400 (1 day)
1064 max_desync_factor - INTEGER
1065 Maximum value for DESYNC_FACTOR, which is a random value
1066 that ensures that clients don't synchronize with each
1067 other and generate new addresses at exactly the same time.
1068 value is in seconds.
1071 regen_max_retry - INTEGER
1072 Number of attempts before give up attempting to generate
1073 valid temporary addresses.
1076 max_addresses - INTEGER
1077 Maximum number of autoconfigured addresses per interface. Setting
1078 to zero disables the limitation. It is not recommended to set this
1079 value too large (or to zero) because it would be an easy way to
1080 crash the kernel by allowing too many addresses to be created.
1083 disable_ipv6 - BOOLEAN
1084 Disable IPv6 operation. If accept_dad is set to 2, this value
1085 will be dynamically set to TRUE if DAD fails for the link-local
1087 Default: FALSE (enable IPv6 operation)
1089 When this value is changed from 1 to 0 (IPv6 is being enabled),
1090 it will dynamically create a link-local address on the given
1091 interface and start Duplicate Address Detection, if necessary.
1093 When this value is changed from 0 to 1 (IPv6 is being disabled),
1094 it will dynamically delete all address on the given interface.
1096 accept_dad - INTEGER
1097 Whether to accept DAD (Duplicate Address Detection).
1099 1: Enable DAD (default)
1100 2: Enable DAD, and disable IPv6 operation if MAC-based duplicate
1101 link-local address has been found.
1103 force_tllao - BOOLEAN
1104 Enable sending the target link-layer address option even when
1105 responding to a unicast neighbor solicitation.
1108 Quoting from RFC 2461, section 4.4, Target link-layer address:
1110 "The option MUST be included for multicast solicitations in order to
1111 avoid infinite Neighbor Solicitation "recursion" when the peer node
1112 does not have a cache entry to return a Neighbor Advertisements
1113 message. When responding to unicast solicitations, the option can be
1114 omitted since the sender of the solicitation has the correct link-
1115 layer address; otherwise it would not have be able to send the unicast
1116 solicitation in the first place. However, including the link-layer
1117 address in this case adds little overhead and eliminates a potential
1118 race condition where the sender deletes the cached link-layer address
1119 prior to receiving a response to a previous solicitation."
1123 Limit the maximal rates for sending ICMPv6 packets.
1124 0 to disable any limiting,
1125 otherwise the minimal space between responses in milliseconds.
1130 Pekka Savola <pekkas@netcore.fi>
1131 YOSHIFUJI Hideaki / USAGI Project <yoshfuji@linux-ipv6.org>
1134 /proc/sys/net/bridge/* Variables:
1136 bridge-nf-call-arptables - BOOLEAN
1137 1 : pass bridged ARP traffic to arptables' FORWARD chain.
1141 bridge-nf-call-iptables - BOOLEAN
1142 1 : pass bridged IPv4 traffic to iptables' chains.
1146 bridge-nf-call-ip6tables - BOOLEAN
1147 1 : pass bridged IPv6 traffic to ip6tables' chains.
1151 bridge-nf-filter-vlan-tagged - BOOLEAN
1152 1 : pass bridged vlan-tagged ARP/IP/IPv6 traffic to {arp,ip,ip6}tables.
1156 bridge-nf-filter-pppoe-tagged - BOOLEAN
1157 1 : pass bridged pppoe-tagged IP/IPv6 traffic to {ip,ip6}tables.
1162 proc/sys/net/sctp/* Variables:
1164 addip_enable - BOOLEAN
1165 Enable or disable extension of Dynamic Address Reconfiguration
1166 (ADD-IP) functionality specified in RFC5061. This extension provides
1167 the ability to dynamically add and remove new addresses for the SCTP
1170 1: Enable extension.
1172 0: Disable extension.
1176 addip_noauth_enable - BOOLEAN
1177 Dynamic Address Reconfiguration (ADD-IP) requires the use of
1178 authentication to protect the operations of adding or removing new
1179 addresses. This requirement is mandated so that unauthorized hosts
1180 would not be able to hijack associations. However, older
1181 implementations may not have implemented this requirement while
1182 allowing the ADD-IP extension. For reasons of interoperability,
1183 we provide this variable to control the enforcement of the
1184 authentication requirement.
1186 1: Allow ADD-IP extension to be used without authentication. This
1187 should only be set in a closed environment for interoperability
1188 with older implementations.
1190 0: Enforce the authentication requirement
1194 auth_enable - BOOLEAN
1195 Enable or disable Authenticated Chunks extension. This extension
1196 provides the ability to send and receive authenticated chunks and is
1197 required for secure operation of Dynamic Address Reconfiguration
1200 1: Enable this extension.
1201 0: Disable this extension.
1205 prsctp_enable - BOOLEAN
1206 Enable or disable the Partial Reliability extension (RFC3758) which
1207 is used to notify peers that a given DATA should no longer be expected.
1215 The limit of the number of new packets that can be initially sent. It
1216 controls how bursty the generated traffic can be.
1220 association_max_retrans - INTEGER
1221 Set the maximum number for retransmissions that an association can
1222 attempt deciding that the remote end is unreachable. If this value
1223 is exceeded, the association is terminated.
1227 max_init_retransmits - INTEGER
1228 The maximum number of retransmissions of INIT and COOKIE-ECHO chunks
1229 that an association will attempt before declaring the destination
1230 unreachable and terminating.
1234 path_max_retrans - INTEGER
1235 The maximum number of retransmissions that will be attempted on a given
1236 path. Once this threshold is exceeded, the path is considered
1237 unreachable, and new traffic will use a different path when the
1238 association is multihomed.
1242 rto_initial - INTEGER
1243 The initial round trip timeout value in milliseconds that will be used
1244 in calculating round trip times. This is the initial time interval
1245 for retransmissions.
1250 The maximum value (in milliseconds) of the round trip timeout. This
1251 is the largest time interval that can elapse between retransmissions.
1256 The minimum value (in milliseconds) of the round trip timeout. This
1257 is the smallest time interval the can elapse between retransmissions.
1261 hb_interval - INTEGER
1262 The interval (in milliseconds) between HEARTBEAT chunks. These chunks
1263 are sent at the specified interval on idle paths to probe the state of
1264 a given path between 2 associations.
1268 sack_timeout - INTEGER
1269 The amount of time (in milliseconds) that the implementation will wait
1274 valid_cookie_life - INTEGER
1275 The default lifetime of the SCTP cookie (in milliseconds). The cookie
1276 is used during association establishment.
1280 cookie_preserve_enable - BOOLEAN
1281 Enable or disable the ability to extend the lifetime of the SCTP cookie
1282 that is used during the establishment phase of SCTP association
1284 1: Enable cookie lifetime extension.
1289 rcvbuf_policy - INTEGER
1290 Determines if the receive buffer is attributed to the socket or to
1291 association. SCTP supports the capability to create multiple
1292 associations on a single socket. When using this capability, it is
1293 possible that a single stalled association that's buffering a lot
1294 of data may block other associations from delivering their data by
1295 consuming all of the receive buffer space. To work around this,
1296 the rcvbuf_policy could be set to attribute the receiver buffer space
1297 to each association instead of the socket. This prevents the described
1300 1: rcvbuf space is per association
1301 0: recbuf space is per socket
1305 sndbuf_policy - INTEGER
1306 Similar to rcvbuf_policy above, this applies to send buffer space.
1308 1: Send buffer is tracked per association
1309 0: Send buffer is tracked per socket.
1313 sctp_mem - vector of 3 INTEGERs: min, pressure, max
1314 Number of pages allowed for queueing by all SCTP sockets.
1316 min: Below this number of pages SCTP is not bothered about its
1317 memory appetite. When amount of memory allocated by SCTP exceeds
1318 this number, SCTP starts to moderate memory usage.
1320 pressure: This value was introduced to follow format of tcp_mem.
1322 max: Number of pages allowed for queueing by all SCTP sockets.
1324 Default is calculated at boot time from amount of available memory.
1326 sctp_rmem - vector of 3 INTEGERs: min, default, max
1327 See tcp_rmem for a description.
1329 sctp_wmem - vector of 3 INTEGERs: min, default, max
1330 See tcp_wmem for a description.
1332 addr_scope_policy - INTEGER
1333 Control IPv4 address scoping - draft-stewart-tsvwg-sctp-ipv4-00
1335 0 - Disable IPv4 address scoping
1336 1 - Enable IPv4 address scoping
1337 2 - Follow draft but allow IPv4 private addresses
1338 3 - Follow draft but allow IPv4 link local addresses
1343 /proc/sys/net/core/*
1344 dev_weight - INTEGER
1345 The maximum number of packets that kernel can handle on a NAPI
1346 interrupt, it's a Per-CPU variable.
1350 /proc/sys/net/unix/*
1351 max_dgram_qlen - INTEGER
1352 The maximum length of dgram socket receive queue
1359 /proc/sys/net/irda/*
1360 fast_poll_increase FIXME
1361 warn_noreply_time FIXME
1362 discovery_slots FIXME
1365 discovery_timeout FIXME
1366 lap_keepalive_time FIXME
1367 max_noreply_time FIXME
1368 max_tx_data_size FIXME
1370 min_tx_turn_time FIXME