tcp: TCP_NOTSENT_LOWAT socket option
[deliverable/linux.git] / Documentation / networking / ip-sysctl.txt
1 /proc/sys/net/ipv4/* Variables:
2
3 ip_forward - BOOLEAN
4 0 - disabled (default)
5 not 0 - enabled
6
7 Forward Packets between interfaces.
8
9 This variable is special, its change resets all configuration
10 parameters to their default state (RFC1122 for hosts, RFC1812
11 for routers)
12
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)
17
18 ip_no_pmtu_disc - BOOLEAN
19 Disable Path MTU Discovery.
20 default FALSE
21
22 min_pmtu - INTEGER
23 default 552 - minimum discovered Path MTU
24
25 route/max_size - INTEGER
26 Maximum number of routes allowed in the kernel. Increase
27 this when using large numbers of interfaces and/or routes.
28
29 neigh/default/gc_thresh1 - INTEGER
30 Minimum number of entries to keep. Garbage collector will not
31 purge entries if there are fewer than this number.
32 Default: 128
33
34 neigh/default/gc_thresh3 - INTEGER
35 Maximum number of neighbor entries allowed. Increase this
36 when using large numbers of interfaces and when communicating
37 with large numbers of directly-connected peers.
38 Default: 1024
39
40 neigh/default/unres_qlen_bytes - INTEGER
41 The maximum number of bytes which may be used by packets
42 queued for each unresolved address by other network layers.
43 (added in linux 3.3)
44 Setting negative value is meaningless and will return error.
45 Default: 65536 Bytes(64KB)
46
47 neigh/default/unres_qlen - INTEGER
48 The maximum number of packets which may be queued for each
49 unresolved address by other network layers.
50 (deprecated in linux 3.3) : use unres_qlen_bytes instead.
51 Prior to linux 3.3, the default value is 3 which may cause
52 unexpected packet loss. The current default value is calculated
53 according to default value of unres_qlen_bytes and true size of
54 packet.
55 Default: 31
56
57 mtu_expires - INTEGER
58 Time, in seconds, that cached PMTU information is kept.
59
60 min_adv_mss - INTEGER
61 The advertised MSS depends on the first hop route MTU, but will
62 never be lower than this setting.
63
64 IP Fragmentation:
65
66 ipfrag_high_thresh - INTEGER
67 Maximum memory used to reassemble IP fragments. When
68 ipfrag_high_thresh bytes of memory is allocated for this purpose,
69 the fragment handler will toss packets until ipfrag_low_thresh
70 is reached.
71
72 ipfrag_low_thresh - INTEGER
73 See ipfrag_high_thresh
74
75 ipfrag_time - INTEGER
76 Time in seconds to keep an IP fragment in memory.
77
78 ipfrag_secret_interval - INTEGER
79 Regeneration interval (in seconds) of the hash secret (or lifetime
80 for the hash secret) for IP fragments.
81 Default: 600
82
83 ipfrag_max_dist - INTEGER
84 ipfrag_max_dist is a non-negative integer value which defines the
85 maximum "disorder" which is allowed among fragments which share a
86 common IP source address. Note that reordering of packets is
87 not unusual, but if a large number of fragments arrive from a source
88 IP address while a particular fragment queue remains incomplete, it
89 probably indicates that one or more fragments belonging to that queue
90 have been lost. When ipfrag_max_dist is positive, an additional check
91 is done on fragments before they are added to a reassembly queue - if
92 ipfrag_max_dist (or more) fragments have arrived from a particular IP
93 address between additions to any IP fragment queue using that source
94 address, it's presumed that one or more fragments in the queue are
95 lost. The existing fragment queue will be dropped, and a new one
96 started. An ipfrag_max_dist value of zero disables this check.
97
98 Using a very small value, e.g. 1 or 2, for ipfrag_max_dist can
99 result in unnecessarily dropping fragment queues when normal
100 reordering of packets occurs, which could lead to poor application
101 performance. Using a very large value, e.g. 50000, increases the
102 likelihood of incorrectly reassembling IP fragments that originate
103 from different IP datagrams, which could result in data corruption.
104 Default: 64
105
106 INET peer storage:
107
108 inet_peer_threshold - INTEGER
109 The approximate size of the storage. Starting from this threshold
110 entries will be thrown aggressively. This threshold also determines
111 entries' time-to-live and time intervals between garbage collection
112 passes. More entries, less time-to-live, less GC interval.
113
114 inet_peer_minttl - INTEGER
115 Minimum time-to-live of entries. Should be enough to cover fragment
116 time-to-live on the reassembling side. This minimum time-to-live is
117 guaranteed if the pool size is less than inet_peer_threshold.
118 Measured in seconds.
119
120 inet_peer_maxttl - INTEGER
121 Maximum time-to-live of entries. Unused entries will expire after
122 this period of time if there is no memory pressure on the pool (i.e.
123 when the number of entries in the pool is very small).
124 Measured in seconds.
125
126 TCP variables:
127
128 somaxconn - INTEGER
129 Limit of socket listen() backlog, known in userspace as SOMAXCONN.
130 Defaults to 128. See also tcp_max_syn_backlog for additional tuning
131 for TCP sockets.
132
133 tcp_abort_on_overflow - BOOLEAN
134 If listening service is too slow to accept new connections,
135 reset them. Default state is FALSE. It means that if overflow
136 occurred due to a burst, connection will recover. Enable this
137 option _only_ if you are really sure that listening daemon
138 cannot be tuned to accept connections faster. Enabling this
139 option can harm clients of your server.
140
141 tcp_adv_win_scale - INTEGER
142 Count buffering overhead as bytes/2^tcp_adv_win_scale
143 (if tcp_adv_win_scale > 0) or bytes-bytes/2^(-tcp_adv_win_scale),
144 if it is <= 0.
145 Possible values are [-31, 31], inclusive.
146 Default: 1
147
148 tcp_allowed_congestion_control - STRING
149 Show/set the congestion control choices available to non-privileged
150 processes. The list is a subset of those listed in
151 tcp_available_congestion_control.
152 Default is "reno" and the default setting (tcp_congestion_control).
153
154 tcp_app_win - INTEGER
155 Reserve max(window/2^tcp_app_win, mss) of window for application
156 buffer. Value 0 is special, it means that nothing is reserved.
157 Default: 31
158
159 tcp_available_congestion_control - STRING
160 Shows the available congestion control choices that are registered.
161 More congestion control algorithms may be available as modules,
162 but not loaded.
163
164 tcp_base_mss - INTEGER
165 The initial value of search_low to be used by the packetization layer
166 Path MTU discovery (MTU probing). If MTU probing is enabled,
167 this is the initial MSS used by the connection.
168
169 tcp_congestion_control - STRING
170 Set the congestion control algorithm to be used for new
171 connections. The algorithm "reno" is always available, but
172 additional choices may be available based on kernel configuration.
173 Default is set as part of kernel configuration.
174 For passive connections, the listener congestion control choice
175 is inherited.
176 [see setsockopt(listenfd, SOL_TCP, TCP_CONGESTION, "name" ...) ]
177
178 tcp_dsack - BOOLEAN
179 Allows TCP to send "duplicate" SACKs.
180
181 tcp_early_retrans - INTEGER
182 Enable Early Retransmit (ER), per RFC 5827. ER lowers the threshold
183 for triggering fast retransmit when the amount of outstanding data is
184 small and when no previously unsent data can be transmitted (such
185 that limited transmit could be used). Also controls the use of
186 Tail loss probe (TLP) that converts RTOs occurring due to tail
187 losses into fast recovery (draft-dukkipati-tcpm-tcp-loss-probe-01).
188 Possible values:
189 0 disables ER
190 1 enables ER
191 2 enables ER but delays fast recovery and fast retransmit
192 by a fourth of RTT. This mitigates connection falsely
193 recovers when network has a small degree of reordering
194 (less than 3 packets).
195 3 enables delayed ER and TLP.
196 4 enables TLP only.
197 Default: 3
198
199 tcp_ecn - INTEGER
200 Control use of Explicit Congestion Notification (ECN) by TCP.
201 ECN is used only when both ends of the TCP connection indicate
202 support for it. This feature is useful in avoiding losses due
203 to congestion by allowing supporting routers to signal
204 congestion before having to drop packets.
205 Possible values are:
206 0 Disable ECN. Neither initiate nor accept ECN.
207 1 Enable ECN when requested by incoming connections and
208 also request ECN on outgoing connection attempts.
209 2 Enable ECN when requested by incoming connections
210 but do not request ECN on outgoing connections.
211 Default: 2
212
213 tcp_fack - BOOLEAN
214 Enable FACK congestion avoidance and fast retransmission.
215 The value is not used, if tcp_sack is not enabled.
216
217 tcp_fin_timeout - INTEGER
218 The length of time an orphaned (no longer referenced by any
219 application) connection will remain in the FIN_WAIT_2 state
220 before it is aborted at the local end. While a perfectly
221 valid "receive only" state for an un-orphaned connection, an
222 orphaned connection in FIN_WAIT_2 state could otherwise wait
223 forever for the remote to close its end of the connection.
224 Cf. tcp_max_orphans
225 Default: 60 seconds
226
227 tcp_frto - INTEGER
228 Enables Forward RTO-Recovery (F-RTO) defined in RFC5682.
229 F-RTO is an enhanced recovery algorithm for TCP retransmission
230 timeouts. It is particularly beneficial in networks where the
231 RTT fluctuates (e.g., wireless). F-RTO is sender-side only
232 modification. It does not require any support from the peer.
233
234 By default it's enabled with a non-zero value. 0 disables F-RTO.
235
236 tcp_keepalive_time - INTEGER
237 How often TCP sends out keepalive messages when keepalive is enabled.
238 Default: 2hours.
239
240 tcp_keepalive_probes - INTEGER
241 How many keepalive probes TCP sends out, until it decides that the
242 connection is broken. Default value: 9.
243
244 tcp_keepalive_intvl - INTEGER
245 How frequently the probes are send out. Multiplied by
246 tcp_keepalive_probes it is time to kill not responding connection,
247 after probes started. Default value: 75sec i.e. connection
248 will be aborted after ~11 minutes of retries.
249
250 tcp_low_latency - BOOLEAN
251 If set, the TCP stack makes decisions that prefer lower
252 latency as opposed to higher throughput. By default, this
253 option is not set meaning that higher throughput is preferred.
254 An example of an application where this default should be
255 changed would be a Beowulf compute cluster.
256 Default: 0
257
258 tcp_max_orphans - INTEGER
259 Maximal number of TCP sockets not attached to any user file handle,
260 held by system. If this number is exceeded orphaned connections are
261 reset immediately and warning is printed. This limit exists
262 only to prevent simple DoS attacks, you _must_ not rely on this
263 or lower the limit artificially, but rather increase it
264 (probably, after increasing installed memory),
265 if network conditions require more than default value,
266 and tune network services to linger and kill such states
267 more aggressively. Let me to remind again: each orphan eats
268 up to ~64K of unswappable memory.
269
270 tcp_max_ssthresh - INTEGER
271 Limited Slow-Start for TCP with large congestion windows (cwnd) defined in
272 RFC3742. Limited slow-start is a mechanism to limit growth of the cwnd
273 on the region where cwnd is larger than tcp_max_ssthresh. TCP increases cwnd
274 by at most tcp_max_ssthresh segments, and by at least tcp_max_ssthresh/2
275 segments per RTT when the cwnd is above tcp_max_ssthresh.
276 If TCP connection increased cwnd to thousands (or tens of thousands) segments,
277 and thousands of packets were being dropped during slow-start, you can set
278 tcp_max_ssthresh to improve performance for new TCP connection.
279 Default: 0 (off)
280
281 tcp_max_syn_backlog - INTEGER
282 Maximal number of remembered connection requests, which have not
283 received an acknowledgment from connecting client.
284 The minimal value is 128 for low memory machines, and it will
285 increase in proportion to the memory of machine.
286 If server suffers from overload, try increasing this number.
287
288 tcp_max_tw_buckets - INTEGER
289 Maximal number of timewait sockets held by system simultaneously.
290 If this number is exceeded time-wait socket is immediately destroyed
291 and warning is printed. This limit exists only to prevent
292 simple DoS attacks, you _must_ not lower the limit artificially,
293 but rather increase it (probably, after increasing installed memory),
294 if network conditions require more than default value.
295
296 tcp_mem - vector of 3 INTEGERs: min, pressure, max
297 min: below this number of pages TCP is not bothered about its
298 memory appetite.
299
300 pressure: when amount of memory allocated by TCP exceeds this number
301 of pages, TCP moderates its memory consumption and enters memory
302 pressure mode, which is exited when memory consumption falls
303 under "min".
304
305 max: number of pages allowed for queueing by all TCP sockets.
306
307 Defaults are calculated at boot time from amount of available
308 memory.
309
310 tcp_moderate_rcvbuf - BOOLEAN
311 If set, TCP performs receive buffer auto-tuning, attempting to
312 automatically size the buffer (no greater than tcp_rmem[2]) to
313 match the size required by the path for full throughput. Enabled by
314 default.
315
316 tcp_mtu_probing - INTEGER
317 Controls TCP Packetization-Layer Path MTU Discovery. Takes three
318 values:
319 0 - Disabled
320 1 - Disabled by default, enabled when an ICMP black hole detected
321 2 - Always enabled, use initial MSS of tcp_base_mss.
322
323 tcp_no_metrics_save - BOOLEAN
324 By default, TCP saves various connection metrics in the route cache
325 when the connection closes, so that connections established in the
326 near future can use these to set initial conditions. Usually, this
327 increases overall performance, but may sometimes cause performance
328 degradation. If set, TCP will not cache metrics on closing
329 connections.
330
331 tcp_orphan_retries - INTEGER
332 This value influences the timeout of a locally closed TCP connection,
333 when RTO retransmissions remain unacknowledged.
334 See tcp_retries2 for more details.
335
336 The default value is 8.
337 If your machine is a loaded WEB server,
338 you should think about lowering this value, such sockets
339 may consume significant resources. Cf. tcp_max_orphans.
340
341 tcp_reordering - INTEGER
342 Maximal reordering of packets in a TCP stream.
343 Default: 3
344
345 tcp_retrans_collapse - BOOLEAN
346 Bug-to-bug compatibility with some broken printers.
347 On retransmit try to send bigger packets to work around bugs in
348 certain TCP stacks.
349
350 tcp_retries1 - INTEGER
351 This value influences the time, after which TCP decides, that
352 something is wrong due to unacknowledged RTO retransmissions,
353 and reports this suspicion to the network layer.
354 See tcp_retries2 for more details.
355
356 RFC 1122 recommends at least 3 retransmissions, which is the
357 default.
358
359 tcp_retries2 - INTEGER
360 This value influences the timeout of an alive TCP connection,
361 when RTO retransmissions remain unacknowledged.
362 Given a value of N, a hypothetical TCP connection following
363 exponential backoff with an initial RTO of TCP_RTO_MIN would
364 retransmit N times before killing the connection at the (N+1)th RTO.
365
366 The default value of 15 yields a hypothetical timeout of 924.6
367 seconds and is a lower bound for the effective timeout.
368 TCP will effectively time out at the first RTO which exceeds the
369 hypothetical timeout.
370
371 RFC 1122 recommends at least 100 seconds for the timeout,
372 which corresponds to a value of at least 8.
373
374 tcp_rfc1337 - BOOLEAN
375 If set, the TCP stack behaves conforming to RFC1337. If unset,
376 we are not conforming to RFC, but prevent TCP TIME_WAIT
377 assassination.
378 Default: 0
379
380 tcp_rmem - vector of 3 INTEGERs: min, default, max
381 min: Minimal size of receive buffer used by TCP sockets.
382 It is guaranteed to each TCP socket, even under moderate memory
383 pressure.
384 Default: 1 page
385
386 default: initial size of receive buffer used by TCP sockets.
387 This value overrides net.core.rmem_default used by other protocols.
388 Default: 87380 bytes. This value results in window of 65535 with
389 default setting of tcp_adv_win_scale and tcp_app_win:0 and a bit
390 less for default tcp_app_win. See below about these variables.
391
392 max: maximal size of receive buffer allowed for automatically
393 selected receiver buffers for TCP socket. This value does not override
394 net.core.rmem_max. Calling setsockopt() with SO_RCVBUF disables
395 automatic tuning of that socket's receive buffer size, in which
396 case this value is ignored.
397 Default: between 87380B and 6MB, depending on RAM size.
398
399 tcp_sack - BOOLEAN
400 Enable select acknowledgments (SACKS).
401
402 tcp_slow_start_after_idle - BOOLEAN
403 If set, provide RFC2861 behavior and time out the congestion
404 window after an idle period. An idle period is defined at
405 the current RTO. If unset, the congestion window will not
406 be timed out after an idle period.
407 Default: 1
408
409 tcp_stdurg - BOOLEAN
410 Use the Host requirements interpretation of the TCP urgent pointer field.
411 Most hosts use the older BSD interpretation, so if you turn this on
412 Linux might not communicate correctly with them.
413 Default: FALSE
414
415 tcp_synack_retries - INTEGER
416 Number of times SYNACKs for a passive TCP connection attempt will
417 be retransmitted. Should not be higher than 255. Default value
418 is 5, which corresponds to 31seconds till the last retransmission
419 with the current initial RTO of 1second. With this the final timeout
420 for a passive TCP connection will happen after 63seconds.
421
422 tcp_syncookies - BOOLEAN
423 Only valid when the kernel was compiled with CONFIG_SYN_COOKIES
424 Send out syncookies when the syn backlog queue of a socket
425 overflows. This is to prevent against the common 'SYN flood attack'
426 Default: 1
427
428 Note, that syncookies is fallback facility.
429 It MUST NOT be used to help highly loaded servers to stand
430 against legal connection rate. If you see SYN flood warnings
431 in your logs, but investigation shows that they occur
432 because of overload with legal connections, you should tune
433 another parameters until this warning disappear.
434 See: tcp_max_syn_backlog, tcp_synack_retries, tcp_abort_on_overflow.
435
436 syncookies seriously violate TCP protocol, do not allow
437 to use TCP extensions, can result in serious degradation
438 of some services (f.e. SMTP relaying), visible not by you,
439 but your clients and relays, contacting you. While you see
440 SYN flood warnings in logs not being really flooded, your server
441 is seriously misconfigured.
442
443 tcp_fastopen - INTEGER
444 Enable TCP Fast Open feature (draft-ietf-tcpm-fastopen) to send data
445 in the opening SYN packet. To use this feature, the client application
446 must use sendmsg() or sendto() with MSG_FASTOPEN flag rather than
447 connect() to perform a TCP handshake automatically.
448
449 The values (bitmap) are
450 1: Enables sending data in the opening SYN on the client.
451 2: Enables TCP Fast Open on the server side, i.e., allowing data in
452 a SYN packet to be accepted and passed to the application before
453 3-way hand shake finishes.
454 4: Send data in the opening SYN regardless of cookie availability and
455 without a cookie option.
456 0x100: Accept SYN data w/o validating the cookie.
457 0x200: Accept data-in-SYN w/o any cookie option present.
458 0x400/0x800: Enable Fast Open on all listeners regardless of the
459 TCP_FASTOPEN socket option. The two different flags designate two
460 different ways of setting max_qlen without the TCP_FASTOPEN socket
461 option.
462
463 Default: 0
464
465 Note that the client & server side Fast Open flags (1 and 2
466 respectively) must be also enabled before the rest of flags can take
467 effect.
468
469 See include/net/tcp.h and the code for more details.
470
471 tcp_syn_retries - INTEGER
472 Number of times initial SYNs for an active TCP connection attempt
473 will be retransmitted. Should not be higher than 255. Default value
474 is 6, which corresponds to 63seconds till the last retransmission
475 with the current initial RTO of 1second. With this the final timeout
476 for an active TCP connection attempt will happen after 127seconds.
477
478 tcp_timestamps - BOOLEAN
479 Enable timestamps as defined in RFC1323.
480
481 tcp_tso_win_divisor - INTEGER
482 This allows control over what percentage of the congestion window
483 can be consumed by a single TSO frame.
484 The setting of this parameter is a choice between burstiness and
485 building larger TSO frames.
486 Default: 3
487
488 tcp_tw_recycle - BOOLEAN
489 Enable fast recycling TIME-WAIT sockets. Default value is 0.
490 It should not be changed without advice/request of technical
491 experts.
492
493 tcp_tw_reuse - BOOLEAN
494 Allow to reuse TIME-WAIT sockets for new connections when it is
495 safe from protocol viewpoint. Default value is 0.
496 It should not be changed without advice/request of technical
497 experts.
498
499 tcp_window_scaling - BOOLEAN
500 Enable window scaling as defined in RFC1323.
501
502 tcp_wmem - vector of 3 INTEGERs: min, default, max
503 min: Amount of memory reserved for send buffers for TCP sockets.
504 Each TCP socket has rights to use it due to fact of its birth.
505 Default: 1 page
506
507 default: initial size of send buffer used by TCP sockets. This
508 value overrides net.core.wmem_default used by other protocols.
509 It is usually lower than net.core.wmem_default.
510 Default: 16K
511
512 max: Maximal amount of memory allowed for automatically tuned
513 send buffers for TCP sockets. This value does not override
514 net.core.wmem_max. Calling setsockopt() with SO_SNDBUF disables
515 automatic tuning of that socket's send buffer size, in which case
516 this value is ignored.
517 Default: between 64K and 4MB, depending on RAM size.
518
519 tcp_notsent_lowat - UNSIGNED INTEGER
520 A TCP socket can control the amount of unsent bytes in its write queue,
521 thanks to TCP_NOTSENT_LOWAT socket option. poll()/select()/epoll()
522 reports POLLOUT events if the amount of unsent bytes is below a per
523 socket value, and if the write queue is not full. sendmsg() will
524 also not add new buffers if the limit is hit.
525
526 This global variable controls the amount of unsent data for
527 sockets not using TCP_NOTSENT_LOWAT. For these sockets, a change
528 to the global variable has immediate effect.
529
530 Default: UINT_MAX (0xFFFFFFFF)
531
532 tcp_workaround_signed_windows - BOOLEAN
533 If set, assume no receipt of a window scaling option means the
534 remote TCP is broken and treats the window as a signed quantity.
535 If unset, assume the remote TCP is not broken even if we do
536 not receive a window scaling option from them.
537 Default: 0
538
539 tcp_dma_copybreak - INTEGER
540 Lower limit, in bytes, of the size of socket reads that will be
541 offloaded to a DMA copy engine, if one is present in the system
542 and CONFIG_NET_DMA is enabled.
543 Default: 4096
544
545 tcp_thin_linear_timeouts - BOOLEAN
546 Enable dynamic triggering of linear timeouts for thin streams.
547 If set, a check is performed upon retransmission by timeout to
548 determine if the stream is thin (less than 4 packets in flight).
549 As long as the stream is found to be thin, up to 6 linear
550 timeouts may be performed before exponential backoff mode is
551 initiated. This improves retransmission latency for
552 non-aggressive thin streams, often found to be time-dependent.
553 For more information on thin streams, see
554 Documentation/networking/tcp-thin.txt
555 Default: 0
556
557 tcp_thin_dupack - BOOLEAN
558 Enable dynamic triggering of retransmissions after one dupACK
559 for thin streams. If set, a check is performed upon reception
560 of a dupACK to determine if the stream is thin (less than 4
561 packets in flight). As long as the stream is found to be thin,
562 data is retransmitted on the first received dupACK. This
563 improves retransmission latency for non-aggressive thin
564 streams, often found to be time-dependent.
565 For more information on thin streams, see
566 Documentation/networking/tcp-thin.txt
567 Default: 0
568
569 tcp_limit_output_bytes - INTEGER
570 Controls TCP Small Queue limit per tcp socket.
571 TCP bulk sender tends to increase packets in flight until it
572 gets losses notifications. With SNDBUF autotuning, this can
573 result in a large amount of packets queued in qdisc/device
574 on the local machine, hurting latency of other flows, for
575 typical pfifo_fast qdiscs.
576 tcp_limit_output_bytes limits the number of bytes on qdisc
577 or device to reduce artificial RTT/cwnd and reduce bufferbloat.
578 Note: For GSO/TSO enabled flows, we try to have at least two
579 packets in flight. Reducing tcp_limit_output_bytes might also
580 reduce the size of individual GSO packet (64KB being the max)
581 Default: 131072
582
583 tcp_challenge_ack_limit - INTEGER
584 Limits number of Challenge ACK sent per second, as recommended
585 in RFC 5961 (Improving TCP's Robustness to Blind In-Window Attacks)
586 Default: 100
587
588 UDP variables:
589
590 udp_mem - vector of 3 INTEGERs: min, pressure, max
591 Number of pages allowed for queueing by all UDP sockets.
592
593 min: Below this number of pages UDP is not bothered about its
594 memory appetite. When amount of memory allocated by UDP exceeds
595 this number, UDP starts to moderate memory usage.
596
597 pressure: This value was introduced to follow format of tcp_mem.
598
599 max: Number of pages allowed for queueing by all UDP sockets.
600
601 Default is calculated at boot time from amount of available memory.
602
603 udp_rmem_min - INTEGER
604 Minimal size of receive buffer used by UDP sockets in moderation.
605 Each UDP socket is able to use the size for receiving data, even if
606 total pages of UDP sockets exceed udp_mem pressure. The unit is byte.
607 Default: 1 page
608
609 udp_wmem_min - INTEGER
610 Minimal size of send buffer used by UDP sockets in moderation.
611 Each UDP socket is able to use the size for sending data, even if
612 total pages of UDP sockets exceed udp_mem pressure. The unit is byte.
613 Default: 1 page
614
615 CIPSOv4 Variables:
616
617 cipso_cache_enable - BOOLEAN
618 If set, enable additions to and lookups from the CIPSO label mapping
619 cache. If unset, additions are ignored and lookups always result in a
620 miss. However, regardless of the setting the cache is still
621 invalidated when required when means you can safely toggle this on and
622 off and the cache will always be "safe".
623 Default: 1
624
625 cipso_cache_bucket_size - INTEGER
626 The CIPSO label cache consists of a fixed size hash table with each
627 hash bucket containing a number of cache entries. This variable limits
628 the number of entries in each hash bucket; the larger the value the
629 more CIPSO label mappings that can be cached. When the number of
630 entries in a given hash bucket reaches this limit adding new entries
631 causes the oldest entry in the bucket to be removed to make room.
632 Default: 10
633
634 cipso_rbm_optfmt - BOOLEAN
635 Enable the "Optimized Tag 1 Format" as defined in section 3.4.2.6 of
636 the CIPSO draft specification (see Documentation/netlabel for details).
637 This means that when set the CIPSO tag will be padded with empty
638 categories in order to make the packet data 32-bit aligned.
639 Default: 0
640
641 cipso_rbm_structvalid - BOOLEAN
642 If set, do a very strict check of the CIPSO option when
643 ip_options_compile() is called. If unset, relax the checks done during
644 ip_options_compile(). Either way is "safe" as errors are caught else
645 where in the CIPSO processing code but setting this to 0 (False) should
646 result in less work (i.e. it should be faster) but could cause problems
647 with other implementations that require strict checking.
648 Default: 0
649
650 IP Variables:
651
652 ip_local_port_range - 2 INTEGERS
653 Defines the local port range that is used by TCP and UDP to
654 choose the local port. The first number is the first, the
655 second the last local port number. The default values are
656 32768 and 61000 respectively.
657
658 ip_local_reserved_ports - list of comma separated ranges
659 Specify the ports which are reserved for known third-party
660 applications. These ports will not be used by automatic port
661 assignments (e.g. when calling connect() or bind() with port
662 number 0). Explicit port allocation behavior is unchanged.
663
664 The format used for both input and output is a comma separated
665 list of ranges (e.g. "1,2-4,10-10" for ports 1, 2, 3, 4 and
666 10). Writing to the file will clear all previously reserved
667 ports and update the current list with the one given in the
668 input.
669
670 Note that ip_local_port_range and ip_local_reserved_ports
671 settings are independent and both are considered by the kernel
672 when determining which ports are available for automatic port
673 assignments.
674
675 You can reserve ports which are not in the current
676 ip_local_port_range, e.g.:
677
678 $ cat /proc/sys/net/ipv4/ip_local_port_range
679 32000 61000
680 $ cat /proc/sys/net/ipv4/ip_local_reserved_ports
681 8080,9148
682
683 although this is redundant. However such a setting is useful
684 if later the port range is changed to a value that will
685 include the reserved ports.
686
687 Default: Empty
688
689 ip_nonlocal_bind - BOOLEAN
690 If set, allows processes to bind() to non-local IP addresses,
691 which can be quite useful - but may break some applications.
692 Default: 0
693
694 ip_dynaddr - BOOLEAN
695 If set non-zero, enables support for dynamic addresses.
696 If set to a non-zero value larger than 1, a kernel log
697 message will be printed when dynamic address rewriting
698 occurs.
699 Default: 0
700
701 ip_early_demux - BOOLEAN
702 Optimize input packet processing down to one demux for
703 certain kinds of local sockets. Currently we only do this
704 for established TCP sockets.
705
706 It may add an additional cost for pure routing workloads that
707 reduces overall throughput, in such case you should disable it.
708 Default: 1
709
710 icmp_echo_ignore_all - BOOLEAN
711 If set non-zero, then the kernel will ignore all ICMP ECHO
712 requests sent to it.
713 Default: 0
714
715 icmp_echo_ignore_broadcasts - BOOLEAN
716 If set non-zero, then the kernel will ignore all ICMP ECHO and
717 TIMESTAMP requests sent to it via broadcast/multicast.
718 Default: 1
719
720 icmp_ratelimit - INTEGER
721 Limit the maximal rates for sending ICMP packets whose type matches
722 icmp_ratemask (see below) to specific targets.
723 0 to disable any limiting,
724 otherwise the minimal space between responses in milliseconds.
725 Default: 1000
726
727 icmp_ratemask - INTEGER
728 Mask made of ICMP types for which rates are being limited.
729 Significant bits: IHGFEDCBA9876543210
730 Default mask: 0000001100000011000 (6168)
731
732 Bit definitions (see include/linux/icmp.h):
733 0 Echo Reply
734 3 Destination Unreachable *
735 4 Source Quench *
736 5 Redirect
737 8 Echo Request
738 B Time Exceeded *
739 C Parameter Problem *
740 D Timestamp Request
741 E Timestamp Reply
742 F Info Request
743 G Info Reply
744 H Address Mask Request
745 I Address Mask Reply
746
747 * These are rate limited by default (see default mask above)
748
749 icmp_ignore_bogus_error_responses - BOOLEAN
750 Some routers violate RFC1122 by sending bogus responses to broadcast
751 frames. Such violations are normally logged via a kernel warning.
752 If this is set to TRUE, the kernel will not give such warnings, which
753 will avoid log file clutter.
754 Default: 1
755
756 icmp_errors_use_inbound_ifaddr - BOOLEAN
757
758 If zero, icmp error messages are sent with the primary address of
759 the exiting interface.
760
761 If non-zero, the message will be sent with the primary address of
762 the interface that received the packet that caused the icmp error.
763 This is the behaviour network many administrators will expect from
764 a router. And it can make debugging complicated network layouts
765 much easier.
766
767 Note that if no primary address exists for the interface selected,
768 then the primary address of the first non-loopback interface that
769 has one will be used regardless of this setting.
770
771 Default: 0
772
773 igmp_max_memberships - INTEGER
774 Change the maximum number of multicast groups we can subscribe to.
775 Default: 20
776
777 Theoretical maximum value is bounded by having to send a membership
778 report in a single datagram (i.e. the report can't span multiple
779 datagrams, or risk confusing the switch and leaving groups you don't
780 intend to).
781
782 The number of supported groups 'M' is bounded by the number of group
783 report entries you can fit into a single datagram of 65535 bytes.
784
785 M = 65536-sizeof (ip header)/(sizeof(Group record))
786
787 Group records are variable length, with a minimum of 12 bytes.
788 So net.ipv4.igmp_max_memberships should not be set higher than:
789
790 (65536-24) / 12 = 5459
791
792 The value 5459 assumes no IP header options, so in practice
793 this number may be lower.
794
795 conf/interface/* changes special settings per interface (where
796 "interface" is the name of your network interface)
797
798 conf/all/* is special, changes the settings for all interfaces
799
800 log_martians - BOOLEAN
801 Log packets with impossible addresses to kernel log.
802 log_martians for the interface will be enabled if at least one of
803 conf/{all,interface}/log_martians is set to TRUE,
804 it will be disabled otherwise
805
806 accept_redirects - BOOLEAN
807 Accept ICMP redirect messages.
808 accept_redirects for the interface will be enabled if:
809 - both conf/{all,interface}/accept_redirects are TRUE in the case
810 forwarding for the interface is enabled
811 or
812 - at least one of conf/{all,interface}/accept_redirects is TRUE in the
813 case forwarding for the interface is disabled
814 accept_redirects for the interface will be disabled otherwise
815 default TRUE (host)
816 FALSE (router)
817
818 forwarding - BOOLEAN
819 Enable IP forwarding on this interface.
820
821 mc_forwarding - BOOLEAN
822 Do multicast routing. The kernel needs to be compiled with CONFIG_MROUTE
823 and a multicast routing daemon is required.
824 conf/all/mc_forwarding must also be set to TRUE to enable multicast
825 routing for the interface
826
827 medium_id - INTEGER
828 Integer value used to differentiate the devices by the medium they
829 are attached to. Two devices can have different id values when
830 the broadcast packets are received only on one of them.
831 The default value 0 means that the device is the only interface
832 to its medium, value of -1 means that medium is not known.
833
834 Currently, it is used to change the proxy_arp behavior:
835 the proxy_arp feature is enabled for packets forwarded between
836 two devices attached to different media.
837
838 proxy_arp - BOOLEAN
839 Do proxy arp.
840 proxy_arp for the interface will be enabled if at least one of
841 conf/{all,interface}/proxy_arp is set to TRUE,
842 it will be disabled otherwise
843
844 proxy_arp_pvlan - BOOLEAN
845 Private VLAN proxy arp.
846 Basically allow proxy arp replies back to the same interface
847 (from which the ARP request/solicitation was received).
848
849 This is done to support (ethernet) switch features, like RFC
850 3069, where the individual ports are NOT allowed to
851 communicate with each other, but they are allowed to talk to
852 the upstream router. As described in RFC 3069, it is possible
853 to allow these hosts to communicate through the upstream
854 router by proxy_arp'ing. Don't need to be used together with
855 proxy_arp.
856
857 This technology is known by different names:
858 In RFC 3069 it is called VLAN Aggregation.
859 Cisco and Allied Telesyn call it Private VLAN.
860 Hewlett-Packard call it Source-Port filtering or port-isolation.
861 Ericsson call it MAC-Forced Forwarding (RFC Draft).
862
863 shared_media - BOOLEAN
864 Send(router) or accept(host) RFC1620 shared media redirects.
865 Overrides ip_secure_redirects.
866 shared_media for the interface will be enabled if at least one of
867 conf/{all,interface}/shared_media is set to TRUE,
868 it will be disabled otherwise
869 default TRUE
870
871 secure_redirects - BOOLEAN
872 Accept ICMP redirect messages only for gateways,
873 listed in default gateway list.
874 secure_redirects for the interface will be enabled if at least one of
875 conf/{all,interface}/secure_redirects is set to TRUE,
876 it will be disabled otherwise
877 default TRUE
878
879 send_redirects - BOOLEAN
880 Send redirects, if router.
881 send_redirects for the interface will be enabled if at least one of
882 conf/{all,interface}/send_redirects is set to TRUE,
883 it will be disabled otherwise
884 Default: TRUE
885
886 bootp_relay - BOOLEAN
887 Accept packets with source address 0.b.c.d destined
888 not to this host as local ones. It is supposed, that
889 BOOTP relay daemon will catch and forward such packets.
890 conf/all/bootp_relay must also be set to TRUE to enable BOOTP relay
891 for the interface
892 default FALSE
893 Not Implemented Yet.
894
895 accept_source_route - BOOLEAN
896 Accept packets with SRR option.
897 conf/all/accept_source_route must also be set to TRUE to accept packets
898 with SRR option on the interface
899 default TRUE (router)
900 FALSE (host)
901
902 accept_local - BOOLEAN
903 Accept packets with local source addresses. In combination
904 with suitable routing, this can be used to direct packets
905 between two local interfaces over the wire and have them
906 accepted properly.
907
908 rp_filter must be set to a non-zero value in order for
909 accept_local to have an effect.
910
911 default FALSE
912
913 route_localnet - BOOLEAN
914 Do not consider loopback addresses as martian source or destination
915 while routing. This enables the use of 127/8 for local routing purposes.
916 default FALSE
917
918 rp_filter - INTEGER
919 0 - No source validation.
920 1 - Strict mode as defined in RFC3704 Strict Reverse Path
921 Each incoming packet is tested against the FIB and if the interface
922 is not the best reverse path the packet check will fail.
923 By default failed packets are discarded.
924 2 - Loose mode as defined in RFC3704 Loose Reverse Path
925 Each incoming packet's source address is also tested against the FIB
926 and if the source address is not reachable via any interface
927 the packet check will fail.
928
929 Current recommended practice in RFC3704 is to enable strict mode
930 to prevent IP spoofing from DDos attacks. If using asymmetric routing
931 or other complicated routing, then loose mode is recommended.
932
933 The max value from conf/{all,interface}/rp_filter is used
934 when doing source validation on the {interface}.
935
936 Default value is 0. Note that some distributions enable it
937 in startup scripts.
938
939 arp_filter - BOOLEAN
940 1 - Allows you to have multiple network interfaces on the same
941 subnet, and have the ARPs for each interface be answered
942 based on whether or not the kernel would route a packet from
943 the ARP'd IP out that interface (therefore you must use source
944 based routing for this to work). In other words it allows control
945 of which cards (usually 1) will respond to an arp request.
946
947 0 - (default) The kernel can respond to arp requests with addresses
948 from other interfaces. This may seem wrong but it usually makes
949 sense, because it increases the chance of successful communication.
950 IP addresses are owned by the complete host on Linux, not by
951 particular interfaces. Only for more complex setups like load-
952 balancing, does this behaviour cause problems.
953
954 arp_filter for the interface will be enabled if at least one of
955 conf/{all,interface}/arp_filter is set to TRUE,
956 it will be disabled otherwise
957
958 arp_announce - INTEGER
959 Define different restriction levels for announcing the local
960 source IP address from IP packets in ARP requests sent on
961 interface:
962 0 - (default) Use any local address, configured on any interface
963 1 - Try to avoid local addresses that are not in the target's
964 subnet for this interface. This mode is useful when target
965 hosts reachable via this interface require the source IP
966 address in ARP requests to be part of their logical network
967 configured on the receiving interface. When we generate the
968 request we will check all our subnets that include the
969 target IP and will preserve the source address if it is from
970 such subnet. If there is no such subnet we select source
971 address according to the rules for level 2.
972 2 - Always use the best local address for this target.
973 In this mode we ignore the source address in the IP packet
974 and try to select local address that we prefer for talks with
975 the target host. Such local address is selected by looking
976 for primary IP addresses on all our subnets on the outgoing
977 interface that include the target IP address. If no suitable
978 local address is found we select the first local address
979 we have on the outgoing interface or on all other interfaces,
980 with the hope we will receive reply for our request and
981 even sometimes no matter the source IP address we announce.
982
983 The max value from conf/{all,interface}/arp_announce is used.
984
985 Increasing the restriction level gives more chance for
986 receiving answer from the resolved target while decreasing
987 the level announces more valid sender's information.
988
989 arp_ignore - INTEGER
990 Define different modes for sending replies in response to
991 received ARP requests that resolve local target IP addresses:
992 0 - (default): reply for any local target IP address, configured
993 on any interface
994 1 - reply only if the target IP address is local address
995 configured on the incoming interface
996 2 - reply only if the target IP address is local address
997 configured on the incoming interface and both with the
998 sender's IP address are part from same subnet on this interface
999 3 - do not reply for local addresses configured with scope host,
1000 only resolutions for global and link addresses are replied
1001 4-7 - reserved
1002 8 - do not reply for all local addresses
1003
1004 The max value from conf/{all,interface}/arp_ignore is used
1005 when ARP request is received on the {interface}
1006
1007 arp_notify - BOOLEAN
1008 Define mode for notification of address and device changes.
1009 0 - (default): do nothing
1010 1 - Generate gratuitous arp requests when device is brought up
1011 or hardware address changes.
1012
1013 arp_accept - BOOLEAN
1014 Define behavior for gratuitous ARP frames who's IP is not
1015 already present in the ARP table:
1016 0 - don't create new entries in the ARP table
1017 1 - create new entries in the ARP table
1018
1019 Both replies and requests type gratuitous arp will trigger the
1020 ARP table to be updated, if this setting is on.
1021
1022 If the ARP table already contains the IP address of the
1023 gratuitous arp frame, the arp table will be updated regardless
1024 if this setting is on or off.
1025
1026
1027 app_solicit - INTEGER
1028 The maximum number of probes to send to the user space ARP daemon
1029 via netlink before dropping back to multicast probes (see
1030 mcast_solicit). Defaults to 0.
1031
1032 disable_policy - BOOLEAN
1033 Disable IPSEC policy (SPD) for this interface
1034
1035 disable_xfrm - BOOLEAN
1036 Disable IPSEC encryption on this interface, whatever the policy
1037
1038
1039
1040 tag - INTEGER
1041 Allows you to write a number, which can be used as required.
1042 Default value is 0.
1043
1044 Alexey Kuznetsov.
1045 kuznet@ms2.inr.ac.ru
1046
1047 Updated by:
1048 Andi Kleen
1049 ak@muc.de
1050 Nicolas Delon
1051 delon.nicolas@wanadoo.fr
1052
1053
1054
1055
1056 /proc/sys/net/ipv6/* Variables:
1057
1058 IPv6 has no global variables such as tcp_*. tcp_* settings under ipv4/ also
1059 apply to IPv6 [XXX?].
1060
1061 bindv6only - BOOLEAN
1062 Default value for IPV6_V6ONLY socket option,
1063 which restricts use of the IPv6 socket to IPv6 communication
1064 only.
1065 TRUE: disable IPv4-mapped address feature
1066 FALSE: enable IPv4-mapped address feature
1067
1068 Default: FALSE (as specified in RFC3493)
1069
1070 IPv6 Fragmentation:
1071
1072 ip6frag_high_thresh - INTEGER
1073 Maximum memory used to reassemble IPv6 fragments. When
1074 ip6frag_high_thresh bytes of memory is allocated for this purpose,
1075 the fragment handler will toss packets until ip6frag_low_thresh
1076 is reached.
1077
1078 ip6frag_low_thresh - INTEGER
1079 See ip6frag_high_thresh
1080
1081 ip6frag_time - INTEGER
1082 Time in seconds to keep an IPv6 fragment in memory.
1083
1084 ip6frag_secret_interval - INTEGER
1085 Regeneration interval (in seconds) of the hash secret (or lifetime
1086 for the hash secret) for IPv6 fragments.
1087 Default: 600
1088
1089 conf/default/*:
1090 Change the interface-specific default settings.
1091
1092
1093 conf/all/*:
1094 Change all the interface-specific settings.
1095
1096 [XXX: Other special features than forwarding?]
1097
1098 conf/all/forwarding - BOOLEAN
1099 Enable global IPv6 forwarding between all interfaces.
1100
1101 IPv4 and IPv6 work differently here; e.g. netfilter must be used
1102 to control which interfaces may forward packets and which not.
1103
1104 This also sets all interfaces' Host/Router setting
1105 'forwarding' to the specified value. See below for details.
1106
1107 This referred to as global forwarding.
1108
1109 proxy_ndp - BOOLEAN
1110 Do proxy ndp.
1111
1112 conf/interface/*:
1113 Change special settings per interface.
1114
1115 The functional behaviour for certain settings is different
1116 depending on whether local forwarding is enabled or not.
1117
1118 accept_ra - INTEGER
1119 Accept Router Advertisements; autoconfigure using them.
1120
1121 It also determines whether or not to transmit Router
1122 Solicitations. If and only if the functional setting is to
1123 accept Router Advertisements, Router Solicitations will be
1124 transmitted.
1125
1126 Possible values are:
1127 0 Do not accept Router Advertisements.
1128 1 Accept Router Advertisements if forwarding is disabled.
1129 2 Overrule forwarding behaviour. Accept Router Advertisements
1130 even if forwarding is enabled.
1131
1132 Functional default: enabled if local forwarding is disabled.
1133 disabled if local forwarding is enabled.
1134
1135 accept_ra_defrtr - BOOLEAN
1136 Learn default router in Router Advertisement.
1137
1138 Functional default: enabled if accept_ra is enabled.
1139 disabled if accept_ra is disabled.
1140
1141 accept_ra_pinfo - BOOLEAN
1142 Learn Prefix Information in Router Advertisement.
1143
1144 Functional default: enabled if accept_ra is enabled.
1145 disabled if accept_ra is disabled.
1146
1147 accept_ra_rt_info_max_plen - INTEGER
1148 Maximum prefix length of Route Information in RA.
1149
1150 Route Information w/ prefix larger than or equal to this
1151 variable shall be ignored.
1152
1153 Functional default: 0 if accept_ra_rtr_pref is enabled.
1154 -1 if accept_ra_rtr_pref is disabled.
1155
1156 accept_ra_rtr_pref - BOOLEAN
1157 Accept Router Preference in RA.
1158
1159 Functional default: enabled if accept_ra is enabled.
1160 disabled if accept_ra is disabled.
1161
1162 accept_redirects - BOOLEAN
1163 Accept Redirects.
1164
1165 Functional default: enabled if local forwarding is disabled.
1166 disabled if local forwarding is enabled.
1167
1168 accept_source_route - INTEGER
1169 Accept source routing (routing extension header).
1170
1171 >= 0: Accept only routing header type 2.
1172 < 0: Do not accept routing header.
1173
1174 Default: 0
1175
1176 autoconf - BOOLEAN
1177 Autoconfigure addresses using Prefix Information in Router
1178 Advertisements.
1179
1180 Functional default: enabled if accept_ra_pinfo is enabled.
1181 disabled if accept_ra_pinfo is disabled.
1182
1183 dad_transmits - INTEGER
1184 The amount of Duplicate Address Detection probes to send.
1185 Default: 1
1186
1187 forwarding - INTEGER
1188 Configure interface-specific Host/Router behaviour.
1189
1190 Note: It is recommended to have the same setting on all
1191 interfaces; mixed router/host scenarios are rather uncommon.
1192
1193 Possible values are:
1194 0 Forwarding disabled
1195 1 Forwarding enabled
1196
1197 FALSE (0):
1198
1199 By default, Host behaviour is assumed. This means:
1200
1201 1. IsRouter flag is not set in Neighbour Advertisements.
1202 2. If accept_ra is TRUE (default), transmit Router
1203 Solicitations.
1204 3. If accept_ra is TRUE (default), accept Router
1205 Advertisements (and do autoconfiguration).
1206 4. If accept_redirects is TRUE (default), accept Redirects.
1207
1208 TRUE (1):
1209
1210 If local forwarding is enabled, Router behaviour is assumed.
1211 This means exactly the reverse from the above:
1212
1213 1. IsRouter flag is set in Neighbour Advertisements.
1214 2. Router Solicitations are not sent unless accept_ra is 2.
1215 3. Router Advertisements are ignored unless accept_ra is 2.
1216 4. Redirects are ignored.
1217
1218 Default: 0 (disabled) if global forwarding is disabled (default),
1219 otherwise 1 (enabled).
1220
1221 hop_limit - INTEGER
1222 Default Hop Limit to set.
1223 Default: 64
1224
1225 mtu - INTEGER
1226 Default Maximum Transfer Unit
1227 Default: 1280 (IPv6 required minimum)
1228
1229 router_probe_interval - INTEGER
1230 Minimum interval (in seconds) between Router Probing described
1231 in RFC4191.
1232
1233 Default: 60
1234
1235 router_solicitation_delay - INTEGER
1236 Number of seconds to wait after interface is brought up
1237 before sending Router Solicitations.
1238 Default: 1
1239
1240 router_solicitation_interval - INTEGER
1241 Number of seconds to wait between Router Solicitations.
1242 Default: 4
1243
1244 router_solicitations - INTEGER
1245 Number of Router Solicitations to send until assuming no
1246 routers are present.
1247 Default: 3
1248
1249 use_tempaddr - INTEGER
1250 Preference for Privacy Extensions (RFC3041).
1251 <= 0 : disable Privacy Extensions
1252 == 1 : enable Privacy Extensions, but prefer public
1253 addresses over temporary addresses.
1254 > 1 : enable Privacy Extensions and prefer temporary
1255 addresses over public addresses.
1256 Default: 0 (for most devices)
1257 -1 (for point-to-point devices and loopback devices)
1258
1259 temp_valid_lft - INTEGER
1260 valid lifetime (in seconds) for temporary addresses.
1261 Default: 604800 (7 days)
1262
1263 temp_prefered_lft - INTEGER
1264 Preferred lifetime (in seconds) for temporary addresses.
1265 Default: 86400 (1 day)
1266
1267 max_desync_factor - INTEGER
1268 Maximum value for DESYNC_FACTOR, which is a random value
1269 that ensures that clients don't synchronize with each
1270 other and generate new addresses at exactly the same time.
1271 value is in seconds.
1272 Default: 600
1273
1274 regen_max_retry - INTEGER
1275 Number of attempts before give up attempting to generate
1276 valid temporary addresses.
1277 Default: 5
1278
1279 max_addresses - INTEGER
1280 Maximum number of autoconfigured addresses per interface. Setting
1281 to zero disables the limitation. It is not recommended to set this
1282 value too large (or to zero) because it would be an easy way to
1283 crash the kernel by allowing too many addresses to be created.
1284 Default: 16
1285
1286 disable_ipv6 - BOOLEAN
1287 Disable IPv6 operation. If accept_dad is set to 2, this value
1288 will be dynamically set to TRUE if DAD fails for the link-local
1289 address.
1290 Default: FALSE (enable IPv6 operation)
1291
1292 When this value is changed from 1 to 0 (IPv6 is being enabled),
1293 it will dynamically create a link-local address on the given
1294 interface and start Duplicate Address Detection, if necessary.
1295
1296 When this value is changed from 0 to 1 (IPv6 is being disabled),
1297 it will dynamically delete all address on the given interface.
1298
1299 accept_dad - INTEGER
1300 Whether to accept DAD (Duplicate Address Detection).
1301 0: Disable DAD
1302 1: Enable DAD (default)
1303 2: Enable DAD, and disable IPv6 operation if MAC-based duplicate
1304 link-local address has been found.
1305
1306 force_tllao - BOOLEAN
1307 Enable sending the target link-layer address option even when
1308 responding to a unicast neighbor solicitation.
1309 Default: FALSE
1310
1311 Quoting from RFC 2461, section 4.4, Target link-layer address:
1312
1313 "The option MUST be included for multicast solicitations in order to
1314 avoid infinite Neighbor Solicitation "recursion" when the peer node
1315 does not have a cache entry to return a Neighbor Advertisements
1316 message. When responding to unicast solicitations, the option can be
1317 omitted since the sender of the solicitation has the correct link-
1318 layer address; otherwise it would not have be able to send the unicast
1319 solicitation in the first place. However, including the link-layer
1320 address in this case adds little overhead and eliminates a potential
1321 race condition where the sender deletes the cached link-layer address
1322 prior to receiving a response to a previous solicitation."
1323
1324 ndisc_notify - BOOLEAN
1325 Define mode for notification of address and device changes.
1326 0 - (default): do nothing
1327 1 - Generate unsolicited neighbour advertisements when device is brought
1328 up or hardware address changes.
1329
1330 icmp/*:
1331 ratelimit - INTEGER
1332 Limit the maximal rates for sending ICMPv6 packets.
1333 0 to disable any limiting,
1334 otherwise the minimal space between responses in milliseconds.
1335 Default: 1000
1336
1337
1338 IPv6 Update by:
1339 Pekka Savola <pekkas@netcore.fi>
1340 YOSHIFUJI Hideaki / USAGI Project <yoshfuji@linux-ipv6.org>
1341
1342
1343 /proc/sys/net/bridge/* Variables:
1344
1345 bridge-nf-call-arptables - BOOLEAN
1346 1 : pass bridged ARP traffic to arptables' FORWARD chain.
1347 0 : disable this.
1348 Default: 1
1349
1350 bridge-nf-call-iptables - BOOLEAN
1351 1 : pass bridged IPv4 traffic to iptables' chains.
1352 0 : disable this.
1353 Default: 1
1354
1355 bridge-nf-call-ip6tables - BOOLEAN
1356 1 : pass bridged IPv6 traffic to ip6tables' chains.
1357 0 : disable this.
1358 Default: 1
1359
1360 bridge-nf-filter-vlan-tagged - BOOLEAN
1361 1 : pass bridged vlan-tagged ARP/IP/IPv6 traffic to {arp,ip,ip6}tables.
1362 0 : disable this.
1363 Default: 0
1364
1365 bridge-nf-filter-pppoe-tagged - BOOLEAN
1366 1 : pass bridged pppoe-tagged IP/IPv6 traffic to {ip,ip6}tables.
1367 0 : disable this.
1368 Default: 0
1369
1370 bridge-nf-pass-vlan-input-dev - BOOLEAN
1371 1: if bridge-nf-filter-vlan-tagged is enabled, try to find a vlan
1372 interface on the bridge and set the netfilter input device to the vlan.
1373 This allows use of e.g. "iptables -i br0.1" and makes the REDIRECT
1374 target work with vlan-on-top-of-bridge interfaces. When no matching
1375 vlan interface is found, or this switch is off, the input device is
1376 set to the bridge interface.
1377 0: disable bridge netfilter vlan interface lookup.
1378 Default: 0
1379
1380 proc/sys/net/sctp/* Variables:
1381
1382 addip_enable - BOOLEAN
1383 Enable or disable extension of Dynamic Address Reconfiguration
1384 (ADD-IP) functionality specified in RFC5061. This extension provides
1385 the ability to dynamically add and remove new addresses for the SCTP
1386 associations.
1387
1388 1: Enable extension.
1389
1390 0: Disable extension.
1391
1392 Default: 0
1393
1394 addip_noauth_enable - BOOLEAN
1395 Dynamic Address Reconfiguration (ADD-IP) requires the use of
1396 authentication to protect the operations of adding or removing new
1397 addresses. This requirement is mandated so that unauthorized hosts
1398 would not be able to hijack associations. However, older
1399 implementations may not have implemented this requirement while
1400 allowing the ADD-IP extension. For reasons of interoperability,
1401 we provide this variable to control the enforcement of the
1402 authentication requirement.
1403
1404 1: Allow ADD-IP extension to be used without authentication. This
1405 should only be set in a closed environment for interoperability
1406 with older implementations.
1407
1408 0: Enforce the authentication requirement
1409
1410 Default: 0
1411
1412 auth_enable - BOOLEAN
1413 Enable or disable Authenticated Chunks extension. This extension
1414 provides the ability to send and receive authenticated chunks and is
1415 required for secure operation of Dynamic Address Reconfiguration
1416 (ADD-IP) extension.
1417
1418 1: Enable this extension.
1419 0: Disable this extension.
1420
1421 Default: 0
1422
1423 prsctp_enable - BOOLEAN
1424 Enable or disable the Partial Reliability extension (RFC3758) which
1425 is used to notify peers that a given DATA should no longer be expected.
1426
1427 1: Enable extension
1428 0: Disable
1429
1430 Default: 1
1431
1432 max_burst - INTEGER
1433 The limit of the number of new packets that can be initially sent. It
1434 controls how bursty the generated traffic can be.
1435
1436 Default: 4
1437
1438 association_max_retrans - INTEGER
1439 Set the maximum number for retransmissions that an association can
1440 attempt deciding that the remote end is unreachable. If this value
1441 is exceeded, the association is terminated.
1442
1443 Default: 10
1444
1445 max_init_retransmits - INTEGER
1446 The maximum number of retransmissions of INIT and COOKIE-ECHO chunks
1447 that an association will attempt before declaring the destination
1448 unreachable and terminating.
1449
1450 Default: 8
1451
1452 path_max_retrans - INTEGER
1453 The maximum number of retransmissions that will be attempted on a given
1454 path. Once this threshold is exceeded, the path is considered
1455 unreachable, and new traffic will use a different path when the
1456 association is multihomed.
1457
1458 Default: 5
1459
1460 pf_retrans - INTEGER
1461 The number of retransmissions that will be attempted on a given path
1462 before traffic is redirected to an alternate transport (should one
1463 exist). Note this is distinct from path_max_retrans, as a path that
1464 passes the pf_retrans threshold can still be used. Its only
1465 deprioritized when a transmission path is selected by the stack. This
1466 setting is primarily used to enable fast failover mechanisms without
1467 having to reduce path_max_retrans to a very low value. See:
1468 http://www.ietf.org/id/draft-nishida-tsvwg-sctp-failover-05.txt
1469 for details. Note also that a value of pf_retrans > path_max_retrans
1470 disables this feature
1471
1472 Default: 0
1473
1474 rto_initial - INTEGER
1475 The initial round trip timeout value in milliseconds that will be used
1476 in calculating round trip times. This is the initial time interval
1477 for retransmissions.
1478
1479 Default: 3000
1480
1481 rto_max - INTEGER
1482 The maximum value (in milliseconds) of the round trip timeout. This
1483 is the largest time interval that can elapse between retransmissions.
1484
1485 Default: 60000
1486
1487 rto_min - INTEGER
1488 The minimum value (in milliseconds) of the round trip timeout. This
1489 is the smallest time interval the can elapse between retransmissions.
1490
1491 Default: 1000
1492
1493 hb_interval - INTEGER
1494 The interval (in milliseconds) between HEARTBEAT chunks. These chunks
1495 are sent at the specified interval on idle paths to probe the state of
1496 a given path between 2 associations.
1497
1498 Default: 30000
1499
1500 sack_timeout - INTEGER
1501 The amount of time (in milliseconds) that the implementation will wait
1502 to send a SACK.
1503
1504 Default: 200
1505
1506 valid_cookie_life - INTEGER
1507 The default lifetime of the SCTP cookie (in milliseconds). The cookie
1508 is used during association establishment.
1509
1510 Default: 60000
1511
1512 cookie_preserve_enable - BOOLEAN
1513 Enable or disable the ability to extend the lifetime of the SCTP cookie
1514 that is used during the establishment phase of SCTP association
1515
1516 1: Enable cookie lifetime extension.
1517 0: Disable
1518
1519 Default: 1
1520
1521 cookie_hmac_alg - STRING
1522 Select the hmac algorithm used when generating the cookie value sent by
1523 a listening sctp socket to a connecting client in the INIT-ACK chunk.
1524 Valid values are:
1525 * md5
1526 * sha1
1527 * none
1528 Ability to assign md5 or sha1 as the selected alg is predicated on the
1529 configuration of those algorithms at build time (CONFIG_CRYPTO_MD5 and
1530 CONFIG_CRYPTO_SHA1).
1531
1532 Default: Dependent on configuration. MD5 if available, else SHA1 if
1533 available, else none.
1534
1535 rcvbuf_policy - INTEGER
1536 Determines if the receive buffer is attributed to the socket or to
1537 association. SCTP supports the capability to create multiple
1538 associations on a single socket. When using this capability, it is
1539 possible that a single stalled association that's buffering a lot
1540 of data may block other associations from delivering their data by
1541 consuming all of the receive buffer space. To work around this,
1542 the rcvbuf_policy could be set to attribute the receiver buffer space
1543 to each association instead of the socket. This prevents the described
1544 blocking.
1545
1546 1: rcvbuf space is per association
1547 0: rcvbuf space is per socket
1548
1549 Default: 0
1550
1551 sndbuf_policy - INTEGER
1552 Similar to rcvbuf_policy above, this applies to send buffer space.
1553
1554 1: Send buffer is tracked per association
1555 0: Send buffer is tracked per socket.
1556
1557 Default: 0
1558
1559 sctp_mem - vector of 3 INTEGERs: min, pressure, max
1560 Number of pages allowed for queueing by all SCTP sockets.
1561
1562 min: Below this number of pages SCTP is not bothered about its
1563 memory appetite. When amount of memory allocated by SCTP exceeds
1564 this number, SCTP starts to moderate memory usage.
1565
1566 pressure: This value was introduced to follow format of tcp_mem.
1567
1568 max: Number of pages allowed for queueing by all SCTP sockets.
1569
1570 Default is calculated at boot time from amount of available memory.
1571
1572 sctp_rmem - vector of 3 INTEGERs: min, default, max
1573 Only the first value ("min") is used, "default" and "max" are
1574 ignored.
1575
1576 min: Minimal size of receive buffer used by SCTP socket.
1577 It is guaranteed to each SCTP socket (but not association) even
1578 under moderate memory pressure.
1579
1580 Default: 1 page
1581
1582 sctp_wmem - vector of 3 INTEGERs: min, default, max
1583 Currently this tunable has no effect.
1584
1585 addr_scope_policy - INTEGER
1586 Control IPv4 address scoping - draft-stewart-tsvwg-sctp-ipv4-00
1587
1588 0 - Disable IPv4 address scoping
1589 1 - Enable IPv4 address scoping
1590 2 - Follow draft but allow IPv4 private addresses
1591 3 - Follow draft but allow IPv4 link local addresses
1592
1593 Default: 1
1594
1595
1596 /proc/sys/net/core/*
1597 Please see: Documentation/sysctl/net.txt for descriptions of these entries.
1598
1599
1600 /proc/sys/net/unix/*
1601 max_dgram_qlen - INTEGER
1602 The maximum length of dgram socket receive queue
1603
1604 Default: 10
1605
1606
1607 UNDOCUMENTED:
1608
1609 /proc/sys/net/irda/*
1610 fast_poll_increase FIXME
1611 warn_noreply_time FIXME
1612 discovery_slots FIXME
1613 slot_timeout FIXME
1614 max_baud_rate FIXME
1615 discovery_timeout FIXME
1616 lap_keepalive_time FIXME
1617 max_noreply_time FIXME
1618 max_tx_data_size FIXME
1619 max_tx_window FIXME
1620 min_tx_turn_time FIXME
This page took 0.066428 seconds and 5 git commands to generate.