blob: c7a81ace35d08aa073392a7b4f62e822457ae571 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001/proc/sys/net/ipv4/* Variables:
2
3ip_forward - BOOLEAN
4 0 - disabled (default)
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +00005 not 0 - enabled
Linus Torvalds1da177e2005-04-16 15:20:36 -07006
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
13ip_default_ttl - INTEGER
Eric Dumazetcc6f02d2010-12-13 12:50:49 -080014 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)
Linus Torvalds1da177e2005-04-16 15:20:36 -070017
Hannes Frederic Sowacd174e62013-12-14 05:13:45 +010018ip_no_pmtu_disc - INTEGER
19 Disable Path MTU Discovery. If enabled in mode 1 and a
Hannes Frederic Sowa188b04d2013-12-14 04:42:13 +010020 fragmentation-required ICMP is received, the PMTU to this
21 destination will be set to min_pmtu (see below). You will need
22 to raise min_pmtu to the smallest interface MTU on your system
23 manually if you want to avoid locally generated fragments.
Hannes Frederic Sowacd174e62013-12-14 05:13:45 +010024
25 In mode 2 incoming Path MTU Discovery messages will be
26 discarded. Outgoing frames are handled the same as in mode 1,
27 implicitly setting IP_PMTUDISC_DONT on every created socket.
28
Hannes Frederic Sowa8ed1dc42014-01-09 10:01:17 +010029 Mode 3 is a hardend pmtu discover mode. The kernel will only
30 accept fragmentation-needed errors if the underlying protocol
31 can verify them besides a plain socket lookup. Current
32 protocols for which pmtu events will be honored are TCP, SCTP
33 and DCCP as they verify e.g. the sequence number or the
34 association. This mode should not be enabled globally but is
35 only intended to secure e.g. name servers in namespaces where
36 TCP path mtu must still work but path MTU information of other
37 protocols should be discarded. If enabled globally this mode
38 could break other protocols.
39
40 Possible values: 0-3
Hannes Frederic Sowa188b04d2013-12-14 04:42:13 +010041 Default: FALSE
Linus Torvalds1da177e2005-04-16 15:20:36 -070042
43min_pmtu - INTEGER
Eric Dumazet20db93c2011-11-08 14:21:44 -050044 default 552 - minimum discovered Path MTU
Linus Torvalds1da177e2005-04-16 15:20:36 -070045
Hannes Frederic Sowaf87c10a2014-01-09 10:01:15 +010046ip_forward_use_pmtu - BOOLEAN
47 By default we don't trust protocol path MTUs while forwarding
48 because they could be easily forged and can lead to unwanted
49 fragmentation by the router.
50 You only need to enable this if you have user-space software
51 which tries to discover path mtus by itself and depends on the
52 kernel honoring this information. This is normally not the
53 case.
54 Default: 0 (disabled)
55 Possible values:
56 0 - disabled
57 1 - enabled
58
Ben Greearcbaf0872010-11-08 09:13:48 +000059route/max_size - INTEGER
60 Maximum number of routes allowed in the kernel. Increase
61 this when using large numbers of interfaces and/or routes.
62
YOSHIFUJI Hideaki / 吉藤英明27246802013-01-22 05:20:05 +000063neigh/default/gc_thresh1 - INTEGER
64 Minimum number of entries to keep. Garbage collector will not
65 purge entries if there are fewer than this number.
Li RongQingb66c66d2013-03-14 22:49:47 +000066 Default: 128
YOSHIFUJI Hideaki / 吉藤英明27246802013-01-22 05:20:05 +000067
stephen hemmingera3d12142014-08-25 15:05:30 -070068neigh/default/gc_thresh2 - INTEGER
69 Threshold when garbage collector becomes more aggressive about
70 purging entries. Entries older than 5 seconds will be cleared
71 when over this number.
72 Default: 512
73
Ben Greearcbaf0872010-11-08 09:13:48 +000074neigh/default/gc_thresh3 - INTEGER
75 Maximum number of neighbor entries allowed. Increase this
76 when using large numbers of interfaces and when communicating
77 with large numbers of directly-connected peers.
Shan Weicc868022012-12-04 18:50:35 +000078 Default: 1024
Ben Greearcbaf0872010-11-08 09:13:48 +000079
Eric Dumazet8b5c1712011-11-09 12:07:14 +000080neigh/default/unres_qlen_bytes - INTEGER
81 The maximum number of bytes which may be used by packets
82 queued for each unresolved address by other network layers.
83 (added in linux 3.3)
stephen hemminger3b09adc2013-01-03 07:50:29 +000084 Setting negative value is meaningless and will return error.
Shan Weicc868022012-12-04 18:50:35 +000085 Default: 65536 Bytes(64KB)
Eric Dumazet8b5c1712011-11-09 12:07:14 +000086
87neigh/default/unres_qlen - INTEGER
88 The maximum number of packets which may be queued for each
89 unresolved address by other network layers.
90 (deprecated in linux 3.3) : use unres_qlen_bytes instead.
Shan Weicc868022012-12-04 18:50:35 +000091 Prior to linux 3.3, the default value is 3 which may cause
Shan Wei5d248c42012-12-06 16:27:51 +000092 unexpected packet loss. The current default value is calculated
Shan Weicc868022012-12-04 18:50:35 +000093 according to default value of unres_qlen_bytes and true size of
94 packet.
95 Default: 31
Eric Dumazet8b5c1712011-11-09 12:07:14 +000096
Linus Torvalds1da177e2005-04-16 15:20:36 -070097mtu_expires - INTEGER
98 Time, in seconds, that cached PMTU information is kept.
99
100min_adv_mss - INTEGER
101 The advertised MSS depends on the first hop route MTU, but will
102 never be lower than this setting.
103
104IP Fragmentation:
105
106ipfrag_high_thresh - INTEGER
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +0000107 Maximum memory used to reassemble IP fragments. When
Linus Torvalds1da177e2005-04-16 15:20:36 -0700108 ipfrag_high_thresh bytes of memory is allocated for this purpose,
109 the fragment handler will toss packets until ipfrag_low_thresh
Nikolay Aleksandrov1bab4c72014-07-24 16:50:37 +0200110 is reached. This also serves as a maximum limit to namespaces
111 different from the initial one.
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +0000112
Linus Torvalds1da177e2005-04-16 15:20:36 -0700113ipfrag_low_thresh - INTEGER
Florian Westphalb13d3cb2014-07-24 16:50:32 +0200114 Maximum memory used to reassemble IP fragments before the kernel
115 begins to remove incomplete fragment queues to free up resources.
116 The kernel still accepts new fragments for defragmentation.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700117
118ipfrag_time - INTEGER
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +0000119 Time in seconds to keep an IP fragment in memory.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700120
Herbert Xu89cee8b2005-12-13 23:14:27 -0800121ipfrag_max_dist - INTEGER
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +0000122 ipfrag_max_dist is a non-negative integer value which defines the
123 maximum "disorder" which is allowed among fragments which share a
124 common IP source address. Note that reordering of packets is
125 not unusual, but if a large number of fragments arrive from a source
126 IP address while a particular fragment queue remains incomplete, it
127 probably indicates that one or more fragments belonging to that queue
128 have been lost. When ipfrag_max_dist is positive, an additional check
129 is done on fragments before they are added to a reassembly queue - if
130 ipfrag_max_dist (or more) fragments have arrived from a particular IP
131 address between additions to any IP fragment queue using that source
132 address, it's presumed that one or more fragments in the queue are
133 lost. The existing fragment queue will be dropped, and a new one
Herbert Xu89cee8b2005-12-13 23:14:27 -0800134 started. An ipfrag_max_dist value of zero disables this check.
135
136 Using a very small value, e.g. 1 or 2, for ipfrag_max_dist can
137 result in unnecessarily dropping fragment queues when normal
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +0000138 reordering of packets occurs, which could lead to poor application
139 performance. Using a very large value, e.g. 50000, increases the
140 likelihood of incorrectly reassembling IP fragments that originate
Herbert Xu89cee8b2005-12-13 23:14:27 -0800141 from different IP datagrams, which could result in data corruption.
142 Default: 64
143
Linus Torvalds1da177e2005-04-16 15:20:36 -0700144INET peer storage:
145
146inet_peer_threshold - INTEGER
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +0000147 The approximate size of the storage. Starting from this threshold
Linus Torvalds1da177e2005-04-16 15:20:36 -0700148 entries will be thrown aggressively. This threshold also determines
149 entries' time-to-live and time intervals between garbage collection
150 passes. More entries, less time-to-live, less GC interval.
151
152inet_peer_minttl - INTEGER
153 Minimum time-to-live of entries. Should be enough to cover fragment
154 time-to-live on the reassembling side. This minimum time-to-live is
155 guaranteed if the pool size is less than inet_peer_threshold.
Stephen Hemminger77a538d2008-07-01 17:22:48 -0700156 Measured in seconds.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700157
158inet_peer_maxttl - INTEGER
159 Maximum time-to-live of entries. Unused entries will expire after
160 this period of time if there is no memory pressure on the pool (i.e.
161 when the number of entries in the pool is very small).
Stephen Hemminger77a538d2008-07-01 17:22:48 -0700162 Measured in seconds.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700163
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +0000164TCP variables:
Linus Torvalds1da177e2005-04-16 15:20:36 -0700165
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800166somaxconn - INTEGER
167 Limit of socket listen() backlog, known in userspace as SOMAXCONN.
168 Defaults to 128. See also tcp_max_syn_backlog for additional tuning
169 for TCP sockets.
170
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800171tcp_abort_on_overflow - BOOLEAN
172 If listening service is too slow to accept new connections,
173 reset them. Default state is FALSE. It means that if overflow
174 occurred due to a burst, connection will recover. Enable this
175 option _only_ if you are really sure that listening daemon
176 cannot be tuned to accept connections faster. Enabling this
177 option can harm clients of your server.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700178
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800179tcp_adv_win_scale - INTEGER
180 Count buffering overhead as bytes/2^tcp_adv_win_scale
181 (if tcp_adv_win_scale > 0) or bytes-bytes/2^(-tcp_adv_win_scale),
182 if it is <= 0.
Alexey Dobriyan0147fc02010-11-22 12:54:21 +0000183 Possible values are [-31, 31], inclusive.
Eric Dumazetb49960a2012-05-02 02:28:41 +0000184 Default: 1
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800185
186tcp_allowed_congestion_control - STRING
187 Show/set the congestion control choices available to non-privileged
188 processes. The list is a subset of those listed in
189 tcp_available_congestion_control.
190 Default is "reno" and the default setting (tcp_congestion_control).
191
192tcp_app_win - INTEGER
193 Reserve max(window/2^tcp_app_win, mss) of window for application
194 buffer. Value 0 is special, it means that nothing is reserved.
195 Default: 31
196
Eric Dumazetf54b3112013-12-05 22:36:05 -0800197tcp_autocorking - BOOLEAN
198 Enable TCP auto corking :
199 When applications do consecutive small write()/sendmsg() system calls,
200 we try to coalesce these small writes as much as possible, to lower
201 total amount of sent packets. This is done if at least one prior
202 packet for the flow is waiting in Qdisc queues or device transmit
203 queue. Applications can still use TCP_CORK for optimal behavior
204 when they know how/when to uncork their sockets.
205 Default : 1
206
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800207tcp_available_congestion_control - STRING
208 Shows the available congestion control choices that are registered.
209 More congestion control algorithms may be available as modules,
210 but not loaded.
211
John Heffner71599cd2007-02-27 10:03:56 -0800212tcp_base_mss - INTEGER
Stephen Hemminger4edc2f32008-07-10 16:50:26 -0700213 The initial value of search_low to be used by the packetization layer
214 Path MTU discovery (MTU probing). If MTU probing is enabled,
215 this is the initial MSS used by the connection.
John Heffner71599cd2007-02-27 10:03:56 -0800216
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800217tcp_congestion_control - STRING
218 Set the congestion control algorithm to be used for new
219 connections. The algorithm "reno" is always available, but
220 additional choices may be available based on kernel configuration.
221 Default is set as part of kernel configuration.
Eric Dumazetd8a6e652011-11-30 01:02:41 +0000222 For passive connections, the listener congestion control choice
223 is inherited.
224 [see setsockopt(listenfd, SOL_TCP, TCP_CONGESTION, "name" ...) ]
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800225
226tcp_dsack - BOOLEAN
227 Allows TCP to send "duplicate" SACKs.
228
Yuchung Chengeed530b2012-05-02 13:30:03 +0000229tcp_early_retrans - INTEGER
230 Enable Early Retransmit (ER), per RFC 5827. ER lowers the threshold
231 for triggering fast retransmit when the amount of outstanding data is
232 small and when no previously unsent data can be transmitted (such
Nandita Dukkipati6ba8a3b2013-03-11 10:00:43 +0000233 that limited transmit could be used). Also controls the use of
Masanari Iida3dd17ed2013-05-24 07:05:59 +0000234 Tail loss probe (TLP) that converts RTOs occurring due to tail
Nandita Dukkipati6ba8a3b2013-03-11 10:00:43 +0000235 losses into fast recovery (draft-dukkipati-tcpm-tcp-loss-probe-01).
Yuchung Chengeed530b2012-05-02 13:30:03 +0000236 Possible values:
237 0 disables ER
238 1 enables ER
239 2 enables ER but delays fast recovery and fast retransmit
240 by a fourth of RTT. This mitigates connection falsely
241 recovers when network has a small degree of reordering
242 (less than 3 packets).
Nandita Dukkipati6ba8a3b2013-03-11 10:00:43 +0000243 3 enables delayed ER and TLP.
244 4 enables TLP only.
245 Default: 3
Yuchung Chengeed530b2012-05-02 13:30:03 +0000246
Peter Chubb34a6ef32011-02-02 15:39:58 -0800247tcp_ecn - INTEGER
Rick Jones7e3a2dc2012-11-28 09:53:10 +0000248 Control use of Explicit Congestion Notification (ECN) by TCP.
249 ECN is used only when both ends of the TCP connection indicate
250 support for it. This feature is useful in avoiding losses due
251 to congestion by allowing supporting routers to signal
252 congestion before having to drop packets.
Ilpo Järvinen255cac92009-05-04 11:07:36 -0700253 Possible values are:
Rick Jones7e3a2dc2012-11-28 09:53:10 +0000254 0 Disable ECN. Neither initiate nor accept ECN.
Vijay Subramanian3d55b322013-01-09 12:21:30 +0000255 1 Enable ECN when requested by incoming connections and
256 also request ECN on outgoing connection attempts.
257 2 Enable ECN when requested by incoming connections
Rick Jones7e3a2dc2012-11-28 09:53:10 +0000258 but do not request ECN on outgoing connections.
Ilpo Järvinen255cac92009-05-04 11:07:36 -0700259 Default: 2
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800260
261tcp_fack - BOOLEAN
262 Enable FACK congestion avoidance and fast retransmission.
263 The value is not used, if tcp_sack is not enabled.
264
265tcp_fin_timeout - INTEGER
Rick Jonesd825da22012-12-10 11:33:00 +0000266 The length of time an orphaned (no longer referenced by any
267 application) connection will remain in the FIN_WAIT_2 state
268 before it is aborted at the local end. While a perfectly
269 valid "receive only" state for an un-orphaned connection, an
270 orphaned connection in FIN_WAIT_2 state could otherwise wait
271 forever for the remote to close its end of the connection.
272 Cf. tcp_max_orphans
273 Default: 60 seconds
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800274
Ilpo Järvinen89808062007-02-27 10:10:55 -0800275tcp_frto - INTEGER
Yuchung Chenge33099f2013-03-20 13:33:00 +0000276 Enables Forward RTO-Recovery (F-RTO) defined in RFC5682.
Ilpo Järvinencd998892007-09-20 11:35:26 -0700277 F-RTO is an enhanced recovery algorithm for TCP retransmission
Yuchung Chenge33099f2013-03-20 13:33:00 +0000278 timeouts. It is particularly beneficial in networks where the
279 RTT fluctuates (e.g., wireless). F-RTO is sender-side only
280 modification. It does not require any support from the peer.
Stephen Hemminger4edc2f32008-07-10 16:50:26 -0700281
Yuchung Chenge33099f2013-03-20 13:33:00 +0000282 By default it's enabled with a non-zero value. 0 disables F-RTO.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700283
284tcp_keepalive_time - INTEGER
285 How often TCP sends out keepalive messages when keepalive is enabled.
286 Default: 2hours.
287
288tcp_keepalive_probes - INTEGER
289 How many keepalive probes TCP sends out, until it decides that the
290 connection is broken. Default value: 9.
291
292tcp_keepalive_intvl - INTEGER
293 How frequently the probes are send out. Multiplied by
294 tcp_keepalive_probes it is time to kill not responding connection,
295 after probes started. Default value: 75sec i.e. connection
296 will be aborted after ~11 minutes of retries.
297
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800298tcp_low_latency - BOOLEAN
299 If set, the TCP stack makes decisions that prefer lower
300 latency as opposed to higher throughput. By default, this
301 option is not set meaning that higher throughput is preferred.
302 An example of an application where this default should be
303 changed would be a Beowulf compute cluster.
304 Default: 0
Linus Torvalds1da177e2005-04-16 15:20:36 -0700305
306tcp_max_orphans - INTEGER
307 Maximal number of TCP sockets not attached to any user file handle,
308 held by system. If this number is exceeded orphaned connections are
309 reset immediately and warning is printed. This limit exists
310 only to prevent simple DoS attacks, you _must_ not rely on this
311 or lower the limit artificially, but rather increase it
312 (probably, after increasing installed memory),
313 if network conditions require more than default value,
314 and tune network services to linger and kill such states
315 more aggressively. Let me to remind again: each orphan eats
316 up to ~64K of unswappable memory.
317
Linus Torvalds1da177e2005-04-16 15:20:36 -0700318tcp_max_syn_backlog - INTEGER
Peter Pan(潘卫平)99b53bd2011-12-05 21:39:41 +0000319 Maximal number of remembered connection requests, which have not
320 received an acknowledgment from connecting client.
321 The minimal value is 128 for low memory machines, and it will
322 increase in proportion to the memory of machine.
323 If server suffers from overload, try increasing this number.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700324
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800325tcp_max_tw_buckets - INTEGER
326 Maximal number of timewait sockets held by system simultaneously.
327 If this number is exceeded time-wait socket is immediately destroyed
328 and warning is printed. This limit exists only to prevent
329 simple DoS attacks, you _must_ not lower the limit artificially,
330 but rather increase it (probably, after increasing installed memory),
331 if network conditions require more than default value.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700332
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800333tcp_mem - vector of 3 INTEGERs: min, pressure, max
334 min: below this number of pages TCP is not bothered about its
335 memory appetite.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700336
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800337 pressure: when amount of memory allocated by TCP exceeds this number
338 of pages, TCP moderates its memory consumption and enters memory
339 pressure mode, which is exited when memory consumption falls
340 under "min".
Linus Torvalds1da177e2005-04-16 15:20:36 -0700341
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800342 max: number of pages allowed for queueing by all TCP sockets.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700343
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800344 Defaults are calculated at boot time from amount of available
345 memory.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700346
John Heffner71599cd2007-02-27 10:03:56 -0800347tcp_moderate_rcvbuf - BOOLEAN
Stephen Hemminger4edc2f32008-07-10 16:50:26 -0700348 If set, TCP performs receive buffer auto-tuning, attempting to
John Heffner71599cd2007-02-27 10:03:56 -0800349 automatically size the buffer (no greater than tcp_rmem[2]) to
350 match the size required by the path for full throughput. Enabled by
351 default.
352
353tcp_mtu_probing - INTEGER
354 Controls TCP Packetization-Layer Path MTU Discovery. Takes three
355 values:
356 0 - Disabled
357 1 - Disabled by default, enabled when an ICMP black hole detected
358 2 - Always enabled, use initial MSS of tcp_base_mss.
359
360tcp_no_metrics_save - BOOLEAN
361 By default, TCP saves various connection metrics in the route cache
362 when the connection closes, so that connections established in the
363 near future can use these to set initial conditions. Usually, this
364 increases overall performance, but may sometimes cause performance
Simon Arlott0f035b82007-10-20 01:30:25 +0200365 degradation. If set, TCP will not cache metrics on closing
John Heffner71599cd2007-02-27 10:03:56 -0800366 connections.
367
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800368tcp_orphan_retries - INTEGER
Damian Lukowski5d789222009-09-01 10:24:04 +0000369 This value influences the timeout of a locally closed TCP connection,
370 when RTO retransmissions remain unacknowledged.
371 See tcp_retries2 for more details.
372
David S. Miller06b8fc52011-07-08 09:31:31 -0700373 The default value is 8.
Damian Lukowski5d789222009-09-01 10:24:04 +0000374 If your machine is a loaded WEB server,
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800375 you should think about lowering this value, such sockets
376 may consume significant resources. Cf. tcp_max_orphans.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700377
378tcp_reordering - INTEGER
379 Maximal reordering of packets in a TCP stream.
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +0000380 Default: 3
Linus Torvalds1da177e2005-04-16 15:20:36 -0700381
382tcp_retrans_collapse - BOOLEAN
383 Bug-to-bug compatibility with some broken printers.
384 On retransmit try to send bigger packets to work around bugs in
385 certain TCP stacks.
386
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800387tcp_retries1 - INTEGER
Damian Lukowski5d789222009-09-01 10:24:04 +0000388 This value influences the time, after which TCP decides, that
389 something is wrong due to unacknowledged RTO retransmissions,
390 and reports this suspicion to the network layer.
391 See tcp_retries2 for more details.
392
393 RFC 1122 recommends at least 3 retransmissions, which is the
394 default.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700395
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800396tcp_retries2 - INTEGER
Damian Lukowski5d789222009-09-01 10:24:04 +0000397 This value influences the timeout of an alive TCP connection,
398 when RTO retransmissions remain unacknowledged.
399 Given a value of N, a hypothetical TCP connection following
400 exponential backoff with an initial RTO of TCP_RTO_MIN would
401 retransmit N times before killing the connection at the (N+1)th RTO.
402
403 The default value of 15 yields a hypothetical timeout of 924.6
404 seconds and is a lower bound for the effective timeout.
405 TCP will effectively time out at the first RTO which exceeds the
406 hypothetical timeout.
407
408 RFC 1122 recommends at least 100 seconds for the timeout,
409 which corresponds to a value of at least 8.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700410
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800411tcp_rfc1337 - BOOLEAN
412 If set, the TCP stack behaves conforming to RFC1337. If unset,
413 we are not conforming to RFC, but prevent TCP TIME_WAIT
414 assassination.
415 Default: 0
Linus Torvalds1da177e2005-04-16 15:20:36 -0700416
417tcp_rmem - vector of 3 INTEGERs: min, default, max
418 min: Minimal size of receive buffer used by TCP sockets.
419 It is guaranteed to each TCP socket, even under moderate memory
420 pressure.
Max Matveev6539fef2011-06-21 21:18:13 +0000421 Default: 1 page
Linus Torvalds1da177e2005-04-16 15:20:36 -0700422
J. Bruce Fields53025f52008-07-10 16:47:41 -0700423 default: initial size of receive buffer used by TCP sockets.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700424 This value overrides net.core.rmem_default used by other protocols.
425 Default: 87380 bytes. This value results in window of 65535 with
426 default setting of tcp_adv_win_scale and tcp_app_win:0 and a bit
427 less for default tcp_app_win. See below about these variables.
428
429 max: maximal size of receive buffer allowed for automatically
430 selected receiver buffers for TCP socket. This value does not override
J. Bruce Fields53025f52008-07-10 16:47:41 -0700431 net.core.rmem_max. Calling setsockopt() with SO_RCVBUF disables
432 automatic tuning of that socket's receive buffer size, in which
433 case this value is ignored.
Eric Dumazetb49960a2012-05-02 02:28:41 +0000434 Default: between 87380B and 6MB, depending on RAM size.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700435
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800436tcp_sack - BOOLEAN
437 Enable select acknowledgments (SACKS).
Rick Jones15d99e02006-03-20 22:40:29 -0800438
David S. Miller35089bb2006-06-13 22:33:04 -0700439tcp_slow_start_after_idle - BOOLEAN
440 If set, provide RFC2861 behavior and time out the congestion
441 window after an idle period. An idle period is defined at
442 the current RTO. If unset, the congestion window will not
443 be timed out after an idle period.
444 Default: 1
445
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800446tcp_stdurg - BOOLEAN
Stephen Hemminger4edc2f32008-07-10 16:50:26 -0700447 Use the Host requirements interpretation of the TCP urgent pointer field.
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800448 Most hosts use the older BSD interpretation, so if you turn this on
449 Linux might not communicate correctly with them.
450 Default: FALSE
451
452tcp_synack_retries - INTEGER
453 Number of times SYNACKs for a passive TCP connection attempt will
454 be retransmitted. Should not be higher than 255. Default value
Alex Bergmann6c9ff972012-08-31 02:48:31 +0000455 is 5, which corresponds to 31seconds till the last retransmission
456 with the current initial RTO of 1second. With this the final timeout
457 for a passive TCP connection will happen after 63seconds.
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800458
459tcp_syncookies - BOOLEAN
Shan Weia3c910d2013-06-21 15:18:32 +0800460 Only valid when the kernel was compiled with CONFIG_SYN_COOKIES
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800461 Send out syncookies when the syn backlog queue of a socket
Stephen Hemminger4edc2f32008-07-10 16:50:26 -0700462 overflows. This is to prevent against the common 'SYN flood attack'
Shan Weia3c910d2013-06-21 15:18:32 +0800463 Default: 1
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800464
465 Note, that syncookies is fallback facility.
466 It MUST NOT be used to help highly loaded servers to stand
Stephen Hemminger4edc2f32008-07-10 16:50:26 -0700467 against legal connection rate. If you see SYN flood warnings
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800468 in your logs, but investigation shows that they occur
469 because of overload with legal connections, you should tune
470 another parameters until this warning disappear.
471 See: tcp_max_syn_backlog, tcp_synack_retries, tcp_abort_on_overflow.
472
473 syncookies seriously violate TCP protocol, do not allow
474 to use TCP extensions, can result in serious degradation
475 of some services (f.e. SMTP relaying), visible not by you,
476 but your clients and relays, contacting you. While you see
Stephen Hemminger4edc2f32008-07-10 16:50:26 -0700477 SYN flood warnings in logs not being really flooded, your server
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800478 is seriously misconfigured.
479
Hannes Frederic Sowa5ad37d52013-07-26 17:43:23 +0200480 If you want to test which effects syncookies have to your
481 network connections you can set this knob to 2 to enable
482 unconditionally generation of syncookies.
483
Yuchung Chengcf60af02012-07-19 06:43:09 +0000484tcp_fastopen - INTEGER
485 Enable TCP Fast Open feature (draft-ietf-tcpm-fastopen) to send data
486 in the opening SYN packet. To use this feature, the client application
Jerry Chu10467162012-08-31 12:29:11 +0000487 must use sendmsg() or sendto() with MSG_FASTOPEN flag rather than
488 connect() to perform a TCP handshake automatically.
Yuchung Chengcf60af02012-07-19 06:43:09 +0000489
Jerry Chu10467162012-08-31 12:29:11 +0000490 The values (bitmap) are
Yuchung Cheng0d41cca2013-10-31 09:19:32 -0700491 1: Enables sending data in the opening SYN on the client w/ MSG_FASTOPEN.
Jerry Chu10467162012-08-31 12:29:11 +0000492 2: Enables TCP Fast Open on the server side, i.e., allowing data in
493 a SYN packet to be accepted and passed to the application before
494 3-way hand shake finishes.
495 4: Send data in the opening SYN regardless of cookie availability and
496 without a cookie option.
497 0x100: Accept SYN data w/o validating the cookie.
498 0x200: Accept data-in-SYN w/o any cookie option present.
499 0x400/0x800: Enable Fast Open on all listeners regardless of the
500 TCP_FASTOPEN socket option. The two different flags designate two
501 different ways of setting max_qlen without the TCP_FASTOPEN socket
502 option.
Yuchung Chengcf60af02012-07-19 06:43:09 +0000503
Yuchung Cheng0d41cca2013-10-31 09:19:32 -0700504 Default: 1
Yuchung Chengcf60af02012-07-19 06:43:09 +0000505
Jerry Chu10467162012-08-31 12:29:11 +0000506 Note that the client & server side Fast Open flags (1 and 2
507 respectively) must be also enabled before the rest of flags can take
508 effect.
509
510 See include/net/tcp.h and the code for more details.
511
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800512tcp_syn_retries - INTEGER
513 Number of times initial SYNs for an active TCP connection attempt
514 will be retransmitted. Should not be higher than 255. Default value
stephen hemminger3b09adc2013-01-03 07:50:29 +0000515 is 6, which corresponds to 63seconds till the last retransmission
Alex Bergmann6c9ff972012-08-31 02:48:31 +0000516 with the current initial RTO of 1second. With this the final timeout
517 for an active TCP connection attempt will happen after 127seconds.
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800518
519tcp_timestamps - BOOLEAN
520 Enable timestamps as defined in RFC1323.
521
Eric Dumazet95bd09e2013-08-27 05:46:32 -0700522tcp_min_tso_segs - INTEGER
523 Minimal number of segments per TSO frame.
524 Since linux-3.12, TCP does an automatic sizing of TSO frames,
525 depending on flow rate, instead of filling 64Kbytes packets.
526 For specific usages, it's possible to force TCP to build big
527 TSO frames. Note that TCP stack might split too big TSO packets
528 if available window is too small.
529 Default: 2
530
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800531tcp_tso_win_divisor - INTEGER
532 This allows control over what percentage of the congestion window
533 can be consumed by a single TSO frame.
534 The setting of this parameter is a choice between burstiness and
535 building larger TSO frames.
536 Default: 3
537
538tcp_tw_recycle - BOOLEAN
539 Enable fast recycling TIME-WAIT sockets. Default value is 0.
540 It should not be changed without advice/request of technical
541 experts.
542
543tcp_tw_reuse - BOOLEAN
544 Allow to reuse TIME-WAIT sockets for new connections when it is
545 safe from protocol viewpoint. Default value is 0.
546 It should not be changed without advice/request of technical
547 experts.
548
549tcp_window_scaling - BOOLEAN
550 Enable window scaling as defined in RFC1323.
551
552tcp_wmem - vector of 3 INTEGERs: min, default, max
J. Bruce Fields53025f52008-07-10 16:47:41 -0700553 min: Amount of memory reserved for send buffers for TCP sockets.
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800554 Each TCP socket has rights to use it due to fact of its birth.
Max Matveev6539fef2011-06-21 21:18:13 +0000555 Default: 1 page
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800556
J. Bruce Fields53025f52008-07-10 16:47:41 -0700557 default: initial size of send buffer used by TCP sockets. This
558 value overrides net.core.wmem_default used by other protocols.
559 It is usually lower than net.core.wmem_default.
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800560 Default: 16K
561
J. Bruce Fields53025f52008-07-10 16:47:41 -0700562 max: Maximal amount of memory allowed for automatically tuned
563 send buffers for TCP sockets. This value does not override
564 net.core.wmem_max. Calling setsockopt() with SO_SNDBUF disables
565 automatic tuning of that socket's send buffer size, in which case
566 this value is ignored.
567 Default: between 64K and 4MB, depending on RAM size.
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800568
Eric Dumazetc9bee3b2013-07-22 20:27:07 -0700569tcp_notsent_lowat - UNSIGNED INTEGER
570 A TCP socket can control the amount of unsent bytes in its write queue,
571 thanks to TCP_NOTSENT_LOWAT socket option. poll()/select()/epoll()
572 reports POLLOUT events if the amount of unsent bytes is below a per
573 socket value, and if the write queue is not full. sendmsg() will
574 also not add new buffers if the limit is hit.
575
576 This global variable controls the amount of unsent data for
577 sockets not using TCP_NOTSENT_LOWAT. For these sockets, a change
578 to the global variable has immediate effect.
579
580 Default: UINT_MAX (0xFFFFFFFF)
581
Stephen Hemmingeref56e622006-11-09 16:37:26 -0800582tcp_workaround_signed_windows - BOOLEAN
583 If set, assume no receipt of a window scaling option means the
584 remote TCP is broken and treats the window as a signed quantity.
585 If unset, assume the remote TCP is not broken even if we do
586 not receive a window scaling option from them.
587 Default: 0
588
Chris Leech72d0b7a2007-03-08 09:57:35 -0800589tcp_dma_copybreak - INTEGER
590 Lower limit, in bytes, of the size of socket reads that will be
591 offloaded to a DMA copy engine, if one is present in the system
592 and CONFIG_NET_DMA is enabled.
593 Default: 4096
594
Andreas Petlund36e31b0a2010-02-18 02:47:01 +0000595tcp_thin_linear_timeouts - BOOLEAN
596 Enable dynamic triggering of linear timeouts for thin streams.
597 If set, a check is performed upon retransmission by timeout to
598 determine if the stream is thin (less than 4 packets in flight).
599 As long as the stream is found to be thin, up to 6 linear
600 timeouts may be performed before exponential backoff mode is
601 initiated. This improves retransmission latency for
602 non-aggressive thin streams, often found to be time-dependent.
603 For more information on thin streams, see
604 Documentation/networking/tcp-thin.txt
605 Default: 0
606
Andreas Petlund7e380172010-02-18 04:48:19 +0000607tcp_thin_dupack - BOOLEAN
608 Enable dynamic triggering of retransmissions after one dupACK
609 for thin streams. If set, a check is performed upon reception
610 of a dupACK to determine if the stream is thin (less than 4
611 packets in flight). As long as the stream is found to be thin,
612 data is retransmitted on the first received dupACK. This
613 improves retransmission latency for non-aggressive thin
614 streams, often found to be time-dependent.
615 For more information on thin streams, see
616 Documentation/networking/tcp-thin.txt
617 Default: 0
618
Eric Dumazet46d3cea2012-07-11 05:50:31 +0000619tcp_limit_output_bytes - INTEGER
620 Controls TCP Small Queue limit per tcp socket.
621 TCP bulk sender tends to increase packets in flight until it
622 gets losses notifications. With SNDBUF autotuning, this can
623 result in a large amount of packets queued in qdisc/device
624 on the local machine, hurting latency of other flows, for
625 typical pfifo_fast qdiscs.
626 tcp_limit_output_bytes limits the number of bytes on qdisc
627 or device to reduce artificial RTT/cwnd and reduce bufferbloat.
Eric Dumazet46d3cea2012-07-11 05:50:31 +0000628 Default: 131072
629
Eric Dumazet282f23c2012-07-17 10:13:05 +0200630tcp_challenge_ack_limit - INTEGER
631 Limits number of Challenge ACK sent per second, as recommended
632 in RFC 5961 (Improving TCP's Robustness to Blind In-Window Attacks)
633 Default: 100
634
Hideo Aoki95766ff2007-12-31 00:29:24 -0800635UDP variables:
636
637udp_mem - vector of 3 INTEGERs: min, pressure, max
638 Number of pages allowed for queueing by all UDP sockets.
639
640 min: Below this number of pages UDP is not bothered about its
641 memory appetite. When amount of memory allocated by UDP exceeds
642 this number, UDP starts to moderate memory usage.
643
644 pressure: This value was introduced to follow format of tcp_mem.
645
646 max: Number of pages allowed for queueing by all UDP sockets.
647
648 Default is calculated at boot time from amount of available memory.
649
650udp_rmem_min - INTEGER
651 Minimal size of receive buffer used by UDP sockets in moderation.
652 Each UDP socket is able to use the size for receiving data, even if
653 total pages of UDP sockets exceed udp_mem pressure. The unit is byte.
Max Matveev6539fef2011-06-21 21:18:13 +0000654 Default: 1 page
Hideo Aoki95766ff2007-12-31 00:29:24 -0800655
656udp_wmem_min - INTEGER
657 Minimal size of send buffer used by UDP sockets in moderation.
658 Each UDP socket is able to use the size for sending data, even if
659 total pages of UDP sockets exceed udp_mem pressure. The unit is byte.
Max Matveev6539fef2011-06-21 21:18:13 +0000660 Default: 1 page
Hideo Aoki95766ff2007-12-31 00:29:24 -0800661
Paul Moore8802f612006-08-03 16:45:49 -0700662CIPSOv4 Variables:
663
664cipso_cache_enable - BOOLEAN
665 If set, enable additions to and lookups from the CIPSO label mapping
666 cache. If unset, additions are ignored and lookups always result in a
667 miss. However, regardless of the setting the cache is still
668 invalidated when required when means you can safely toggle this on and
669 off and the cache will always be "safe".
670 Default: 1
671
672cipso_cache_bucket_size - INTEGER
673 The CIPSO label cache consists of a fixed size hash table with each
674 hash bucket containing a number of cache entries. This variable limits
675 the number of entries in each hash bucket; the larger the value the
676 more CIPSO label mappings that can be cached. When the number of
677 entries in a given hash bucket reaches this limit adding new entries
678 causes the oldest entry in the bucket to be removed to make room.
679 Default: 10
680
681cipso_rbm_optfmt - BOOLEAN
682 Enable the "Optimized Tag 1 Format" as defined in section 3.4.2.6 of
683 the CIPSO draft specification (see Documentation/netlabel for details).
684 This means that when set the CIPSO tag will be padded with empty
685 categories in order to make the packet data 32-bit aligned.
686 Default: 0
687
688cipso_rbm_structvalid - BOOLEAN
689 If set, do a very strict check of the CIPSO option when
690 ip_options_compile() is called. If unset, relax the checks done during
691 ip_options_compile(). Either way is "safe" as errors are caught else
692 where in the CIPSO processing code but setting this to 0 (False) should
693 result in less work (i.e. it should be faster) but could cause problems
694 with other implementations that require strict checking.
695 Default: 0
696
Linus Torvalds1da177e2005-04-16 15:20:36 -0700697IP Variables:
698
699ip_local_port_range - 2 INTEGERS
700 Defines the local port range that is used by TCP and UDP to
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +0000701 choose the local port. The first number is the first, the
Fernando Luis Vazquez Cao5d6bd862012-04-03 08:41:40 +0000702 second the last local port number. The default values are
703 32768 and 61000 respectively.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700704
Amerigo Wange3826f12010-05-05 00:27:06 +0000705ip_local_reserved_ports - list of comma separated ranges
706 Specify the ports which are reserved for known third-party
707 applications. These ports will not be used by automatic port
708 assignments (e.g. when calling connect() or bind() with port
709 number 0). Explicit port allocation behavior is unchanged.
710
711 The format used for both input and output is a comma separated
712 list of ranges (e.g. "1,2-4,10-10" for ports 1, 2, 3, 4 and
713 10). Writing to the file will clear all previously reserved
714 ports and update the current list with the one given in the
715 input.
716
717 Note that ip_local_port_range and ip_local_reserved_ports
718 settings are independent and both are considered by the kernel
719 when determining which ports are available for automatic port
720 assignments.
721
722 You can reserve ports which are not in the current
723 ip_local_port_range, e.g.:
724
725 $ cat /proc/sys/net/ipv4/ip_local_port_range
726 32000 61000
727 $ cat /proc/sys/net/ipv4/ip_local_reserved_ports
728 8080,9148
729
730 although this is redundant. However such a setting is useful
731 if later the port range is changed to a value that will
732 include the reserved ports.
733
734 Default: Empty
735
Linus Torvalds1da177e2005-04-16 15:20:36 -0700736ip_nonlocal_bind - BOOLEAN
737 If set, allows processes to bind() to non-local IP addresses,
738 which can be quite useful - but may break some applications.
739 Default: 0
740
741ip_dynaddr - BOOLEAN
742 If set non-zero, enables support for dynamic addresses.
743 If set to a non-zero value larger than 1, a kernel log
744 message will be printed when dynamic address rewriting
745 occurs.
746 Default: 0
747
Cong Wange3d73bc2013-06-11 18:54:39 +0800748ip_early_demux - BOOLEAN
749 Optimize input packet processing down to one demux for
750 certain kinds of local sockets. Currently we only do this
751 for established TCP sockets.
752
753 It may add an additional cost for pure routing workloads that
754 reduces overall throughput, in such case you should disable it.
755 Default: 1
756
Linus Torvalds1da177e2005-04-16 15:20:36 -0700757icmp_echo_ignore_all - BOOLEAN
David S. Miller7ce312462005-10-03 16:07:30 -0700758 If set non-zero, then the kernel will ignore all ICMP ECHO
759 requests sent to it.
760 Default: 0
761
Linus Torvalds1da177e2005-04-16 15:20:36 -0700762icmp_echo_ignore_broadcasts - BOOLEAN
David S. Miller7ce312462005-10-03 16:07:30 -0700763 If set non-zero, then the kernel will ignore all ICMP ECHO and
764 TIMESTAMP requests sent to it via broadcast/multicast.
765 Default: 1
Linus Torvalds1da177e2005-04-16 15:20:36 -0700766
767icmp_ratelimit - INTEGER
768 Limit the maximal rates for sending ICMP packets whose type matches
769 icmp_ratemask (see below) to specific targets.
Stephen Hemminger6dbf4bc2008-07-01 19:29:07 -0700770 0 to disable any limiting,
771 otherwise the minimal space between responses in milliseconds.
Eric Dumazet4cdf5072014-09-19 07:38:40 -0700772 Note that another sysctl, icmp_msgs_per_sec limits the number
773 of ICMP packets sent on all targets.
Stephen Hemminger6dbf4bc2008-07-01 19:29:07 -0700774 Default: 1000
Linus Torvalds1da177e2005-04-16 15:20:36 -0700775
Eric Dumazet4cdf5072014-09-19 07:38:40 -0700776icmp_msgs_per_sec - INTEGER
777 Limit maximal number of ICMP packets sent per second from this host.
778 Only messages whose type matches icmp_ratemask (see below) are
779 controlled by this limit.
780 Default: 1000
781
782icmp_msgs_burst - INTEGER
783 icmp_msgs_per_sec controls number of ICMP packets sent per second,
784 while icmp_msgs_burst controls the burst size of these packets.
785 Default: 50
786
Linus Torvalds1da177e2005-04-16 15:20:36 -0700787icmp_ratemask - INTEGER
788 Mask made of ICMP types for which rates are being limited.
789 Significant bits: IHGFEDCBA9876543210
790 Default mask: 0000001100000011000 (6168)
791
792 Bit definitions (see include/linux/icmp.h):
793 0 Echo Reply
794 3 Destination Unreachable *
795 4 Source Quench *
796 5 Redirect
797 8 Echo Request
798 B Time Exceeded *
799 C Parameter Problem *
800 D Timestamp Request
801 E Timestamp Reply
802 F Info Request
803 G Info Reply
804 H Address Mask Request
805 I Address Mask Reply
806
807 * These are rate limited by default (see default mask above)
808
809icmp_ignore_bogus_error_responses - BOOLEAN
810 Some routers violate RFC1122 by sending bogus responses to broadcast
811 frames. Such violations are normally logged via a kernel warning.
812 If this is set to TRUE, the kernel will not give such warnings, which
813 will avoid log file clutter.
Rami Rosene8b265e2013-06-07 20:16:19 +0000814 Default: 1
Linus Torvalds1da177e2005-04-16 15:20:36 -0700815
Horms95f7daf2006-02-02 17:02:25 -0800816icmp_errors_use_inbound_ifaddr - BOOLEAN
817
818 If zero, icmp error messages are sent with the primary address of
819 the exiting interface.
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +0000820
Horms95f7daf2006-02-02 17:02:25 -0800821 If non-zero, the message will be sent with the primary address of
822 the interface that received the packet that caused the icmp error.
823 This is the behaviour network many administrators will expect from
824 a router. And it can make debugging complicated network layouts
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +0000825 much easier.
Horms95f7daf2006-02-02 17:02:25 -0800826
827 Note that if no primary address exists for the interface selected,
828 then the primary address of the first non-loopback interface that
Matt LaPlanted6bc8ac2006-10-03 22:54:15 +0200829 has one will be used regardless of this setting.
Horms95f7daf2006-02-02 17:02:25 -0800830
831 Default: 0
832
Linus Torvalds1da177e2005-04-16 15:20:36 -0700833igmp_max_memberships - INTEGER
834 Change the maximum number of multicast groups we can subscribe to.
835 Default: 20
836
Jeremy Ederd67ef352010-11-15 05:41:31 +0000837 Theoretical maximum value is bounded by having to send a membership
838 report in a single datagram (i.e. the report can't span multiple
839 datagrams, or risk confusing the switch and leaving groups you don't
840 intend to).
Linus Torvalds1da177e2005-04-16 15:20:36 -0700841
Jeremy Ederd67ef352010-11-15 05:41:31 +0000842 The number of supported groups 'M' is bounded by the number of group
843 report entries you can fit into a single datagram of 65535 bytes.
844
845 M = 65536-sizeof (ip header)/(sizeof(Group record))
846
847 Group records are variable length, with a minimum of 12 bytes.
848 So net.ipv4.igmp_max_memberships should not be set higher than:
849
850 (65536-24) / 12 = 5459
851
852 The value 5459 assumes no IP header options, so in practice
853 this number may be lower.
854
855 conf/interface/* changes special settings per interface (where
856 "interface" is the name of your network interface)
857
858 conf/all/* is special, changes the settings for all interfaces
Linus Torvalds1da177e2005-04-16 15:20:36 -0700859
Hannes Frederic Sowaa9fe8e22014-09-02 15:49:26 +0200860igmp_qrv - INTEGER
861 Controls the IGMP query robustness variable (see RFC2236 8.1).
862 Default: 2 (as specified by RFC2236 8.1)
863 Minimum: 1 (as specified by RFC6636 4.5)
864
Linus Torvalds1da177e2005-04-16 15:20:36 -0700865log_martians - BOOLEAN
866 Log packets with impossible addresses to kernel log.
867 log_martians for the interface will be enabled if at least one of
868 conf/{all,interface}/log_martians is set to TRUE,
869 it will be disabled otherwise
870
871accept_redirects - BOOLEAN
872 Accept ICMP redirect messages.
873 accept_redirects for the interface will be enabled if:
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +0000874 - both conf/{all,interface}/accept_redirects are TRUE in the case
875 forwarding for the interface is enabled
Linus Torvalds1da177e2005-04-16 15:20:36 -0700876 or
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +0000877 - at least one of conf/{all,interface}/accept_redirects is TRUE in the
878 case forwarding for the interface is disabled
Linus Torvalds1da177e2005-04-16 15:20:36 -0700879 accept_redirects for the interface will be disabled otherwise
880 default TRUE (host)
881 FALSE (router)
882
883forwarding - BOOLEAN
884 Enable IP forwarding on this interface.
885
886mc_forwarding - BOOLEAN
887 Do multicast routing. The kernel needs to be compiled with CONFIG_MROUTE
888 and a multicast routing daemon is required.
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +0000889 conf/all/mc_forwarding must also be set to TRUE to enable multicast
890 routing for the interface
Linus Torvalds1da177e2005-04-16 15:20:36 -0700891
892medium_id - INTEGER
893 Integer value used to differentiate the devices by the medium they
894 are attached to. Two devices can have different id values when
895 the broadcast packets are received only on one of them.
896 The default value 0 means that the device is the only interface
897 to its medium, value of -1 means that medium is not known.
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +0000898
Linus Torvalds1da177e2005-04-16 15:20:36 -0700899 Currently, it is used to change the proxy_arp behavior:
900 the proxy_arp feature is enabled for packets forwarded between
901 two devices attached to different media.
902
903proxy_arp - BOOLEAN
904 Do proxy arp.
905 proxy_arp for the interface will be enabled if at least one of
906 conf/{all,interface}/proxy_arp is set to TRUE,
907 it will be disabled otherwise
908
Jesper Dangaard Brouer65324142010-01-05 05:50:47 +0000909proxy_arp_pvlan - BOOLEAN
910 Private VLAN proxy arp.
911 Basically allow proxy arp replies back to the same interface
912 (from which the ARP request/solicitation was received).
913
914 This is done to support (ethernet) switch features, like RFC
915 3069, where the individual ports are NOT allowed to
916 communicate with each other, but they are allowed to talk to
917 the upstream router. As described in RFC 3069, it is possible
918 to allow these hosts to communicate through the upstream
919 router by proxy_arp'ing. Don't need to be used together with
920 proxy_arp.
921
922 This technology is known by different names:
923 In RFC 3069 it is called VLAN Aggregation.
924 Cisco and Allied Telesyn call it Private VLAN.
925 Hewlett-Packard call it Source-Port filtering or port-isolation.
926 Ericsson call it MAC-Forced Forwarding (RFC Draft).
927
Linus Torvalds1da177e2005-04-16 15:20:36 -0700928shared_media - BOOLEAN
929 Send(router) or accept(host) RFC1620 shared media redirects.
930 Overrides ip_secure_redirects.
931 shared_media for the interface will be enabled if at least one of
932 conf/{all,interface}/shared_media is set to TRUE,
933 it will be disabled otherwise
934 default TRUE
935
936secure_redirects - BOOLEAN
937 Accept ICMP redirect messages only for gateways,
938 listed in default gateway list.
939 secure_redirects for the interface will be enabled if at least one of
940 conf/{all,interface}/secure_redirects is set to TRUE,
941 it will be disabled otherwise
942 default TRUE
943
944send_redirects - BOOLEAN
945 Send redirects, if router.
946 send_redirects for the interface will be enabled if at least one of
947 conf/{all,interface}/send_redirects is set to TRUE,
948 it will be disabled otherwise
949 Default: TRUE
950
951bootp_relay - BOOLEAN
952 Accept packets with source address 0.b.c.d destined
953 not to this host as local ones. It is supposed, that
954 BOOTP relay daemon will catch and forward such packets.
955 conf/all/bootp_relay must also be set to TRUE to enable BOOTP relay
956 for the interface
957 default FALSE
958 Not Implemented Yet.
959
960accept_source_route - BOOLEAN
961 Accept packets with SRR option.
962 conf/all/accept_source_route must also be set to TRUE to accept packets
963 with SRR option on the interface
964 default TRUE (router)
965 FALSE (host)
966
Patrick McHardy8153a102009-12-03 01:25:58 +0000967accept_local - BOOLEAN
Sébastien Barré72b126a2014-09-10 18:20:23 +0200968 Accept packets with local source addresses. In combination with
969 suitable routing, this can be used to direct packets between two
970 local interfaces over the wire and have them accepted properly.
Patrick McHardy8153a102009-12-03 01:25:58 +0000971 default FALSE
972
Thomas Grafd0daebc32012-06-12 00:44:01 +0000973route_localnet - BOOLEAN
974 Do not consider loopback addresses as martian source or destination
975 while routing. This enables the use of 127/8 for local routing purposes.
976 default FALSE
977
Stephen Hemmingerc1cf8422009-02-20 08:25:36 +0000978rp_filter - INTEGER
Linus Torvalds1da177e2005-04-16 15:20:36 -0700979 0 - No source validation.
Stephen Hemmingerc1cf8422009-02-20 08:25:36 +0000980 1 - Strict mode as defined in RFC3704 Strict Reverse Path
981 Each incoming packet is tested against the FIB and if the interface
982 is not the best reverse path the packet check will fail.
983 By default failed packets are discarded.
984 2 - Loose mode as defined in RFC3704 Loose Reverse Path
985 Each incoming packet's source address is also tested against the FIB
986 and if the source address is not reachable via any interface
987 the packet check will fail.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700988
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +0000989 Current recommended practice in RFC3704 is to enable strict mode
Jesper Dangaard Brouerbf869c32009-02-23 04:37:55 +0000990 to prevent IP spoofing from DDos attacks. If using asymmetric routing
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +0000991 or other complicated routing, then loose mode is recommended.
Stephen Hemmingerc1cf8422009-02-20 08:25:36 +0000992
Shan Wei1f5865e2009-12-02 15:39:04 -0800993 The max value from conf/{all,interface}/rp_filter is used
994 when doing source validation on the {interface}.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700995
996 Default value is 0. Note that some distributions enable it
997 in startup scripts.
998
999arp_filter - BOOLEAN
1000 1 - Allows you to have multiple network interfaces on the same
1001 subnet, and have the ARPs for each interface be answered
1002 based on whether or not the kernel would route a packet from
1003 the ARP'd IP out that interface (therefore you must use source
1004 based routing for this to work). In other words it allows control
1005 of which cards (usually 1) will respond to an arp request.
1006
1007 0 - (default) The kernel can respond to arp requests with addresses
1008 from other interfaces. This may seem wrong but it usually makes
1009 sense, because it increases the chance of successful communication.
1010 IP addresses are owned by the complete host on Linux, not by
1011 particular interfaces. Only for more complex setups like load-
1012 balancing, does this behaviour cause problems.
1013
1014 arp_filter for the interface will be enabled if at least one of
1015 conf/{all,interface}/arp_filter is set to TRUE,
1016 it will be disabled otherwise
1017
1018arp_announce - INTEGER
1019 Define different restriction levels for announcing the local
1020 source IP address from IP packets in ARP requests sent on
1021 interface:
1022 0 - (default) Use any local address, configured on any interface
1023 1 - Try to avoid local addresses that are not in the target's
1024 subnet for this interface. This mode is useful when target
1025 hosts reachable via this interface require the source IP
1026 address in ARP requests to be part of their logical network
1027 configured on the receiving interface. When we generate the
1028 request we will check all our subnets that include the
1029 target IP and will preserve the source address if it is from
1030 such subnet. If there is no such subnet we select source
1031 address according to the rules for level 2.
1032 2 - Always use the best local address for this target.
1033 In this mode we ignore the source address in the IP packet
1034 and try to select local address that we prefer for talks with
1035 the target host. Such local address is selected by looking
1036 for primary IP addresses on all our subnets on the outgoing
1037 interface that include the target IP address. If no suitable
1038 local address is found we select the first local address
1039 we have on the outgoing interface or on all other interfaces,
1040 with the hope we will receive reply for our request and
1041 even sometimes no matter the source IP address we announce.
1042
1043 The max value from conf/{all,interface}/arp_announce is used.
1044
1045 Increasing the restriction level gives more chance for
1046 receiving answer from the resolved target while decreasing
1047 the level announces more valid sender's information.
1048
1049arp_ignore - INTEGER
1050 Define different modes for sending replies in response to
1051 received ARP requests that resolve local target IP addresses:
1052 0 - (default): reply for any local target IP address, configured
1053 on any interface
1054 1 - reply only if the target IP address is local address
1055 configured on the incoming interface
1056 2 - reply only if the target IP address is local address
1057 configured on the incoming interface and both with the
1058 sender's IP address are part from same subnet on this interface
1059 3 - do not reply for local addresses configured with scope host,
1060 only resolutions for global and link addresses are replied
1061 4-7 - reserved
1062 8 - do not reply for all local addresses
1063
1064 The max value from conf/{all,interface}/arp_ignore is used
1065 when ARP request is received on the {interface}
1066
Stephen Hemmingereefef1c2009-02-01 01:04:33 -08001067arp_notify - BOOLEAN
1068 Define mode for notification of address and device changes.
1069 0 - (default): do nothing
Ian Campbell3f8dc232010-05-26 00:09:41 +00001070 1 - Generate gratuitous arp requests when device is brought up
Stephen Hemmingereefef1c2009-02-01 01:04:33 -08001071 or hardware address changes.
1072
Neil Hormanc1b1bce2006-03-20 22:40:03 -08001073arp_accept - BOOLEAN
Octavian Purdila6d955182010-01-18 12:58:44 +00001074 Define behavior for gratuitous ARP frames who's IP is not
1075 already present in the ARP table:
1076 0 - don't create new entries in the ARP table
1077 1 - create new entries in the ARP table
1078
1079 Both replies and requests type gratuitous arp will trigger the
1080 ARP table to be updated, if this setting is on.
1081
1082 If the ARP table already contains the IP address of the
1083 gratuitous arp frame, the arp table will be updated regardless
1084 if this setting is on or off.
1085
Neil Hormanc1b1bce2006-03-20 22:40:03 -08001086
Linus Torvalds1da177e2005-04-16 15:20:36 -07001087app_solicit - INTEGER
1088 The maximum number of probes to send to the user space ARP daemon
1089 via netlink before dropping back to multicast probes (see
1090 mcast_solicit). Defaults to 0.
1091
1092disable_policy - BOOLEAN
1093 Disable IPSEC policy (SPD) for this interface
1094
1095disable_xfrm - BOOLEAN
1096 Disable IPSEC encryption on this interface, whatever the policy
1097
Hannes Frederic Sowafc4eba52013-08-14 01:03:46 +02001098igmpv2_unsolicited_report_interval - INTEGER
1099 The interval in milliseconds in which the next unsolicited
1100 IGMPv1 or IGMPv2 report retransmit will take place.
1101 Default: 10000 (10 seconds)
Linus Torvalds1da177e2005-04-16 15:20:36 -07001102
Hannes Frederic Sowafc4eba52013-08-14 01:03:46 +02001103igmpv3_unsolicited_report_interval - INTEGER
1104 The interval in milliseconds in which the next unsolicited
1105 IGMPv3 report retransmit will take place.
1106 Default: 1000 (1 seconds)
Linus Torvalds1da177e2005-04-16 15:20:36 -07001107
Martin Schwenked922e1c2014-01-28 15:26:42 +11001108promote_secondaries - BOOLEAN
1109 When a primary IP address is removed from this interface
1110 promote a corresponding secondary IP address instead of
1111 removing all the corresponding secondary IP addresses.
1112
1113
Linus Torvalds1da177e2005-04-16 15:20:36 -07001114tag - INTEGER
1115 Allows you to write a number, which can be used as required.
1116 Default value is 0.
1117
Linus Torvalds1da177e2005-04-16 15:20:36 -07001118Alexey Kuznetsov.
1119kuznet@ms2.inr.ac.ru
1120
1121Updated by:
1122Andi Kleen
1123ak@muc.de
1124Nicolas Delon
1125delon.nicolas@wanadoo.fr
1126
1127
1128
1129
1130/proc/sys/net/ipv6/* Variables:
1131
1132IPv6 has no global variables such as tcp_*. tcp_* settings under ipv4/ also
1133apply to IPv6 [XXX?].
1134
1135bindv6only - BOOLEAN
1136 Default value for IPV6_V6ONLY socket option,
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +00001137 which restricts use of the IPv6 socket to IPv6 communication
Linus Torvalds1da177e2005-04-16 15:20:36 -07001138 only.
1139 TRUE: disable IPv4-mapped address feature
1140 FALSE: enable IPv4-mapped address feature
1141
Geoffrey Thomasd5c073ca2011-08-22 11:28:57 -07001142 Default: FALSE (as specified in RFC3493)
Linus Torvalds1da177e2005-04-16 15:20:36 -07001143
Florent Fourcot6444f722014-01-17 17:15:05 +01001144flowlabel_consistency - BOOLEAN
1145 Protect the consistency (and unicity) of flow label.
1146 You have to disable it to use IPV6_FL_F_REFLECT flag on the
1147 flow label manager.
1148 TRUE: enabled
1149 FALSE: disabled
1150 Default: TRUE
1151
Tom Herbertcb1ce2e2014-07-01 21:33:10 -07001152auto_flowlabels - BOOLEAN
1153 Automatically generate flow labels based based on a flow hash
1154 of the packet. This allows intermediate devices, such as routers,
1155 to idenfify packet flows for mechanisms like Equal Cost Multipath
1156 Routing (see RFC 6438).
1157 TRUE: enabled
1158 FALSE: disabled
1159 Default: false
1160
FX Le Bail509aba32014-01-07 14:57:27 +01001161anycast_src_echo_reply - BOOLEAN
1162 Controls the use of anycast addresses as source addresses for ICMPv6
1163 echo reply
1164 TRUE: enabled
1165 FALSE: disabled
1166 Default: FALSE
1167
Hannes Frederic Sowa2f711932014-09-02 15:49:25 +02001168mld_qrv - INTEGER
1169 Controls the MLD query robustness variable (see RFC3810 9.1).
1170 Default: 2 (as specified by RFC3810 9.1)
1171 Minimum: 1 (as specified by RFC6636 4.5)
1172
Linus Torvalds1da177e2005-04-16 15:20:36 -07001173IPv6 Fragmentation:
1174
1175ip6frag_high_thresh - INTEGER
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +00001176 Maximum memory used to reassemble IPv6 fragments. When
Linus Torvalds1da177e2005-04-16 15:20:36 -07001177 ip6frag_high_thresh bytes of memory is allocated for this purpose,
1178 the fragment handler will toss packets until ip6frag_low_thresh
1179 is reached.
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +00001180
Linus Torvalds1da177e2005-04-16 15:20:36 -07001181ip6frag_low_thresh - INTEGER
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +00001182 See ip6frag_high_thresh
Linus Torvalds1da177e2005-04-16 15:20:36 -07001183
1184ip6frag_time - INTEGER
1185 Time in seconds to keep an IPv6 fragment in memory.
1186
Linus Torvalds1da177e2005-04-16 15:20:36 -07001187conf/default/*:
1188 Change the interface-specific default settings.
1189
1190
1191conf/all/*:
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +00001192 Change all the interface-specific settings.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001193
1194 [XXX: Other special features than forwarding?]
1195
1196conf/all/forwarding - BOOLEAN
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +00001197 Enable global IPv6 forwarding between all interfaces.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001198
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +00001199 IPv4 and IPv6 work differently here; e.g. netfilter must be used
Linus Torvalds1da177e2005-04-16 15:20:36 -07001200 to control which interfaces may forward packets and which not.
1201
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +00001202 This also sets all interfaces' Host/Router setting
Linus Torvalds1da177e2005-04-16 15:20:36 -07001203 'forwarding' to the specified value. See below for details.
1204
1205 This referred to as global forwarding.
1206
YOSHIFUJI Hideakifbea49e2006-09-22 14:43:49 -07001207proxy_ndp - BOOLEAN
1208 Do proxy ndp.
1209
Linus Torvalds1da177e2005-04-16 15:20:36 -07001210conf/interface/*:
1211 Change special settings per interface.
1212
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +00001213 The functional behaviour for certain settings is different
Linus Torvalds1da177e2005-04-16 15:20:36 -07001214 depending on whether local forwarding is enabled or not.
1215
Roy.Li605b91c2011-09-28 19:51:54 +00001216accept_ra - INTEGER
Linus Torvalds1da177e2005-04-16 15:20:36 -07001217 Accept Router Advertisements; autoconfigure using them.
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +00001218
Tore Anderson026359b2011-08-28 23:47:33 +00001219 It also determines whether or not to transmit Router
1220 Solicitations. If and only if the functional setting is to
1221 accept Router Advertisements, Router Solicitations will be
1222 transmitted.
1223
Thomas Grafae8abfa2010-09-03 05:47:30 +00001224 Possible values are:
1225 0 Do not accept Router Advertisements.
1226 1 Accept Router Advertisements if forwarding is disabled.
1227 2 Overrule forwarding behaviour. Accept Router Advertisements
1228 even if forwarding is enabled.
1229
Linus Torvalds1da177e2005-04-16 15:20:36 -07001230 Functional default: enabled if local forwarding is disabled.
1231 disabled if local forwarding is enabled.
1232
YOSHIFUJI Hideaki65f5c7c2006-03-20 16:55:08 -08001233accept_ra_defrtr - BOOLEAN
1234 Learn default router in Router Advertisement.
1235
1236 Functional default: enabled if accept_ra is enabled.
1237 disabled if accept_ra is disabled.
1238
Ben Greeard9333192014-06-25 14:44:53 -07001239accept_ra_from_local - BOOLEAN
1240 Accept RA with source-address that is found on local machine
1241 if the RA is otherwise proper and able to be accepted.
1242 Default is to NOT accept these as it may be an un-intended
1243 network loop.
1244
1245 Functional default:
1246 enabled if accept_ra_from_local is enabled
1247 on a specific interface.
1248 disabled if accept_ra_from_local is disabled
1249 on a specific interface.
1250
YOSHIFUJI Hideakic4fd30e2006-03-20 16:55:26 -08001251accept_ra_pinfo - BOOLEAN
Matt LaPlante2fe0ae72006-10-03 22:50:39 +02001252 Learn Prefix Information in Router Advertisement.
YOSHIFUJI Hideakic4fd30e2006-03-20 16:55:26 -08001253
1254 Functional default: enabled if accept_ra is enabled.
1255 disabled if accept_ra is disabled.
1256
YOSHIFUJI Hideaki09c884d2006-03-20 17:07:03 -08001257accept_ra_rt_info_max_plen - INTEGER
1258 Maximum prefix length of Route Information in RA.
1259
1260 Route Information w/ prefix larger than or equal to this
1261 variable shall be ignored.
1262
1263 Functional default: 0 if accept_ra_rtr_pref is enabled.
1264 -1 if accept_ra_rtr_pref is disabled.
1265
YOSHIFUJI Hideaki930d6ff2006-03-20 17:05:30 -08001266accept_ra_rtr_pref - BOOLEAN
1267 Accept Router Preference in RA.
1268
1269 Functional default: enabled if accept_ra is enabled.
1270 disabled if accept_ra is disabled.
1271
Linus Torvalds1da177e2005-04-16 15:20:36 -07001272accept_redirects - BOOLEAN
1273 Accept Redirects.
1274
1275 Functional default: enabled if local forwarding is disabled.
1276 disabled if local forwarding is enabled.
1277
YOSHIFUJI Hideaki0bcbc922007-04-24 14:58:30 -07001278accept_source_route - INTEGER
1279 Accept source routing (routing extension header).
1280
YOSHIFUJI Hideakibb4dbf92007-07-10 22:55:49 -07001281 >= 0: Accept only routing header type 2.
YOSHIFUJI Hideaki0bcbc922007-04-24 14:58:30 -07001282 < 0: Do not accept routing header.
1283
1284 Default: 0
1285
Linus Torvalds1da177e2005-04-16 15:20:36 -07001286autoconf - BOOLEAN
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +00001287 Autoconfigure addresses using Prefix Information in Router
Linus Torvalds1da177e2005-04-16 15:20:36 -07001288 Advertisements.
1289
YOSHIFUJI Hideakic4fd30e2006-03-20 16:55:26 -08001290 Functional default: enabled if accept_ra_pinfo is enabled.
1291 disabled if accept_ra_pinfo is disabled.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001292
1293dad_transmits - INTEGER
1294 The amount of Duplicate Address Detection probes to send.
1295 Default: 1
Linus Torvalds1da177e2005-04-16 15:20:36 -07001296
Roy.Li605b91c2011-09-28 19:51:54 +00001297forwarding - INTEGER
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +00001298 Configure interface-specific Host/Router behaviour.
1299
1300 Note: It is recommended to have the same setting on all
Linus Torvalds1da177e2005-04-16 15:20:36 -07001301 interfaces; mixed router/host scenarios are rather uncommon.
1302
Thomas Grafae8abfa2010-09-03 05:47:30 +00001303 Possible values are:
1304 0 Forwarding disabled
1305 1 Forwarding enabled
Thomas Grafae8abfa2010-09-03 05:47:30 +00001306
1307 FALSE (0):
Linus Torvalds1da177e2005-04-16 15:20:36 -07001308
1309 By default, Host behaviour is assumed. This means:
1310
1311 1. IsRouter flag is not set in Neighbour Advertisements.
Tore Anderson026359b2011-08-28 23:47:33 +00001312 2. If accept_ra is TRUE (default), transmit Router
1313 Solicitations.
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +00001314 3. If accept_ra is TRUE (default), accept Router
Linus Torvalds1da177e2005-04-16 15:20:36 -07001315 Advertisements (and do autoconfiguration).
1316 4. If accept_redirects is TRUE (default), accept Redirects.
1317
Thomas Grafae8abfa2010-09-03 05:47:30 +00001318 TRUE (1):
Linus Torvalds1da177e2005-04-16 15:20:36 -07001319
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +00001320 If local forwarding is enabled, Router behaviour is assumed.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001321 This means exactly the reverse from the above:
1322
1323 1. IsRouter flag is set in Neighbour Advertisements.
Tore Anderson026359b2011-08-28 23:47:33 +00001324 2. Router Solicitations are not sent unless accept_ra is 2.
Thomas Grafae8abfa2010-09-03 05:47:30 +00001325 3. Router Advertisements are ignored unless accept_ra is 2.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001326 4. Redirects are ignored.
1327
Thomas Grafae8abfa2010-09-03 05:47:30 +00001328 Default: 0 (disabled) if global forwarding is disabled (default),
1329 otherwise 1 (enabled).
Linus Torvalds1da177e2005-04-16 15:20:36 -07001330
1331hop_limit - INTEGER
1332 Default Hop Limit to set.
1333 Default: 64
1334
1335mtu - INTEGER
1336 Default Maximum Transfer Unit
1337 Default: 1280 (IPv6 required minimum)
1338
YOSHIFUJI Hideaki52e16352006-03-20 17:05:47 -08001339router_probe_interval - INTEGER
1340 Minimum interval (in seconds) between Router Probing described
1341 in RFC4191.
1342
1343 Default: 60
1344
Linus Torvalds1da177e2005-04-16 15:20:36 -07001345router_solicitation_delay - INTEGER
1346 Number of seconds to wait after interface is brought up
1347 before sending Router Solicitations.
1348 Default: 1
1349
1350router_solicitation_interval - INTEGER
1351 Number of seconds to wait between Router Solicitations.
1352 Default: 4
1353
1354router_solicitations - INTEGER
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +00001355 Number of Router Solicitations to send until assuming no
Linus Torvalds1da177e2005-04-16 15:20:36 -07001356 routers are present.
1357 Default: 3
1358
1359use_tempaddr - INTEGER
1360 Preference for Privacy Extensions (RFC3041).
1361 <= 0 : disable Privacy Extensions
1362 == 1 : enable Privacy Extensions, but prefer public
1363 addresses over temporary addresses.
1364 > 1 : enable Privacy Extensions and prefer temporary
1365 addresses over public addresses.
1366 Default: 0 (for most devices)
1367 -1 (for point-to-point devices and loopback devices)
1368
1369temp_valid_lft - INTEGER
1370 valid lifetime (in seconds) for temporary addresses.
1371 Default: 604800 (7 days)
1372
1373temp_prefered_lft - INTEGER
1374 Preferred lifetime (in seconds) for temporary addresses.
1375 Default: 86400 (1 day)
1376
1377max_desync_factor - INTEGER
1378 Maximum value for DESYNC_FACTOR, which is a random value
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +00001379 that ensures that clients don't synchronize with each
Linus Torvalds1da177e2005-04-16 15:20:36 -07001380 other and generate new addresses at exactly the same time.
1381 value is in seconds.
1382 Default: 600
Jesper Dangaard Brouere18f5fe2009-02-23 04:39:04 +00001383
Linus Torvalds1da177e2005-04-16 15:20:36 -07001384regen_max_retry - INTEGER
1385 Number of attempts before give up attempting to generate
1386 valid temporary addresses.
1387 Default: 5
1388
1389max_addresses - INTEGER
Brian Haleye79dc482010-02-22 12:27:21 +00001390 Maximum number of autoconfigured addresses per interface. Setting
1391 to zero disables the limitation. It is not recommended to set this
1392 value too large (or to zero) because it would be an easy way to
1393 crash the kernel by allowing too many addresses to be created.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001394 Default: 16
1395
YOSHIFUJI Hideaki778d80b2008-06-28 14:17:11 +09001396disable_ipv6 - BOOLEAN
Brian Haley9bdd8d42009-03-18 18:22:48 -07001397 Disable IPv6 operation. If accept_dad is set to 2, this value
1398 will be dynamically set to TRUE if DAD fails for the link-local
1399 address.
YOSHIFUJI Hideaki778d80b2008-06-28 14:17:11 +09001400 Default: FALSE (enable IPv6 operation)
1401
Brian Haley56d417b2009-06-01 03:07:33 -07001402 When this value is changed from 1 to 0 (IPv6 is being enabled),
1403 it will dynamically create a link-local address on the given
1404 interface and start Duplicate Address Detection, if necessary.
1405
1406 When this value is changed from 0 to 1 (IPv6 is being disabled),
1407 it will dynamically delete all address on the given interface.
1408
YOSHIFUJI Hideaki1b34be72008-06-28 14:18:38 +09001409accept_dad - INTEGER
1410 Whether to accept DAD (Duplicate Address Detection).
1411 0: Disable DAD
1412 1: Enable DAD (default)
1413 2: Enable DAD, and disable IPv6 operation if MAC-based duplicate
1414 link-local address has been found.
1415
Octavian Purdilaf7734fd2009-10-02 11:39:15 +00001416force_tllao - BOOLEAN
1417 Enable sending the target link-layer address option even when
1418 responding to a unicast neighbor solicitation.
1419 Default: FALSE
1420
1421 Quoting from RFC 2461, section 4.4, Target link-layer address:
1422
1423 "The option MUST be included for multicast solicitations in order to
1424 avoid infinite Neighbor Solicitation "recursion" when the peer node
1425 does not have a cache entry to return a Neighbor Advertisements
1426 message. When responding to unicast solicitations, the option can be
1427 omitted since the sender of the solicitation has the correct link-
1428 layer address; otherwise it would not have be able to send the unicast
1429 solicitation in the first place. However, including the link-layer
1430 address in this case adds little overhead and eliminates a potential
1431 race condition where the sender deletes the cached link-layer address
1432 prior to receiving a response to a previous solicitation."
1433
Hannes Frederic Sowadb2b6202013-01-01 00:35:31 +00001434ndisc_notify - BOOLEAN
1435 Define mode for notification of address and device changes.
1436 0 - (default): do nothing
1437 1 - Generate unsolicited neighbour advertisements when device is brought
1438 up or hardware address changes.
1439
Hannes Frederic Sowafc4eba52013-08-14 01:03:46 +02001440mldv1_unsolicited_report_interval - INTEGER
1441 The interval in milliseconds in which the next unsolicited
1442 MLDv1 report retransmit will take place.
1443 Default: 10000 (10 seconds)
1444
1445mldv2_unsolicited_report_interval - INTEGER
1446 The interval in milliseconds in which the next unsolicited
1447 MLDv2 report retransmit will take place.
1448 Default: 1000 (1 second)
1449
Daniel Borkmannf2127812013-09-04 00:19:44 +02001450force_mld_version - INTEGER
1451 0 - (default) No enforcement of a MLD version, MLDv1 fallback allowed
1452 1 - Enforce to use MLD version 1
1453 2 - Enforce to use MLD version 2
1454
Hannes Frederic Sowab800c3b2013-08-27 01:36:51 +02001455suppress_frag_ndisc - INTEGER
1456 Control RFC 6980 (Security Implications of IPv6 Fragmentation
1457 with IPv6 Neighbor Discovery) behavior:
1458 1 - (default) discard fragmented neighbor discovery packets
1459 0 - allow fragmented neighbor discovery packets
1460
Linus Torvalds1da177e2005-04-16 15:20:36 -07001461icmp/*:
1462ratelimit - INTEGER
1463 Limit the maximal rates for sending ICMPv6 packets.
Stephen Hemminger6dbf4bc2008-07-01 19:29:07 -07001464 0 to disable any limiting,
1465 otherwise the minimal space between responses in milliseconds.
1466 Default: 1000
Linus Torvalds1da177e2005-04-16 15:20:36 -07001467
1468
1469IPv6 Update by:
1470Pekka Savola <pekkas@netcore.fi>
1471YOSHIFUJI Hideaki / USAGI Project <yoshfuji@linux-ipv6.org>
1472
1473
1474/proc/sys/net/bridge/* Variables:
1475
1476bridge-nf-call-arptables - BOOLEAN
1477 1 : pass bridged ARP traffic to arptables' FORWARD chain.
1478 0 : disable this.
1479 Default: 1
1480
1481bridge-nf-call-iptables - BOOLEAN
1482 1 : pass bridged IPv4 traffic to iptables' chains.
1483 0 : disable this.
1484 Default: 1
1485
1486bridge-nf-call-ip6tables - BOOLEAN
1487 1 : pass bridged IPv6 traffic to ip6tables' chains.
1488 0 : disable this.
1489 Default: 1
1490
1491bridge-nf-filter-vlan-tagged - BOOLEAN
Michael Milner516299d2007-04-12 22:14:23 -07001492 1 : pass bridged vlan-tagged ARP/IP/IPv6 traffic to {arp,ip,ip6}tables.
1493 0 : disable this.
Pablo Neira Ayuso49816822012-05-08 19:36:44 +02001494 Default: 0
Michael Milner516299d2007-04-12 22:14:23 -07001495
1496bridge-nf-filter-pppoe-tagged - BOOLEAN
1497 1 : pass bridged pppoe-tagged IP/IPv6 traffic to {ip,ip6}tables.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001498 0 : disable this.
Pablo Neira Ayuso49816822012-05-08 19:36:44 +02001499 Default: 0
Linus Torvalds1da177e2005-04-16 15:20:36 -07001500
Pablo Neira Ayuso49816822012-05-08 19:36:44 +02001501bridge-nf-pass-vlan-input-dev - BOOLEAN
1502 1: if bridge-nf-filter-vlan-tagged is enabled, try to find a vlan
1503 interface on the bridge and set the netfilter input device to the vlan.
1504 This allows use of e.g. "iptables -i br0.1" and makes the REDIRECT
1505 target work with vlan-on-top-of-bridge interfaces. When no matching
1506 vlan interface is found, or this switch is off, the input device is
1507 set to the bridge interface.
1508 0: disable bridge netfilter vlan interface lookup.
1509 Default: 0
Linus Torvalds1da177e2005-04-16 15:20:36 -07001510
Vlad Yasevich32e8d492008-07-08 16:43:29 -07001511proc/sys/net/sctp/* Variables:
1512
1513addip_enable - BOOLEAN
1514 Enable or disable extension of Dynamic Address Reconfiguration
1515 (ADD-IP) functionality specified in RFC5061. This extension provides
1516 the ability to dynamically add and remove new addresses for the SCTP
1517 associations.
1518
1519 1: Enable extension.
1520
1521 0: Disable extension.
1522
1523 Default: 0
1524
1525addip_noauth_enable - BOOLEAN
1526 Dynamic Address Reconfiguration (ADD-IP) requires the use of
1527 authentication to protect the operations of adding or removing new
1528 addresses. This requirement is mandated so that unauthorized hosts
1529 would not be able to hijack associations. However, older
1530 implementations may not have implemented this requirement while
1531 allowing the ADD-IP extension. For reasons of interoperability,
1532 we provide this variable to control the enforcement of the
1533 authentication requirement.
1534
1535 1: Allow ADD-IP extension to be used without authentication. This
1536 should only be set in a closed environment for interoperability
1537 with older implementations.
1538
1539 0: Enforce the authentication requirement
1540
1541 Default: 0
1542
1543auth_enable - BOOLEAN
1544 Enable or disable Authenticated Chunks extension. This extension
1545 provides the ability to send and receive authenticated chunks and is
1546 required for secure operation of Dynamic Address Reconfiguration
1547 (ADD-IP) extension.
1548
1549 1: Enable this extension.
1550 0: Disable this extension.
1551
1552 Default: 0
1553
1554prsctp_enable - BOOLEAN
1555 Enable or disable the Partial Reliability extension (RFC3758) which
1556 is used to notify peers that a given DATA should no longer be expected.
1557
1558 1: Enable extension
1559 0: Disable
1560
1561 Default: 1
1562
1563max_burst - INTEGER
1564 The limit of the number of new packets that can be initially sent. It
1565 controls how bursty the generated traffic can be.
1566
1567 Default: 4
1568
1569association_max_retrans - INTEGER
1570 Set the maximum number for retransmissions that an association can
1571 attempt deciding that the remote end is unreachable. If this value
1572 is exceeded, the association is terminated.
1573
1574 Default: 10
1575
1576max_init_retransmits - INTEGER
1577 The maximum number of retransmissions of INIT and COOKIE-ECHO chunks
1578 that an association will attempt before declaring the destination
1579 unreachable and terminating.
1580
1581 Default: 8
1582
1583path_max_retrans - INTEGER
1584 The maximum number of retransmissions that will be attempted on a given
1585 path. Once this threshold is exceeded, the path is considered
1586 unreachable, and new traffic will use a different path when the
1587 association is multihomed.
1588
1589 Default: 5
1590
Neil Horman5aa93bc2012-07-21 07:56:07 +00001591pf_retrans - INTEGER
1592 The number of retransmissions that will be attempted on a given path
1593 before traffic is redirected to an alternate transport (should one
1594 exist). Note this is distinct from path_max_retrans, as a path that
1595 passes the pf_retrans threshold can still be used. Its only
1596 deprioritized when a transmission path is selected by the stack. This
1597 setting is primarily used to enable fast failover mechanisms without
1598 having to reduce path_max_retrans to a very low value. See:
1599 http://www.ietf.org/id/draft-nishida-tsvwg-sctp-failover-05.txt
1600 for details. Note also that a value of pf_retrans > path_max_retrans
1601 disables this feature
1602
1603 Default: 0
1604
Vlad Yasevich32e8d492008-07-08 16:43:29 -07001605rto_initial - INTEGER
1606 The initial round trip timeout value in milliseconds that will be used
1607 in calculating round trip times. This is the initial time interval
1608 for retransmissions.
1609
1610 Default: 3000
1611
1612rto_max - INTEGER
1613 The maximum value (in milliseconds) of the round trip timeout. This
1614 is the largest time interval that can elapse between retransmissions.
1615
1616 Default: 60000
1617
1618rto_min - INTEGER
1619 The minimum value (in milliseconds) of the round trip timeout. This
1620 is the smallest time interval the can elapse between retransmissions.
1621
1622 Default: 1000
1623
1624hb_interval - INTEGER
1625 The interval (in milliseconds) between HEARTBEAT chunks. These chunks
1626 are sent at the specified interval on idle paths to probe the state of
1627 a given path between 2 associations.
1628
1629 Default: 30000
1630
1631sack_timeout - INTEGER
1632 The amount of time (in milliseconds) that the implementation will wait
1633 to send a SACK.
1634
1635 Default: 200
1636
1637valid_cookie_life - INTEGER
1638 The default lifetime of the SCTP cookie (in milliseconds). The cookie
1639 is used during association establishment.
1640
1641 Default: 60000
1642
1643cookie_preserve_enable - BOOLEAN
1644 Enable or disable the ability to extend the lifetime of the SCTP cookie
1645 that is used during the establishment phase of SCTP association
1646
1647 1: Enable cookie lifetime extension.
1648 0: Disable
1649
1650 Default: 1
1651
Neil Horman3c681982012-10-24 09:20:03 +00001652cookie_hmac_alg - STRING
1653 Select the hmac algorithm used when generating the cookie value sent by
1654 a listening sctp socket to a connecting client in the INIT-ACK chunk.
1655 Valid values are:
1656 * md5
1657 * sha1
1658 * none
1659 Ability to assign md5 or sha1 as the selected alg is predicated on the
stephen hemminger3b09adc2013-01-03 07:50:29 +00001660 configuration of those algorithms at build time (CONFIG_CRYPTO_MD5 and
Neil Horman3c681982012-10-24 09:20:03 +00001661 CONFIG_CRYPTO_SHA1).
1662
1663 Default: Dependent on configuration. MD5 if available, else SHA1 if
1664 available, else none.
1665
Vlad Yasevich32e8d492008-07-08 16:43:29 -07001666rcvbuf_policy - INTEGER
1667 Determines if the receive buffer is attributed to the socket or to
1668 association. SCTP supports the capability to create multiple
1669 associations on a single socket. When using this capability, it is
1670 possible that a single stalled association that's buffering a lot
1671 of data may block other associations from delivering their data by
1672 consuming all of the receive buffer space. To work around this,
1673 the rcvbuf_policy could be set to attribute the receiver buffer space
1674 to each association instead of the socket. This prevents the described
1675 blocking.
1676
1677 1: rcvbuf space is per association
stephen hemminger3b09adc2013-01-03 07:50:29 +00001678 0: rcvbuf space is per socket
Vlad Yasevich32e8d492008-07-08 16:43:29 -07001679
1680 Default: 0
1681
1682sndbuf_policy - INTEGER
1683 Similar to rcvbuf_policy above, this applies to send buffer space.
1684
1685 1: Send buffer is tracked per association
1686 0: Send buffer is tracked per socket.
1687
1688 Default: 0
1689
1690sctp_mem - vector of 3 INTEGERs: min, pressure, max
1691 Number of pages allowed for queueing by all SCTP sockets.
1692
1693 min: Below this number of pages SCTP is not bothered about its
1694 memory appetite. When amount of memory allocated by SCTP exceeds
1695 this number, SCTP starts to moderate memory usage.
1696
1697 pressure: This value was introduced to follow format of tcp_mem.
1698
1699 max: Number of pages allowed for queueing by all SCTP sockets.
1700
1701 Default is calculated at boot time from amount of available memory.
1702
1703sctp_rmem - vector of 3 INTEGERs: min, default, max
Max Matveeva6e12042011-06-19 22:08:10 +00001704 Only the first value ("min") is used, "default" and "max" are
1705 ignored.
1706
1707 min: Minimal size of receive buffer used by SCTP socket.
1708 It is guaranteed to each SCTP socket (but not association) even
1709 under moderate memory pressure.
1710
1711 Default: 1 page
Vlad Yasevich32e8d492008-07-08 16:43:29 -07001712
1713sctp_wmem - vector of 3 INTEGERs: min, default, max
Max Matveeva6e12042011-06-19 22:08:10 +00001714 Currently this tunable has no effect.
Vlad Yasevich32e8d492008-07-08 16:43:29 -07001715
Bhaskar Dutta72388432009-09-03 17:25:47 +05301716addr_scope_policy - INTEGER
1717 Control IPv4 address scoping - draft-stewart-tsvwg-sctp-ipv4-00
1718
1719 0 - Disable IPv4 address scoping
1720 1 - Enable IPv4 address scoping
1721 2 - Follow draft but allow IPv4 private addresses
1722 3 - Follow draft but allow IPv4 link local addresses
1723
1724 Default: 1
1725
Linus Torvalds1da177e2005-04-16 15:20:36 -07001726
Stephen Hemminger4edc2f32008-07-10 16:50:26 -07001727/proc/sys/net/core/*
Shan Weic60f6aa2012-04-26 16:52:52 +00001728 Please see: Documentation/sysctl/net.txt for descriptions of these entries.
Wang Tinggong705efc32009-05-14 22:49:36 +00001729
Linus Torvalds1da177e2005-04-16 15:20:36 -07001730
Stephen Hemminger4edc2f32008-07-10 16:50:26 -07001731/proc/sys/net/unix/*
Wang Tinggong705efc32009-05-14 22:49:36 +00001732max_dgram_qlen - INTEGER
1733 The maximum length of dgram socket receive queue
1734
1735 Default: 10
1736
1737
1738UNDOCUMENTED:
Stephen Hemminger4edc2f32008-07-10 16:50:26 -07001739
1740/proc/sys/net/irda/*
1741 fast_poll_increase FIXME
1742 warn_noreply_time FIXME
1743 discovery_slots FIXME
1744 slot_timeout FIXME
1745 max_baud_rate FIXME
1746 discovery_timeout FIXME
1747 lap_keepalive_time FIXME
1748 max_noreply_time FIXME
1749 max_tx_data_size FIXME
1750 max_tx_window FIXME
1751 min_tx_turn_time FIXME