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