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