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