1/proc/sys/net/ipv4/* Variables: 2 3ip_forward - BOOLEAN 4 0 - disabled (default) 5 not 0 - enabled 6 7 Forward Packets between interfaces. 8 9 This variable is special, its change resets all configuration 10 parameters to their default state (RFC1122 for hosts, RFC1812 11 for routers) 12 13ip_default_ttl - INTEGER 14 Default value of TTL field (Time To Live) for outgoing (but not 15 forwarded) IP packets. Should be between 1 and 255 inclusive. 16 Default: 64 (as recommended by RFC1700) 17 18ip_no_pmtu_disc - INTEGER 19 Disable Path MTU Discovery. If enabled in mode 1 and a 20 fragmentation-required ICMP is received, the PMTU to this 21 destination will be set to min_pmtu (see below). You will need 22 to raise min_pmtu to the smallest interface MTU on your system 23 manually if you want to avoid locally generated fragments. 24 25 In mode 2 incoming Path MTU Discovery messages will be 26 discarded. Outgoing frames are handled the same as in mode 1, 27 implicitly setting IP_PMTUDISC_DONT on every created socket. 28 29 Mode 3 is a hardened pmtu discover mode. The kernel will only 30 accept fragmentation-needed errors if the underlying protocol 31 can verify them besides a plain socket lookup. Current 32 protocols for which pmtu events will be honored are TCP, SCTP 33 and DCCP as they verify e.g. the sequence number or the 34 association. This mode should not be enabled globally but is 35 only intended to secure e.g. name servers in namespaces where 36 TCP path mtu must still work but path MTU information of other 37 protocols should be discarded. If enabled globally this mode 38 could break other protocols. 39 40 Possible values: 0-3 41 Default: FALSE 42 43min_pmtu - INTEGER 44 default 552 - minimum discovered Path MTU 45 46ip_forward_use_pmtu - BOOLEAN 47 By default we don't trust protocol path MTUs while forwarding 48 because they could be easily forged and can lead to unwanted 49 fragmentation by the router. 50 You only need to enable this if you have user-space software 51 which tries to discover path mtus by itself and depends on the 52 kernel honoring this information. This is normally not the 53 case. 54 Default: 0 (disabled) 55 Possible values: 56 0 - disabled 57 1 - enabled 58 59fwmark_reflect - BOOLEAN 60 Controls the fwmark of kernel-generated IPv4 reply packets that are not 61 associated with a socket for example, TCP RSTs or ICMP echo replies). 62 If unset, these packets have a fwmark of zero. If set, they have the 63 fwmark of the packet they are replying to. 64 Default: 0 65 66fib_multipath_use_neigh - BOOLEAN 67 Use status of existing neighbor entry when determining nexthop for 68 multipath routes. If disabled, neighbor information is not used and 69 packets could be directed to a failed nexthop. Only valid for kernels 70 built with CONFIG_IP_ROUTE_MULTIPATH enabled. 71 Default: 0 (disabled) 72 Possible values: 73 0 - disabled 74 1 - enabled 75 76fib_multipath_hash_policy - INTEGER 77 Controls which hash policy to use for multipath routes. Only valid 78 for kernels built with CONFIG_IP_ROUTE_MULTIPATH enabled. 79 Default: 0 (Layer 3) 80 Possible values: 81 0 - Layer 3 82 1 - Layer 4 83 84ip_forward_update_priority - INTEGER 85 Whether to update SKB priority from "TOS" field in IPv4 header after it 86 is forwarded. The new SKB priority is mapped from TOS field value 87 according to an rt_tos2priority table (see e.g. man tc-prio). 88 Default: 1 (Update priority.) 89 Possible values: 90 0 - Do not update priority. 91 1 - Update priority. 92 93route/max_size - INTEGER 94 Maximum number of routes allowed in the kernel. Increase 95 this when using large numbers of interfaces and/or routes. 96 From linux kernel 3.6 onwards, this is deprecated for ipv4 97 as route cache is no longer used. 98 99neigh/default/gc_thresh1 - INTEGER 100 Minimum number of entries to keep. Garbage collector will not 101 purge entries if there are fewer than this number. 102 Default: 128 103 104neigh/default/gc_thresh2 - INTEGER 105 Threshold when garbage collector becomes more aggressive about 106 purging entries. Entries older than 5 seconds will be cleared 107 when over this number. 108 Default: 512 109 110neigh/default/gc_thresh3 - INTEGER 111 Maximum number of neighbor entries allowed. Increase this 112 when using large numbers of interfaces and when communicating 113 with large numbers of directly-connected peers. 114 Default: 1024 115 116neigh/default/unres_qlen_bytes - INTEGER 117 The maximum number of bytes which may be used by packets 118 queued for each unresolved address by other network layers. 119 (added in linux 3.3) 120 Setting negative value is meaningless and will return error. 121 Default: SK_WMEM_MAX, (same as net.core.wmem_default). 122 Exact value depends on architecture and kernel options, 123 but should be enough to allow queuing 256 packets 124 of medium size. 125 126neigh/default/unres_qlen - INTEGER 127 The maximum number of packets which may be queued for each 128 unresolved address by other network layers. 129 (deprecated in linux 3.3) : use unres_qlen_bytes instead. 130 Prior to linux 3.3, the default value is 3 which may cause 131 unexpected packet loss. The current default value is calculated 132 according to default value of unres_qlen_bytes and true size of 133 packet. 134 Default: 101 135 136mtu_expires - INTEGER 137 Time, in seconds, that cached PMTU information is kept. 138 139min_adv_mss - INTEGER 140 The advertised MSS depends on the first hop route MTU, but will 141 never be lower than this setting. 142 143IP Fragmentation: 144 145ipfrag_high_thresh - LONG INTEGER 146 Maximum memory used to reassemble IP fragments. 147 148ipfrag_low_thresh - LONG INTEGER 149 (Obsolete since linux-4.17) 150 Maximum memory used to reassemble IP fragments before the kernel 151 begins to remove incomplete fragment queues to free up resources. 152 The kernel still accepts new fragments for defragmentation. 153 154ipfrag_time - INTEGER 155 Time in seconds to keep an IP fragment in memory. 156 157ipfrag_max_dist - INTEGER 158 ipfrag_max_dist is a non-negative integer value which defines the 159 maximum "disorder" which is allowed among fragments which share a 160 common IP source address. Note that reordering of packets is 161 not unusual, but if a large number of fragments arrive from a source 162 IP address while a particular fragment queue remains incomplete, it 163 probably indicates that one or more fragments belonging to that queue 164 have been lost. When ipfrag_max_dist is positive, an additional check 165 is done on fragments before they are added to a reassembly queue - if 166 ipfrag_max_dist (or more) fragments have arrived from a particular IP 167 address between additions to any IP fragment queue using that source 168 address, it's presumed that one or more fragments in the queue are 169 lost. The existing fragment queue will be dropped, and a new one 170 started. An ipfrag_max_dist value of zero disables this check. 171 172 Using a very small value, e.g. 1 or 2, for ipfrag_max_dist can 173 result in unnecessarily dropping fragment queues when normal 174 reordering of packets occurs, which could lead to poor application 175 performance. Using a very large value, e.g. 50000, increases the 176 likelihood of incorrectly reassembling IP fragments that originate 177 from different IP datagrams, which could result in data corruption. 178 Default: 64 179 180INET peer storage: 181 182inet_peer_threshold - INTEGER 183 The approximate size of the storage. Starting from this threshold 184 entries will be thrown aggressively. This threshold also determines 185 entries' time-to-live and time intervals between garbage collection 186 passes. More entries, less time-to-live, less GC interval. 187 188inet_peer_minttl - INTEGER 189 Minimum time-to-live of entries. Should be enough to cover fragment 190 time-to-live on the reassembling side. This minimum time-to-live is 191 guaranteed if the pool size is less than inet_peer_threshold. 192 Measured in seconds. 193 194inet_peer_maxttl - INTEGER 195 Maximum time-to-live of entries. Unused entries will expire after 196 this period of time if there is no memory pressure on the pool (i.e. 197 when the number of entries in the pool is very small). 198 Measured in seconds. 199 200TCP variables: 201 202somaxconn - INTEGER 203 Limit of socket listen() backlog, known in userspace as SOMAXCONN. 204 Defaults to 128. See also tcp_max_syn_backlog for additional tuning 205 for TCP sockets. 206 207tcp_abort_on_overflow - BOOLEAN 208 If listening service is too slow to accept new connections, 209 reset them. Default state is FALSE. It means that if overflow 210 occurred due to a burst, connection will recover. Enable this 211 option _only_ if you are really sure that listening daemon 212 cannot be tuned to accept connections faster. Enabling this 213 option can harm clients of your server. 214 215tcp_adv_win_scale - INTEGER 216 Count buffering overhead as bytes/2^tcp_adv_win_scale 217 (if tcp_adv_win_scale > 0) or bytes-bytes/2^(-tcp_adv_win_scale), 218 if it is <= 0. 219 Possible values are [-31, 31], inclusive. 220 Default: 1 221 222tcp_allowed_congestion_control - STRING 223 Show/set the congestion control choices available to non-privileged 224 processes. The list is a subset of those listed in 225 tcp_available_congestion_control. 226 Default is "reno" and the default setting (tcp_congestion_control). 227 228tcp_app_win - INTEGER 229 Reserve max(window/2^tcp_app_win, mss) of window for application 230 buffer. Value 0 is special, it means that nothing is reserved. 231 Default: 31 232 233tcp_autocorking - BOOLEAN 234 Enable TCP auto corking : 235 When applications do consecutive small write()/sendmsg() system calls, 236 we try to coalesce these small writes as much as possible, to lower 237 total amount of sent packets. This is done if at least one prior 238 packet for the flow is waiting in Qdisc queues or device transmit 239 queue. Applications can still use TCP_CORK for optimal behavior 240 when they know how/when to uncork their sockets. 241 Default : 1 242 243tcp_available_congestion_control - STRING 244 Shows the available congestion control choices that are registered. 245 More congestion control algorithms may be available as modules, 246 but not loaded. 247 248tcp_base_mss - INTEGER 249 The initial value of search_low to be used by the packetization layer 250 Path MTU discovery (MTU probing). If MTU probing is enabled, 251 this is the initial MSS used by the connection. 252 253tcp_congestion_control - STRING 254 Set the congestion control algorithm to be used for new 255 connections. The algorithm "reno" is always available, but 256 additional choices may be available based on kernel configuration. 257 Default is set as part of kernel configuration. 258 For passive connections, the listener congestion control choice 259 is inherited. 260 [see setsockopt(listenfd, SOL_TCP, TCP_CONGESTION, "name" ...) ] 261 262tcp_dsack - BOOLEAN 263 Allows TCP to send "duplicate" SACKs. 264 265tcp_early_retrans - INTEGER 266 Tail loss probe (TLP) converts RTOs occurring due to tail 267 losses into fast recovery (draft-ietf-tcpm-rack). Note that 268 TLP requires RACK to function properly (see tcp_recovery below) 269 Possible values: 270 0 disables TLP 271 3 or 4 enables TLP 272 Default: 3 273 274tcp_ecn - INTEGER 275 Control use of Explicit Congestion Notification (ECN) by TCP. 276 ECN is used only when both ends of the TCP connection indicate 277 support for it. This feature is useful in avoiding losses due 278 to congestion by allowing supporting routers to signal 279 congestion before having to drop packets. 280 Possible values are: 281 0 Disable ECN. Neither initiate nor accept ECN. 282 1 Enable ECN when requested by incoming connections and 283 also request ECN on outgoing connection attempts. 284 2 Enable ECN when requested by incoming connections 285 but do not request ECN on outgoing connections. 286 Default: 2 287 288tcp_ecn_fallback - BOOLEAN 289 If the kernel detects that ECN connection misbehaves, enable fall 290 back to non-ECN. Currently, this knob implements the fallback 291 from RFC3168, section 6.1.1.1., but we reserve that in future, 292 additional detection mechanisms could be implemented under this 293 knob. The value is not used, if tcp_ecn or per route (or congestion 294 control) ECN settings are disabled. 295 Default: 1 (fallback enabled) 296 297tcp_fack - BOOLEAN 298 This is a legacy option, it has no effect anymore. 299 300tcp_fin_timeout - INTEGER 301 The length of time an orphaned (no longer referenced by any 302 application) connection will remain in the FIN_WAIT_2 state 303 before it is aborted at the local end. While a perfectly 304 valid "receive only" state for an un-orphaned connection, an 305 orphaned connection in FIN_WAIT_2 state could otherwise wait 306 forever for the remote to close its end of the connection. 307 Cf. tcp_max_orphans 308 Default: 60 seconds 309 310tcp_frto - INTEGER 311 Enables Forward RTO-Recovery (F-RTO) defined in RFC5682. 312 F-RTO is an enhanced recovery algorithm for TCP retransmission 313 timeouts. It is particularly beneficial in networks where the 314 RTT fluctuates (e.g., wireless). F-RTO is sender-side only 315 modification. It does not require any support from the peer. 316 317 By default it's enabled with a non-zero value. 0 disables F-RTO. 318 319tcp_invalid_ratelimit - INTEGER 320 Limit the maximal rate for sending duplicate acknowledgments 321 in response to incoming TCP packets that are for an existing 322 connection but that are invalid due to any of these reasons: 323 324 (a) out-of-window sequence number, 325 (b) out-of-window acknowledgment number, or 326 (c) PAWS (Protection Against Wrapped Sequence numbers) check failure 327 328 This can help mitigate simple "ack loop" DoS attacks, wherein 329 a buggy or malicious middlebox or man-in-the-middle can 330 rewrite TCP header fields in manner that causes each endpoint 331 to think that the other is sending invalid TCP segments, thus 332 causing each side to send an unterminating stream of duplicate 333 acknowledgments for invalid segments. 334 335 Using 0 disables rate-limiting of dupacks in response to 336 invalid segments; otherwise this value specifies the minimal 337 space between sending such dupacks, in milliseconds. 338 339 Default: 500 (milliseconds). 340 341tcp_keepalive_time - INTEGER 342 How often TCP sends out keepalive messages when keepalive is enabled. 343 Default: 2hours. 344 345tcp_keepalive_probes - INTEGER 346 How many keepalive probes TCP sends out, until it decides that the 347 connection is broken. Default value: 9. 348 349tcp_keepalive_intvl - INTEGER 350 How frequently the probes are send out. Multiplied by 351 tcp_keepalive_probes it is time to kill not responding connection, 352 after probes started. Default value: 75sec i.e. connection 353 will be aborted after ~11 minutes of retries. 354 355tcp_l3mdev_accept - BOOLEAN 356 Enables child sockets to inherit the L3 master device index. 357 Enabling this option allows a "global" listen socket to work 358 across L3 master domains (e.g., VRFs) with connected sockets 359 derived from the listen socket to be bound to the L3 domain in 360 which the packets originated. Only valid when the kernel was 361 compiled with CONFIG_NET_L3_MASTER_DEV. 362 363tcp_low_latency - BOOLEAN 364 This is a legacy option, it has no effect anymore. 365 366tcp_max_orphans - INTEGER 367 Maximal number of TCP sockets not attached to any user file handle, 368 held by system. If this number is exceeded orphaned connections are 369 reset immediately and warning is printed. This limit exists 370 only to prevent simple DoS attacks, you _must_ not rely on this 371 or lower the limit artificially, but rather increase it 372 (probably, after increasing installed memory), 373 if network conditions require more than default value, 374 and tune network services to linger and kill such states 375 more aggressively. Let me to remind again: each orphan eats 376 up to ~64K of unswappable memory. 377 378tcp_max_syn_backlog - INTEGER 379 Maximal number of remembered connection requests, which have not 380 received an acknowledgment from connecting client. 381 The minimal value is 128 for low memory machines, and it will 382 increase in proportion to the memory of machine. 383 If server suffers from overload, try increasing this number. 384 385tcp_max_tw_buckets - INTEGER 386 Maximal number of timewait sockets held by system simultaneously. 387 If this number is exceeded time-wait socket is immediately destroyed 388 and warning is printed. This limit exists only to prevent 389 simple DoS attacks, you _must_ not lower the limit artificially, 390 but rather increase it (probably, after increasing installed memory), 391 if network conditions require more than default value. 392 393tcp_mem - vector of 3 INTEGERs: min, pressure, max 394 min: below this number of pages TCP is not bothered about its 395 memory appetite. 396 397 pressure: when amount of memory allocated by TCP exceeds this number 398 of pages, TCP moderates its memory consumption and enters memory 399 pressure mode, which is exited when memory consumption falls 400 under "min". 401 402 max: number of pages allowed for queueing by all TCP sockets. 403 404 Defaults are calculated at boot time from amount of available 405 memory. 406 407tcp_min_rtt_wlen - INTEGER 408 The window length of the windowed min filter to track the minimum RTT. 409 A shorter window lets a flow more quickly pick up new (higher) 410 minimum RTT when it is moved to a longer path (e.g., due to traffic 411 engineering). A longer window makes the filter more resistant to RTT 412 inflations such as transient congestion. The unit is seconds. 413 Default: 300 414 415tcp_moderate_rcvbuf - BOOLEAN 416 If set, TCP performs receive buffer auto-tuning, attempting to 417 automatically size the buffer (no greater than tcp_rmem[2]) to 418 match the size required by the path for full throughput. Enabled by 419 default. 420 421tcp_mtu_probing - INTEGER 422 Controls TCP Packetization-Layer Path MTU Discovery. Takes three 423 values: 424 0 - Disabled 425 1 - Disabled by default, enabled when an ICMP black hole detected 426 2 - Always enabled, use initial MSS of tcp_base_mss. 427 428tcp_probe_interval - UNSIGNED INTEGER 429 Controls how often to start TCP Packetization-Layer Path MTU 430 Discovery reprobe. The default is reprobing every 10 minutes as 431 per RFC4821. 432 433tcp_probe_threshold - INTEGER 434 Controls when TCP Packetization-Layer Path MTU Discovery probing 435 will stop in respect to the width of search range in bytes. Default 436 is 8 bytes. 437 438tcp_no_metrics_save - BOOLEAN 439 By default, TCP saves various connection metrics in the route cache 440 when the connection closes, so that connections established in the 441 near future can use these to set initial conditions. Usually, this 442 increases overall performance, but may sometimes cause performance 443 degradation. If set, TCP will not cache metrics on closing 444 connections. 445 446tcp_orphan_retries - INTEGER 447 This value influences the timeout of a locally closed TCP connection, 448 when RTO retransmissions remain unacknowledged. 449 See tcp_retries2 for more details. 450 451 The default value is 8. 452 If your machine is a loaded WEB server, 453 you should think about lowering this value, such sockets 454 may consume significant resources. Cf. tcp_max_orphans. 455 456tcp_recovery - INTEGER 457 This value is a bitmap to enable various experimental loss recovery 458 features. 459 460 RACK: 0x1 enables the RACK loss detection for fast detection of lost 461 retransmissions and tail drops. It also subsumes and disables 462 RFC6675 recovery for SACK connections. 463 RACK: 0x2 makes RACK's reordering window static (min_rtt/4). 464 RACK: 0x4 disables RACK's DUPACK threshold heuristic 465 466 Default: 0x1 467 468tcp_reordering - INTEGER 469 Initial reordering level of packets in a TCP stream. 470 TCP stack can then dynamically adjust flow reordering level 471 between this initial value and tcp_max_reordering 472 Default: 3 473 474tcp_max_reordering - INTEGER 475 Maximal reordering level of packets in a TCP stream. 476 300 is a fairly conservative value, but you might increase it 477 if paths are using per packet load balancing (like bonding rr mode) 478 Default: 300 479 480tcp_retrans_collapse - BOOLEAN 481 Bug-to-bug compatibility with some broken printers. 482 On retransmit try to send bigger packets to work around bugs in 483 certain TCP stacks. 484 485tcp_retries1 - INTEGER 486 This value influences the time, after which TCP decides, that 487 something is wrong due to unacknowledged RTO retransmissions, 488 and reports this suspicion to the network layer. 489 See tcp_retries2 for more details. 490 491 RFC 1122 recommends at least 3 retransmissions, which is the 492 default. 493 494tcp_retries2 - INTEGER 495 This value influences the timeout of an alive TCP connection, 496 when RTO retransmissions remain unacknowledged. 497 Given a value of N, a hypothetical TCP connection following 498 exponential backoff with an initial RTO of TCP_RTO_MIN would 499 retransmit N times before killing the connection at the (N+1)th RTO. 500 501 The default value of 15 yields a hypothetical timeout of 924.6 502 seconds and is a lower bound for the effective timeout. 503 TCP will effectively time out at the first RTO which exceeds the 504 hypothetical timeout. 505 506 RFC 1122 recommends at least 100 seconds for the timeout, 507 which corresponds to a value of at least 8. 508 509tcp_rfc1337 - BOOLEAN 510 If set, the TCP stack behaves conforming to RFC1337. If unset, 511 we are not conforming to RFC, but prevent TCP TIME_WAIT 512 assassination. 513 Default: 0 514 515tcp_rmem - vector of 3 INTEGERs: min, default, max 516 min: Minimal size of receive buffer used by TCP sockets. 517 It is guaranteed to each TCP socket, even under moderate memory 518 pressure. 519 Default: 4K 520 521 default: initial size of receive buffer used by TCP sockets. 522 This value overrides net.core.rmem_default used by other protocols. 523 Default: 87380 bytes. This value results in window of 65535 with 524 default setting of tcp_adv_win_scale and tcp_app_win:0 and a bit 525 less for default tcp_app_win. See below about these variables. 526 527 max: maximal size of receive buffer allowed for automatically 528 selected receiver buffers for TCP socket. This value does not override 529 net.core.rmem_max. Calling setsockopt() with SO_RCVBUF disables 530 automatic tuning of that socket's receive buffer size, in which 531 case this value is ignored. 532 Default: between 87380B and 6MB, depending on RAM size. 533 534tcp_sack - BOOLEAN 535 Enable select acknowledgments (SACKS). 536 537tcp_comp_sack_delay_ns - LONG INTEGER 538 TCP tries to reduce number of SACK sent, using a timer 539 based on 5% of SRTT, capped by this sysctl, in nano seconds. 540 The default is 1ms, based on TSO autosizing period. 541 542 Default : 1,000,000 ns (1 ms) 543 544tcp_comp_sack_nr - INTEGER 545 Max numer of SACK that can be compressed. 546 Using 0 disables SACK compression. 547 548 Detault : 44 549 550tcp_slow_start_after_idle - BOOLEAN 551 If set, provide RFC2861 behavior and time out the congestion 552 window after an idle period. An idle period is defined at 553 the current RTO. If unset, the congestion window will not 554 be timed out after an idle period. 555 Default: 1 556 557tcp_stdurg - BOOLEAN 558 Use the Host requirements interpretation of the TCP urgent pointer field. 559 Most hosts use the older BSD interpretation, so if you turn this on 560 Linux might not communicate correctly with them. 561 Default: FALSE 562 563tcp_synack_retries - INTEGER 564 Number of times SYNACKs for a passive TCP connection attempt will 565 be retransmitted. Should not be higher than 255. Default value 566 is 5, which corresponds to 31seconds till the last retransmission 567 with the current initial RTO of 1second. With this the final timeout 568 for a passive TCP connection will happen after 63seconds. 569 570tcp_syncookies - BOOLEAN 571 Only valid when the kernel was compiled with CONFIG_SYN_COOKIES 572 Send out syncookies when the syn backlog queue of a socket 573 overflows. This is to prevent against the common 'SYN flood attack' 574 Default: 1 575 576 Note, that syncookies is fallback facility. 577 It MUST NOT be used to help highly loaded servers to stand 578 against legal connection rate. If you see SYN flood warnings 579 in your logs, but investigation shows that they occur 580 because of overload with legal connections, you should tune 581 another parameters until this warning disappear. 582 See: tcp_max_syn_backlog, tcp_synack_retries, tcp_abort_on_overflow. 583 584 syncookies seriously violate TCP protocol, do not allow 585 to use TCP extensions, can result in serious degradation 586 of some services (f.e. SMTP relaying), visible not by you, 587 but your clients and relays, contacting you. While you see 588 SYN flood warnings in logs not being really flooded, your server 589 is seriously misconfigured. 590 591 If you want to test which effects syncookies have to your 592 network connections you can set this knob to 2 to enable 593 unconditionally generation of syncookies. 594 595tcp_fastopen - INTEGER 596 Enable TCP Fast Open (RFC7413) to send and accept data in the opening 597 SYN packet. 598 599 The client support is enabled by flag 0x1 (on by default). The client 600 then must use sendmsg() or sendto() with the MSG_FASTOPEN flag, 601 rather than connect() to send data in SYN. 602 603 The server support is enabled by flag 0x2 (off by default). Then 604 either enable for all listeners with another flag (0x400) or 605 enable individual listeners via TCP_FASTOPEN socket option with 606 the option value being the length of the syn-data backlog. 607 608 The values (bitmap) are 609 0x1: (client) enables sending data in the opening SYN on the client. 610 0x2: (server) enables the server support, i.e., allowing data in 611 a SYN packet to be accepted and passed to the 612 application before 3-way handshake finishes. 613 0x4: (client) send data in the opening SYN regardless of cookie 614 availability and without a cookie option. 615 0x200: (server) accept data-in-SYN w/o any cookie option present. 616 0x400: (server) enable all listeners to support Fast Open by 617 default without explicit TCP_FASTOPEN socket option. 618 619 Default: 0x1 620 621 Note that that additional client or server features are only 622 effective if the basic support (0x1 and 0x2) are enabled respectively. 623 624tcp_fastopen_blackhole_timeout_sec - INTEGER 625 Initial time period in second to disable Fastopen on active TCP sockets 626 when a TFO firewall blackhole issue happens. 627 This time period will grow exponentially when more blackhole issues 628 get detected right after Fastopen is re-enabled and will reset to 629 initial value when the blackhole issue goes away. 630 0 to disable the blackhole detection. 631 By default, it is set to 1hr. 632 633tcp_syn_retries - INTEGER 634 Number of times initial SYNs for an active TCP connection attempt 635 will be retransmitted. Should not be higher than 127. Default value 636 is 6, which corresponds to 63seconds till the last retransmission 637 with the current initial RTO of 1second. With this the final timeout 638 for an active TCP connection attempt will happen after 127seconds. 639 640tcp_timestamps - INTEGER 641Enable timestamps as defined in RFC1323. 642 0: Disabled. 643 1: Enable timestamps as defined in RFC1323 and use random offset for 644 each connection rather than only using the current time. 645 2: Like 1, but without random offsets. 646 Default: 1 647 648tcp_min_tso_segs - INTEGER 649 Minimal number of segments per TSO frame. 650 Since linux-3.12, TCP does an automatic sizing of TSO frames, 651 depending on flow rate, instead of filling 64Kbytes packets. 652 For specific usages, it's possible to force TCP to build big 653 TSO frames. Note that TCP stack might split too big TSO packets 654 if available window is too small. 655 Default: 2 656 657tcp_pacing_ss_ratio - INTEGER 658 sk->sk_pacing_rate is set by TCP stack using a ratio applied 659 to current rate. (current_rate = cwnd * mss / srtt) 660 If TCP is in slow start, tcp_pacing_ss_ratio is applied 661 to let TCP probe for bigger speeds, assuming cwnd can be 662 doubled every other RTT. 663 Default: 200 664 665tcp_pacing_ca_ratio - INTEGER 666 sk->sk_pacing_rate is set by TCP stack using a ratio applied 667 to current rate. (current_rate = cwnd * mss / srtt) 668 If TCP is in congestion avoidance phase, tcp_pacing_ca_ratio 669 is applied to conservatively probe for bigger throughput. 670 Default: 120 671 672tcp_tso_win_divisor - INTEGER 673 This allows control over what percentage of the congestion window 674 can be consumed by a single TSO frame. 675 The setting of this parameter is a choice between burstiness and 676 building larger TSO frames. 677 Default: 3 678 679tcp_tw_reuse - INTEGER 680 Enable reuse of TIME-WAIT sockets for new connections when it is 681 safe from protocol viewpoint. 682 0 - disable 683 1 - global enable 684 2 - enable for loopback traffic only 685 It should not be changed without advice/request of technical 686 experts. 687 Default: 2 688 689tcp_window_scaling - BOOLEAN 690 Enable window scaling as defined in RFC1323. 691 692tcp_wmem - vector of 3 INTEGERs: min, default, max 693 min: Amount of memory reserved for send buffers for TCP sockets. 694 Each TCP socket has rights to use it due to fact of its birth. 695 Default: 4K 696 697 default: initial size of send buffer used by TCP sockets. This 698 value overrides net.core.wmem_default used by other protocols. 699 It is usually lower than net.core.wmem_default. 700 Default: 16K 701 702 max: Maximal amount of memory allowed for automatically tuned 703 send buffers for TCP sockets. This value does not override 704 net.core.wmem_max. Calling setsockopt() with SO_SNDBUF disables 705 automatic tuning of that socket's send buffer size, in which case 706 this value is ignored. 707 Default: between 64K and 4MB, depending on RAM size. 708 709tcp_notsent_lowat - UNSIGNED INTEGER 710 A TCP socket can control the amount of unsent bytes in its write queue, 711 thanks to TCP_NOTSENT_LOWAT socket option. poll()/select()/epoll() 712 reports POLLOUT events if the amount of unsent bytes is below a per 713 socket value, and if the write queue is not full. sendmsg() will 714 also not add new buffers if the limit is hit. 715 716 This global variable controls the amount of unsent data for 717 sockets not using TCP_NOTSENT_LOWAT. For these sockets, a change 718 to the global variable has immediate effect. 719 720 Default: UINT_MAX (0xFFFFFFFF) 721 722tcp_workaround_signed_windows - BOOLEAN 723 If set, assume no receipt of a window scaling option means the 724 remote TCP is broken and treats the window as a signed quantity. 725 If unset, assume the remote TCP is not broken even if we do 726 not receive a window scaling option from them. 727 Default: 0 728 729tcp_thin_linear_timeouts - BOOLEAN 730 Enable dynamic triggering of linear timeouts for thin streams. 731 If set, a check is performed upon retransmission by timeout to 732 determine if the stream is thin (less than 4 packets in flight). 733 As long as the stream is found to be thin, up to 6 linear 734 timeouts may be performed before exponential backoff mode is 735 initiated. This improves retransmission latency for 736 non-aggressive thin streams, often found to be time-dependent. 737 For more information on thin streams, see 738 Documentation/networking/tcp-thin.txt 739 Default: 0 740 741tcp_limit_output_bytes - INTEGER 742 Controls TCP Small Queue limit per tcp socket. 743 TCP bulk sender tends to increase packets in flight until it 744 gets losses notifications. With SNDBUF autotuning, this can 745 result in a large amount of packets queued on the local machine 746 (e.g.: qdiscs, CPU backlog, or device) hurting latency of other 747 flows, for typical pfifo_fast qdiscs. tcp_limit_output_bytes 748 limits the number of bytes on qdisc or device to reduce artificial 749 RTT/cwnd and reduce bufferbloat. 750 Default: 262144 751 752tcp_challenge_ack_limit - INTEGER 753 Limits number of Challenge ACK sent per second, as recommended 754 in RFC 5961 (Improving TCP's Robustness to Blind In-Window Attacks) 755 Default: 100 756 757UDP variables: 758 759udp_l3mdev_accept - BOOLEAN 760 Enabling this option allows a "global" bound socket to work 761 across L3 master domains (e.g., VRFs) with packets capable of 762 being received regardless of the L3 domain in which they 763 originated. Only valid when the kernel was compiled with 764 CONFIG_NET_L3_MASTER_DEV. 765 766udp_mem - vector of 3 INTEGERs: min, pressure, max 767 Number of pages allowed for queueing by all UDP sockets. 768 769 min: Below this number of pages UDP is not bothered about its 770 memory appetite. When amount of memory allocated by UDP exceeds 771 this number, UDP starts to moderate memory usage. 772 773 pressure: This value was introduced to follow format of tcp_mem. 774 775 max: Number of pages allowed for queueing by all UDP sockets. 776 777 Default is calculated at boot time from amount of available memory. 778 779udp_rmem_min - INTEGER 780 Minimal size of receive buffer used by UDP sockets in moderation. 781 Each UDP socket is able to use the size for receiving data, even if 782 total pages of UDP sockets exceed udp_mem pressure. The unit is byte. 783 Default: 4K 784 785udp_wmem_min - INTEGER 786 Minimal size of send buffer used by UDP sockets in moderation. 787 Each UDP socket is able to use the size for sending data, even if 788 total pages of UDP sockets exceed udp_mem pressure. The unit is byte. 789 Default: 4K 790 791CIPSOv4 Variables: 792 793cipso_cache_enable - BOOLEAN 794 If set, enable additions to and lookups from the CIPSO label mapping 795 cache. If unset, additions are ignored and lookups always result in a 796 miss. However, regardless of the setting the cache is still 797 invalidated when required when means you can safely toggle this on and 798 off and the cache will always be "safe". 799 Default: 1 800 801cipso_cache_bucket_size - INTEGER 802 The CIPSO label cache consists of a fixed size hash table with each 803 hash bucket containing a number of cache entries. This variable limits 804 the number of entries in each hash bucket; the larger the value the 805 more CIPSO label mappings that can be cached. When the number of 806 entries in a given hash bucket reaches this limit adding new entries 807 causes the oldest entry in the bucket to be removed to make room. 808 Default: 10 809 810cipso_rbm_optfmt - BOOLEAN 811 Enable the "Optimized Tag 1 Format" as defined in section 3.4.2.6 of 812 the CIPSO draft specification (see Documentation/netlabel for details). 813 This means that when set the CIPSO tag will be padded with empty 814 categories in order to make the packet data 32-bit aligned. 815 Default: 0 816 817cipso_rbm_structvalid - BOOLEAN 818 If set, do a very strict check of the CIPSO option when 819 ip_options_compile() is called. If unset, relax the checks done during 820 ip_options_compile(). Either way is "safe" as errors are caught else 821 where in the CIPSO processing code but setting this to 0 (False) should 822 result in less work (i.e. it should be faster) but could cause problems 823 with other implementations that require strict checking. 824 Default: 0 825 826IP Variables: 827 828ip_local_port_range - 2 INTEGERS 829 Defines the local port range that is used by TCP and UDP to 830 choose the local port. The first number is the first, the 831 second the last local port number. 832 If possible, it is better these numbers have different parity. 833 (one even and one odd values) 834 The default values are 32768 and 60999 respectively. 835 836ip_local_reserved_ports - list of comma separated ranges 837 Specify the ports which are reserved for known third-party 838 applications. These ports will not be used by automatic port 839 assignments (e.g. when calling connect() or bind() with port 840 number 0). Explicit port allocation behavior is unchanged. 841 842 The format used for both input and output is a comma separated 843 list of ranges (e.g. "1,2-4,10-10" for ports 1, 2, 3, 4 and 844 10). Writing to the file will clear all previously reserved 845 ports and update the current list with the one given in the 846 input. 847 848 Note that ip_local_port_range and ip_local_reserved_ports 849 settings are independent and both are considered by the kernel 850 when determining which ports are available for automatic port 851 assignments. 852 853 You can reserve ports which are not in the current 854 ip_local_port_range, e.g.: 855 856 $ cat /proc/sys/net/ipv4/ip_local_port_range 857 32000 60999 858 $ cat /proc/sys/net/ipv4/ip_local_reserved_ports 859 8080,9148 860 861 although this is redundant. However such a setting is useful 862 if later the port range is changed to a value that will 863 include the reserved ports. 864 865 Default: Empty 866 867ip_unprivileged_port_start - INTEGER 868 This is a per-namespace sysctl. It defines the first 869 unprivileged port in the network namespace. Privileged ports 870 require root or CAP_NET_BIND_SERVICE in order to bind to them. 871 To disable all privileged ports, set this to 0. It may not 872 overlap with the ip_local_reserved_ports range. 873 874 Default: 1024 875 876ip_nonlocal_bind - BOOLEAN 877 If set, allows processes to bind() to non-local IP addresses, 878 which can be quite useful - but may break some applications. 879 Default: 0 880 881ip_dynaddr - BOOLEAN 882 If set non-zero, enables support for dynamic addresses. 883 If set to a non-zero value larger than 1, a kernel log 884 message will be printed when dynamic address rewriting 885 occurs. 886 Default: 0 887 888ip_early_demux - BOOLEAN 889 Optimize input packet processing down to one demux for 890 certain kinds of local sockets. Currently we only do this 891 for established TCP and connected UDP sockets. 892 893 It may add an additional cost for pure routing workloads that 894 reduces overall throughput, in such case you should disable it. 895 Default: 1 896 897tcp_early_demux - BOOLEAN 898 Enable early demux for established TCP sockets. 899 Default: 1 900 901udp_early_demux - BOOLEAN 902 Enable early demux for connected UDP sockets. Disable this if 903 your system could experience more unconnected load. 904 Default: 1 905 906icmp_echo_ignore_all - BOOLEAN 907 If set non-zero, then the kernel will ignore all ICMP ECHO 908 requests sent to it. 909 Default: 0 910 911icmp_echo_ignore_broadcasts - BOOLEAN 912 If set non-zero, then the kernel will ignore all ICMP ECHO and 913 TIMESTAMP requests sent to it via broadcast/multicast. 914 Default: 1 915 916icmp_ratelimit - INTEGER 917 Limit the maximal rates for sending ICMP packets whose type matches 918 icmp_ratemask (see below) to specific targets. 919 0 to disable any limiting, 920 otherwise the minimal space between responses in milliseconds. 921 Note that another sysctl, icmp_msgs_per_sec limits the number 922 of ICMP packets sent on all targets. 923 Default: 1000 924 925icmp_msgs_per_sec - INTEGER 926 Limit maximal number of ICMP packets sent per second from this host. 927 Only messages whose type matches icmp_ratemask (see below) are 928 controlled by this limit. 929 Default: 1000 930 931icmp_msgs_burst - INTEGER 932 icmp_msgs_per_sec controls number of ICMP packets sent per second, 933 while icmp_msgs_burst controls the burst size of these packets. 934 Default: 50 935 936icmp_ratemask - INTEGER 937 Mask made of ICMP types for which rates are being limited. 938 Significant bits: IHGFEDCBA9876543210 939 Default mask: 0000001100000011000 (6168) 940 941 Bit definitions (see include/linux/icmp.h): 942 0 Echo Reply 943 3 Destination Unreachable * 944 4 Source Quench * 945 5 Redirect 946 8 Echo Request 947 B Time Exceeded * 948 C Parameter Problem * 949 D Timestamp Request 950 E Timestamp Reply 951 F Info Request 952 G Info Reply 953 H Address Mask Request 954 I Address Mask Reply 955 956 * These are rate limited by default (see default mask above) 957 958icmp_ignore_bogus_error_responses - BOOLEAN 959 Some routers violate RFC1122 by sending bogus responses to broadcast 960 frames. Such violations are normally logged via a kernel warning. 961 If this is set to TRUE, the kernel will not give such warnings, which 962 will avoid log file clutter. 963 Default: 1 964 965icmp_errors_use_inbound_ifaddr - BOOLEAN 966 967 If zero, icmp error messages are sent with the primary address of 968 the exiting interface. 969 970 If non-zero, the message will be sent with the primary address of 971 the interface that received the packet that caused the icmp error. 972 This is the behaviour network many administrators will expect from 973 a router. And it can make debugging complicated network layouts 974 much easier. 975 976 Note that if no primary address exists for the interface selected, 977 then the primary address of the first non-loopback interface that 978 has one will be used regardless of this setting. 979 980 Default: 0 981 982igmp_max_memberships - INTEGER 983 Change the maximum number of multicast groups we can subscribe to. 984 Default: 20 985 986 Theoretical maximum value is bounded by having to send a membership 987 report in a single datagram (i.e. the report can't span multiple 988 datagrams, or risk confusing the switch and leaving groups you don't 989 intend to). 990 991 The number of supported groups 'M' is bounded by the number of group 992 report entries you can fit into a single datagram of 65535 bytes. 993 994 M = 65536-sizeof (ip header)/(sizeof(Group record)) 995 996 Group records are variable length, with a minimum of 12 bytes. 997 So net.ipv4.igmp_max_memberships should not be set higher than: 998 999 (65536-24) / 12 = 5459 1000 1001 The value 5459 assumes no IP header options, so in practice 1002 this number may be lower. 1003 1004igmp_max_msf - INTEGER 1005 Maximum number of addresses allowed in the source filter list for a 1006 multicast group. 1007 Default: 10 1008 1009igmp_qrv - INTEGER 1010 Controls the IGMP query robustness variable (see RFC2236 8.1). 1011 Default: 2 (as specified by RFC2236 8.1) 1012 Minimum: 1 (as specified by RFC6636 4.5) 1013 1014force_igmp_version - INTEGER 1015 0 - (default) No enforcement of a IGMP version, IGMPv1/v2 fallback 1016 allowed. Will back to IGMPv3 mode again if all IGMPv1/v2 Querier 1017 Present timer expires. 1018 1 - Enforce to use IGMP version 1. Will also reply IGMPv1 report if 1019 receive IGMPv2/v3 query. 1020 2 - Enforce to use IGMP version 2. Will fallback to IGMPv1 if receive 1021 IGMPv1 query message. Will reply report if receive IGMPv3 query. 1022 3 - Enforce to use IGMP version 3. The same react with default 0. 1023 1024 Note: this is not the same with force_mld_version because IGMPv3 RFC3376 1025 Security Considerations does not have clear description that we could 1026 ignore other version messages completely as MLDv2 RFC3810. So make 1027 this value as default 0 is recommended. 1028 1029conf/interface/* changes special settings per interface (where 1030"interface" is the name of your network interface) 1031 1032conf/all/* is special, changes the settings for all interfaces 1033 1034log_martians - BOOLEAN 1035 Log packets with impossible addresses to kernel log. 1036 log_martians for the interface will be enabled if at least one of 1037 conf/{all,interface}/log_martians is set to TRUE, 1038 it will be disabled otherwise 1039 1040accept_redirects - BOOLEAN 1041 Accept ICMP redirect messages. 1042 accept_redirects for the interface will be enabled if: 1043 - both conf/{all,interface}/accept_redirects are TRUE in the case 1044 forwarding for the interface is enabled 1045 or 1046 - at least one of conf/{all,interface}/accept_redirects is TRUE in the 1047 case forwarding for the interface is disabled 1048 accept_redirects for the interface will be disabled otherwise 1049 default TRUE (host) 1050 FALSE (router) 1051 1052forwarding - BOOLEAN 1053 Enable IP forwarding on this interface. This controls whether packets 1054 received _on_ this interface can be forwarded. 1055 1056mc_forwarding - BOOLEAN 1057 Do multicast routing. The kernel needs to be compiled with CONFIG_MROUTE 1058 and a multicast routing daemon is required. 1059 conf/all/mc_forwarding must also be set to TRUE to enable multicast 1060 routing for the interface 1061 1062medium_id - INTEGER 1063 Integer value used to differentiate the devices by the medium they 1064 are attached to. Two devices can have different id values when 1065 the broadcast packets are received only on one of them. 1066 The default value 0 means that the device is the only interface 1067 to its medium, value of -1 means that medium is not known. 1068 1069 Currently, it is used to change the proxy_arp behavior: 1070 the proxy_arp feature is enabled for packets forwarded between 1071 two devices attached to different media. 1072 1073proxy_arp - BOOLEAN 1074 Do proxy arp. 1075 proxy_arp for the interface will be enabled if at least one of 1076 conf/{all,interface}/proxy_arp is set to TRUE, 1077 it will be disabled otherwise 1078 1079proxy_arp_pvlan - BOOLEAN 1080 Private VLAN proxy arp. 1081 Basically allow proxy arp replies back to the same interface 1082 (from which the ARP request/solicitation was received). 1083 1084 This is done to support (ethernet) switch features, like RFC 1085 3069, where the individual ports are NOT allowed to 1086 communicate with each other, but they are allowed to talk to 1087 the upstream router. As described in RFC 3069, it is possible 1088 to allow these hosts to communicate through the upstream 1089 router by proxy_arp'ing. Don't need to be used together with 1090 proxy_arp. 1091 1092 This technology is known by different names: 1093 In RFC 3069 it is called VLAN Aggregation. 1094 Cisco and Allied Telesyn call it Private VLAN. 1095 Hewlett-Packard call it Source-Port filtering or port-isolation. 1096 Ericsson call it MAC-Forced Forwarding (RFC Draft). 1097 1098shared_media - BOOLEAN 1099 Send(router) or accept(host) RFC1620 shared media redirects. 1100 Overrides secure_redirects. 1101 shared_media for the interface will be enabled if at least one of 1102 conf/{all,interface}/shared_media is set to TRUE, 1103 it will be disabled otherwise 1104 default TRUE 1105 1106secure_redirects - BOOLEAN 1107 Accept ICMP redirect messages only to gateways listed in the 1108 interface's current gateway list. Even if disabled, RFC1122 redirect 1109 rules still apply. 1110 Overridden by shared_media. 1111 secure_redirects for the interface will be enabled if at least one of 1112 conf/{all,interface}/secure_redirects is set to TRUE, 1113 it will be disabled otherwise 1114 default TRUE 1115 1116send_redirects - BOOLEAN 1117 Send redirects, if router. 1118 send_redirects for the interface will be enabled if at least one of 1119 conf/{all,interface}/send_redirects is set to TRUE, 1120 it will be disabled otherwise 1121 Default: TRUE 1122 1123bootp_relay - BOOLEAN 1124 Accept packets with source address 0.b.c.d destined 1125 not to this host as local ones. It is supposed, that 1126 BOOTP relay daemon will catch and forward such packets. 1127 conf/all/bootp_relay must also be set to TRUE to enable BOOTP relay 1128 for the interface 1129 default FALSE 1130 Not Implemented Yet. 1131 1132accept_source_route - BOOLEAN 1133 Accept packets with SRR option. 1134 conf/all/accept_source_route must also be set to TRUE to accept packets 1135 with SRR option on the interface 1136 default TRUE (router) 1137 FALSE (host) 1138 1139accept_local - BOOLEAN 1140 Accept packets with local source addresses. In combination with 1141 suitable routing, this can be used to direct packets between two 1142 local interfaces over the wire and have them accepted properly. 1143 default FALSE 1144 1145route_localnet - BOOLEAN 1146 Do not consider loopback addresses as martian source or destination 1147 while routing. This enables the use of 127/8 for local routing purposes. 1148 default FALSE 1149 1150rp_filter - INTEGER 1151 0 - No source validation. 1152 1 - Strict mode as defined in RFC3704 Strict Reverse Path 1153 Each incoming packet is tested against the FIB and if the interface 1154 is not the best reverse path the packet check will fail. 1155 By default failed packets are discarded. 1156 2 - Loose mode as defined in RFC3704 Loose Reverse Path 1157 Each incoming packet's source address is also tested against the FIB 1158 and if the source address is not reachable via any interface 1159 the packet check will fail. 1160 1161 Current recommended practice in RFC3704 is to enable strict mode 1162 to prevent IP spoofing from DDos attacks. If using asymmetric routing 1163 or other complicated routing, then loose mode is recommended. 1164 1165 The max value from conf/{all,interface}/rp_filter is used 1166 when doing source validation on the {interface}. 1167 1168 Default value is 0. Note that some distributions enable it 1169 in startup scripts. 1170 1171arp_filter - BOOLEAN 1172 1 - Allows you to have multiple network interfaces on the same 1173 subnet, and have the ARPs for each interface be answered 1174 based on whether or not the kernel would route a packet from 1175 the ARP'd IP out that interface (therefore you must use source 1176 based routing for this to work). In other words it allows control 1177 of which cards (usually 1) will respond to an arp request. 1178 1179 0 - (default) The kernel can respond to arp requests with addresses 1180 from other interfaces. This may seem wrong but it usually makes 1181 sense, because it increases the chance of successful communication. 1182 IP addresses are owned by the complete host on Linux, not by 1183 particular interfaces. Only for more complex setups like load- 1184 balancing, does this behaviour cause problems. 1185 1186 arp_filter for the interface will be enabled if at least one of 1187 conf/{all,interface}/arp_filter is set to TRUE, 1188 it will be disabled otherwise 1189 1190arp_announce - INTEGER 1191 Define different restriction levels for announcing the local 1192 source IP address from IP packets in ARP requests sent on 1193 interface: 1194 0 - (default) Use any local address, configured on any interface 1195 1 - Try to avoid local addresses that are not in the target's 1196 subnet for this interface. This mode is useful when target 1197 hosts reachable via this interface require the source IP 1198 address in ARP requests to be part of their logical network 1199 configured on the receiving interface. When we generate the 1200 request we will check all our subnets that include the 1201 target IP and will preserve the source address if it is from 1202 such subnet. If there is no such subnet we select source 1203 address according to the rules for level 2. 1204 2 - Always use the best local address for this target. 1205 In this mode we ignore the source address in the IP packet 1206 and try to select local address that we prefer for talks with 1207 the target host. Such local address is selected by looking 1208 for primary IP addresses on all our subnets on the outgoing 1209 interface that include the target IP address. If no suitable 1210 local address is found we select the first local address 1211 we have on the outgoing interface or on all other interfaces, 1212 with the hope we will receive reply for our request and 1213 even sometimes no matter the source IP address we announce. 1214 1215 The max value from conf/{all,interface}/arp_announce is used. 1216 1217 Increasing the restriction level gives more chance for 1218 receiving answer from the resolved target while decreasing 1219 the level announces more valid sender's information. 1220 1221arp_ignore - INTEGER 1222 Define different modes for sending replies in response to 1223 received ARP requests that resolve local target IP addresses: 1224 0 - (default): reply for any local target IP address, configured 1225 on any interface 1226 1 - reply only if the target IP address is local address 1227 configured on the incoming interface 1228 2 - reply only if the target IP address is local address 1229 configured on the incoming interface and both with the 1230 sender's IP address are part from same subnet on this interface 1231 3 - do not reply for local addresses configured with scope host, 1232 only resolutions for global and link addresses are replied 1233 4-7 - reserved 1234 8 - do not reply for all local addresses 1235 1236 The max value from conf/{all,interface}/arp_ignore is used 1237 when ARP request is received on the {interface} 1238 1239arp_notify - BOOLEAN 1240 Define mode for notification of address and device changes. 1241 0 - (default): do nothing 1242 1 - Generate gratuitous arp requests when device is brought up 1243 or hardware address changes. 1244 1245arp_accept - BOOLEAN 1246 Define behavior for gratuitous ARP frames who's IP is not 1247 already present in the ARP table: 1248 0 - don't create new entries in the ARP table 1249 1 - create new entries in the ARP table 1250 1251 Both replies and requests type gratuitous arp will trigger the 1252 ARP table to be updated, if this setting is on. 1253 1254 If the ARP table already contains the IP address of the 1255 gratuitous arp frame, the arp table will be updated regardless 1256 if this setting is on or off. 1257 1258mcast_solicit - INTEGER 1259 The maximum number of multicast probes in INCOMPLETE state, 1260 when the associated hardware address is unknown. Defaults 1261 to 3. 1262 1263ucast_solicit - INTEGER 1264 The maximum number of unicast probes in PROBE state, when 1265 the hardware address is being reconfirmed. Defaults to 3. 1266 1267app_solicit - INTEGER 1268 The maximum number of probes to send to the user space ARP daemon 1269 via netlink before dropping back to multicast probes (see 1270 mcast_resolicit). Defaults to 0. 1271 1272mcast_resolicit - INTEGER 1273 The maximum number of multicast probes after unicast and 1274 app probes in PROBE state. Defaults to 0. 1275 1276disable_policy - BOOLEAN 1277 Disable IPSEC policy (SPD) for this interface 1278 1279disable_xfrm - BOOLEAN 1280 Disable IPSEC encryption on this interface, whatever the policy 1281 1282igmpv2_unsolicited_report_interval - INTEGER 1283 The interval in milliseconds in which the next unsolicited 1284 IGMPv1 or IGMPv2 report retransmit will take place. 1285 Default: 10000 (10 seconds) 1286 1287igmpv3_unsolicited_report_interval - INTEGER 1288 The interval in milliseconds in which the next unsolicited 1289 IGMPv3 report retransmit will take place. 1290 Default: 1000 (1 seconds) 1291 1292promote_secondaries - BOOLEAN 1293 When a primary IP address is removed from this interface 1294 promote a corresponding secondary IP address instead of 1295 removing all the corresponding secondary IP addresses. 1296 1297drop_unicast_in_l2_multicast - BOOLEAN 1298 Drop any unicast IP packets that are received in link-layer 1299 multicast (or broadcast) frames. 1300 This behavior (for multicast) is actually a SHOULD in RFC 1301 1122, but is disabled by default for compatibility reasons. 1302 Default: off (0) 1303 1304drop_gratuitous_arp - BOOLEAN 1305 Drop all gratuitous ARP frames, for example if there's a known 1306 good ARP proxy on the network and such frames need not be used 1307 (or in the case of 802.11, must not be used to prevent attacks.) 1308 Default: off (0) 1309 1310 1311tag - INTEGER 1312 Allows you to write a number, which can be used as required. 1313 Default value is 0. 1314 1315xfrm4_gc_thresh - INTEGER 1316 The threshold at which we will start garbage collecting for IPv4 1317 destination cache entries. At twice this value the system will 1318 refuse new allocations. 1319 1320igmp_link_local_mcast_reports - BOOLEAN 1321 Enable IGMP reports for link local multicast groups in the 1322 224.0.0.X range. 1323 Default TRUE 1324 1325Alexey Kuznetsov. 1326kuznet@ms2.inr.ac.ru 1327 1328Updated by: 1329Andi Kleen 1330ak@muc.de 1331Nicolas Delon 1332delon.nicolas@wanadoo.fr 1333 1334 1335 1336 1337/proc/sys/net/ipv6/* Variables: 1338 1339IPv6 has no global variables such as tcp_*. tcp_* settings under ipv4/ also 1340apply to IPv6 [XXX?]. 1341 1342bindv6only - BOOLEAN 1343 Default value for IPV6_V6ONLY socket option, 1344 which restricts use of the IPv6 socket to IPv6 communication 1345 only. 1346 TRUE: disable IPv4-mapped address feature 1347 FALSE: enable IPv4-mapped address feature 1348 1349 Default: FALSE (as specified in RFC3493) 1350 1351flowlabel_consistency - BOOLEAN 1352 Protect the consistency (and unicity) of flow label. 1353 You have to disable it to use IPV6_FL_F_REFLECT flag on the 1354 flow label manager. 1355 TRUE: enabled 1356 FALSE: disabled 1357 Default: TRUE 1358 1359auto_flowlabels - INTEGER 1360 Automatically generate flow labels based on a flow hash of the 1361 packet. This allows intermediate devices, such as routers, to 1362 identify packet flows for mechanisms like Equal Cost Multipath 1363 Routing (see RFC 6438). 1364 0: automatic flow labels are completely disabled 1365 1: automatic flow labels are enabled by default, they can be 1366 disabled on a per socket basis using the IPV6_AUTOFLOWLABEL 1367 socket option 1368 2: automatic flow labels are allowed, they may be enabled on a 1369 per socket basis using the IPV6_AUTOFLOWLABEL socket option 1370 3: automatic flow labels are enabled and enforced, they cannot 1371 be disabled by the socket option 1372 Default: 1 1373 1374flowlabel_state_ranges - BOOLEAN 1375 Split the flow label number space into two ranges. 0-0x7FFFF is 1376 reserved for the IPv6 flow manager facility, 0x80000-0xFFFFF 1377 is reserved for stateless flow labels as described in RFC6437. 1378 TRUE: enabled 1379 FALSE: disabled 1380 Default: true 1381 1382flowlabel_reflect - BOOLEAN 1383 Automatically reflect the flow label. Needed for Path MTU 1384 Discovery to work with Equal Cost Multipath Routing in anycast 1385 environments. See RFC 7690 and: 1386 https://tools.ietf.org/html/draft-wang-6man-flow-label-reflection-01 1387 TRUE: enabled 1388 FALSE: disabled 1389 Default: FALSE 1390 1391fib_multipath_hash_policy - INTEGER 1392 Controls which hash policy to use for multipath routes. 1393 Default: 0 (Layer 3) 1394 Possible values: 1395 0 - Layer 3 (source and destination addresses plus flow label) 1396 1 - Layer 4 (standard 5-tuple) 1397 1398anycast_src_echo_reply - BOOLEAN 1399 Controls the use of anycast addresses as source addresses for ICMPv6 1400 echo reply 1401 TRUE: enabled 1402 FALSE: disabled 1403 Default: FALSE 1404 1405idgen_delay - INTEGER 1406 Controls the delay in seconds after which time to retry 1407 privacy stable address generation if a DAD conflict is 1408 detected. 1409 Default: 1 (as specified in RFC7217) 1410 1411idgen_retries - INTEGER 1412 Controls the number of retries to generate a stable privacy 1413 address if a DAD conflict is detected. 1414 Default: 3 (as specified in RFC7217) 1415 1416mld_qrv - INTEGER 1417 Controls the MLD query robustness variable (see RFC3810 9.1). 1418 Default: 2 (as specified by RFC3810 9.1) 1419 Minimum: 1 (as specified by RFC6636 4.5) 1420 1421max_dst_opts_number - INTEGER 1422 Maximum number of non-padding TLVs allowed in a Destination 1423 options extension header. If this value is less than zero 1424 then unknown options are disallowed and the number of known 1425 TLVs allowed is the absolute value of this number. 1426 Default: 8 1427 1428max_hbh_opts_number - INTEGER 1429 Maximum number of non-padding TLVs allowed in a Hop-by-Hop 1430 options extension header. If this value is less than zero 1431 then unknown options are disallowed and the number of known 1432 TLVs allowed is the absolute value of this number. 1433 Default: 8 1434 1435max_dst_opts_length - INTEGER 1436 Maximum length allowed for a Destination options extension 1437 header. 1438 Default: INT_MAX (unlimited) 1439 1440max_hbh_length - INTEGER 1441 Maximum length allowed for a Hop-by-Hop options extension 1442 header. 1443 Default: INT_MAX (unlimited) 1444 1445IPv6 Fragmentation: 1446 1447ip6frag_high_thresh - INTEGER 1448 Maximum memory used to reassemble IPv6 fragments. When 1449 ip6frag_high_thresh bytes of memory is allocated for this purpose, 1450 the fragment handler will toss packets until ip6frag_low_thresh 1451 is reached. 1452 1453ip6frag_low_thresh - INTEGER 1454 See ip6frag_high_thresh 1455 1456ip6frag_time - INTEGER 1457 Time in seconds to keep an IPv6 fragment in memory. 1458 1459IPv6 Segment Routing: 1460 1461seg6_flowlabel - INTEGER 1462 Controls the behaviour of computing the flowlabel of outer 1463 IPv6 header in case of SR T.encaps 1464 1465 -1 set flowlabel to zero. 1466 0 copy flowlabel from Inner packet in case of Inner IPv6 1467 (Set flowlabel to 0 in case IPv4/L2) 1468 1 Compute the flowlabel using seg6_make_flowlabel() 1469 1470 Default is 0. 1471 1472conf/default/*: 1473 Change the interface-specific default settings. 1474 1475 1476conf/all/*: 1477 Change all the interface-specific settings. 1478 1479 [XXX: Other special features than forwarding?] 1480 1481conf/all/forwarding - BOOLEAN 1482 Enable global IPv6 forwarding between all interfaces. 1483 1484 IPv4 and IPv6 work differently here; e.g. netfilter must be used 1485 to control which interfaces may forward packets and which not. 1486 1487 This also sets all interfaces' Host/Router setting 1488 'forwarding' to the specified value. See below for details. 1489 1490 This referred to as global forwarding. 1491 1492proxy_ndp - BOOLEAN 1493 Do proxy ndp. 1494 1495fwmark_reflect - BOOLEAN 1496 Controls the fwmark of kernel-generated IPv6 reply packets that are not 1497 associated with a socket for example, TCP RSTs or ICMPv6 echo replies). 1498 If unset, these packets have a fwmark of zero. If set, they have the 1499 fwmark of the packet they are replying to. 1500 Default: 0 1501 1502conf/interface/*: 1503 Change special settings per interface. 1504 1505 The functional behaviour for certain settings is different 1506 depending on whether local forwarding is enabled or not. 1507 1508accept_ra - INTEGER 1509 Accept Router Advertisements; autoconfigure using them. 1510 1511 It also determines whether or not to transmit Router 1512 Solicitations. If and only if the functional setting is to 1513 accept Router Advertisements, Router Solicitations will be 1514 transmitted. 1515 1516 Possible values are: 1517 0 Do not accept Router Advertisements. 1518 1 Accept Router Advertisements if forwarding is disabled. 1519 2 Overrule forwarding behaviour. Accept Router Advertisements 1520 even if forwarding is enabled. 1521 1522 Functional default: enabled if local forwarding is disabled. 1523 disabled if local forwarding is enabled. 1524 1525accept_ra_defrtr - BOOLEAN 1526 Learn default router in Router Advertisement. 1527 1528 Functional default: enabled if accept_ra is enabled. 1529 disabled if accept_ra is disabled. 1530 1531accept_ra_from_local - BOOLEAN 1532 Accept RA with source-address that is found on local machine 1533 if the RA is otherwise proper and able to be accepted. 1534 Default is to NOT accept these as it may be an un-intended 1535 network loop. 1536 1537 Functional default: 1538 enabled if accept_ra_from_local is enabled 1539 on a specific interface. 1540 disabled if accept_ra_from_local is disabled 1541 on a specific interface. 1542 1543accept_ra_min_hop_limit - INTEGER 1544 Minimum hop limit Information in Router Advertisement. 1545 1546 Hop limit Information in Router Advertisement less than this 1547 variable shall be ignored. 1548 1549 Default: 1 1550 1551accept_ra_pinfo - BOOLEAN 1552 Learn Prefix Information in Router Advertisement. 1553 1554 Functional default: enabled if accept_ra is enabled. 1555 disabled if accept_ra is disabled. 1556 1557accept_ra_rt_info_min_plen - INTEGER 1558 Minimum prefix length of Route Information in RA. 1559 1560 Route Information w/ prefix smaller than this variable shall 1561 be ignored. 1562 1563 Functional default: 0 if accept_ra_rtr_pref is enabled. 1564 -1 if accept_ra_rtr_pref is disabled. 1565 1566accept_ra_rt_info_max_plen - INTEGER 1567 Maximum prefix length of Route Information in RA. 1568 1569 Route Information w/ prefix larger than this variable shall 1570 be ignored. 1571 1572 Functional default: 0 if accept_ra_rtr_pref is enabled. 1573 -1 if accept_ra_rtr_pref is disabled. 1574 1575accept_ra_rtr_pref - BOOLEAN 1576 Accept Router Preference in RA. 1577 1578 Functional default: enabled if accept_ra is enabled. 1579 disabled if accept_ra is disabled. 1580 1581accept_ra_mtu - BOOLEAN 1582 Apply the MTU value specified in RA option 5 (RFC4861). If 1583 disabled, the MTU specified in the RA will be ignored. 1584 1585 Functional default: enabled if accept_ra is enabled. 1586 disabled if accept_ra is disabled. 1587 1588accept_redirects - BOOLEAN 1589 Accept Redirects. 1590 1591 Functional default: enabled if local forwarding is disabled. 1592 disabled if local forwarding is enabled. 1593 1594accept_source_route - INTEGER 1595 Accept source routing (routing extension header). 1596 1597 >= 0: Accept only routing header type 2. 1598 < 0: Do not accept routing header. 1599 1600 Default: 0 1601 1602autoconf - BOOLEAN 1603 Autoconfigure addresses using Prefix Information in Router 1604 Advertisements. 1605 1606 Functional default: enabled if accept_ra_pinfo is enabled. 1607 disabled if accept_ra_pinfo is disabled. 1608 1609dad_transmits - INTEGER 1610 The amount of Duplicate Address Detection probes to send. 1611 Default: 1 1612 1613forwarding - INTEGER 1614 Configure interface-specific Host/Router behaviour. 1615 1616 Note: It is recommended to have the same setting on all 1617 interfaces; mixed router/host scenarios are rather uncommon. 1618 1619 Possible values are: 1620 0 Forwarding disabled 1621 1 Forwarding enabled 1622 1623 FALSE (0): 1624 1625 By default, Host behaviour is assumed. This means: 1626 1627 1. IsRouter flag is not set in Neighbour Advertisements. 1628 2. If accept_ra is TRUE (default), transmit Router 1629 Solicitations. 1630 3. If accept_ra is TRUE (default), accept Router 1631 Advertisements (and do autoconfiguration). 1632 4. If accept_redirects is TRUE (default), accept Redirects. 1633 1634 TRUE (1): 1635 1636 If local forwarding is enabled, Router behaviour is assumed. 1637 This means exactly the reverse from the above: 1638 1639 1. IsRouter flag is set in Neighbour Advertisements. 1640 2. Router Solicitations are not sent unless accept_ra is 2. 1641 3. Router Advertisements are ignored unless accept_ra is 2. 1642 4. Redirects are ignored. 1643 1644 Default: 0 (disabled) if global forwarding is disabled (default), 1645 otherwise 1 (enabled). 1646 1647hop_limit - INTEGER 1648 Default Hop Limit to set. 1649 Default: 64 1650 1651mtu - INTEGER 1652 Default Maximum Transfer Unit 1653 Default: 1280 (IPv6 required minimum) 1654 1655ip_nonlocal_bind - BOOLEAN 1656 If set, allows processes to bind() to non-local IPv6 addresses, 1657 which can be quite useful - but may break some applications. 1658 Default: 0 1659 1660router_probe_interval - INTEGER 1661 Minimum interval (in seconds) between Router Probing described 1662 in RFC4191. 1663 1664 Default: 60 1665 1666router_solicitation_delay - INTEGER 1667 Number of seconds to wait after interface is brought up 1668 before sending Router Solicitations. 1669 Default: 1 1670 1671router_solicitation_interval - INTEGER 1672 Number of seconds to wait between Router Solicitations. 1673 Default: 4 1674 1675router_solicitations - INTEGER 1676 Number of Router Solicitations to send until assuming no 1677 routers are present. 1678 Default: 3 1679 1680use_oif_addrs_only - BOOLEAN 1681 When enabled, the candidate source addresses for destinations 1682 routed via this interface are restricted to the set of addresses 1683 configured on this interface (vis. RFC 6724, section 4). 1684 1685 Default: false 1686 1687use_tempaddr - INTEGER 1688 Preference for Privacy Extensions (RFC3041). 1689 <= 0 : disable Privacy Extensions 1690 == 1 : enable Privacy Extensions, but prefer public 1691 addresses over temporary addresses. 1692 > 1 : enable Privacy Extensions and prefer temporary 1693 addresses over public addresses. 1694 Default: 0 (for most devices) 1695 -1 (for point-to-point devices and loopback devices) 1696 1697temp_valid_lft - INTEGER 1698 valid lifetime (in seconds) for temporary addresses. 1699 Default: 604800 (7 days) 1700 1701temp_prefered_lft - INTEGER 1702 Preferred lifetime (in seconds) for temporary addresses. 1703 Default: 86400 (1 day) 1704 1705keep_addr_on_down - INTEGER 1706 Keep all IPv6 addresses on an interface down event. If set static 1707 global addresses with no expiration time are not flushed. 1708 >0 : enabled 1709 0 : system default 1710 <0 : disabled 1711 1712 Default: 0 (addresses are removed) 1713 1714max_desync_factor - INTEGER 1715 Maximum value for DESYNC_FACTOR, which is a random value 1716 that ensures that clients don't synchronize with each 1717 other and generate new addresses at exactly the same time. 1718 value is in seconds. 1719 Default: 600 1720 1721regen_max_retry - INTEGER 1722 Number of attempts before give up attempting to generate 1723 valid temporary addresses. 1724 Default: 5 1725 1726max_addresses - INTEGER 1727 Maximum number of autoconfigured addresses per interface. Setting 1728 to zero disables the limitation. It is not recommended to set this 1729 value too large (or to zero) because it would be an easy way to 1730 crash the kernel by allowing too many addresses to be created. 1731 Default: 16 1732 1733disable_ipv6 - BOOLEAN 1734 Disable IPv6 operation. If accept_dad is set to 2, this value 1735 will be dynamically set to TRUE if DAD fails for the link-local 1736 address. 1737 Default: FALSE (enable IPv6 operation) 1738 1739 When this value is changed from 1 to 0 (IPv6 is being enabled), 1740 it will dynamically create a link-local address on the given 1741 interface and start Duplicate Address Detection, if necessary. 1742 1743 When this value is changed from 0 to 1 (IPv6 is being disabled), 1744 it will dynamically delete all addresses and routes on the given 1745 interface. From now on it will not possible to add addresses/routes 1746 to the selected interface. 1747 1748accept_dad - INTEGER 1749 Whether to accept DAD (Duplicate Address Detection). 1750 0: Disable DAD 1751 1: Enable DAD (default) 1752 2: Enable DAD, and disable IPv6 operation if MAC-based duplicate 1753 link-local address has been found. 1754 1755 DAD operation and mode on a given interface will be selected according 1756 to the maximum value of conf/{all,interface}/accept_dad. 1757 1758force_tllao - BOOLEAN 1759 Enable sending the target link-layer address option even when 1760 responding to a unicast neighbor solicitation. 1761 Default: FALSE 1762 1763 Quoting from RFC 2461, section 4.4, Target link-layer address: 1764 1765 "The option MUST be included for multicast solicitations in order to 1766 avoid infinite Neighbor Solicitation "recursion" when the peer node 1767 does not have a cache entry to return a Neighbor Advertisements 1768 message. When responding to unicast solicitations, the option can be 1769 omitted since the sender of the solicitation has the correct link- 1770 layer address; otherwise it would not have be able to send the unicast 1771 solicitation in the first place. However, including the link-layer 1772 address in this case adds little overhead and eliminates a potential 1773 race condition where the sender deletes the cached link-layer address 1774 prior to receiving a response to a previous solicitation." 1775 1776ndisc_notify - BOOLEAN 1777 Define mode for notification of address and device changes. 1778 0 - (default): do nothing 1779 1 - Generate unsolicited neighbour advertisements when device is brought 1780 up or hardware address changes. 1781 1782ndisc_tclass - INTEGER 1783 The IPv6 Traffic Class to use by default when sending IPv6 Neighbor 1784 Discovery (Router Solicitation, Router Advertisement, Neighbor 1785 Solicitation, Neighbor Advertisement, Redirect) messages. 1786 These 8 bits can be interpreted as 6 high order bits holding the DSCP 1787 value and 2 low order bits representing ECN (which you probably want 1788 to leave cleared). 1789 0 - (default) 1790 1791mldv1_unsolicited_report_interval - INTEGER 1792 The interval in milliseconds in which the next unsolicited 1793 MLDv1 report retransmit will take place. 1794 Default: 10000 (10 seconds) 1795 1796mldv2_unsolicited_report_interval - INTEGER 1797 The interval in milliseconds in which the next unsolicited 1798 MLDv2 report retransmit will take place. 1799 Default: 1000 (1 second) 1800 1801force_mld_version - INTEGER 1802 0 - (default) No enforcement of a MLD version, MLDv1 fallback allowed 1803 1 - Enforce to use MLD version 1 1804 2 - Enforce to use MLD version 2 1805 1806suppress_frag_ndisc - INTEGER 1807 Control RFC 6980 (Security Implications of IPv6 Fragmentation 1808 with IPv6 Neighbor Discovery) behavior: 1809 1 - (default) discard fragmented neighbor discovery packets 1810 0 - allow fragmented neighbor discovery packets 1811 1812optimistic_dad - BOOLEAN 1813 Whether to perform Optimistic Duplicate Address Detection (RFC 4429). 1814 0: disabled (default) 1815 1: enabled 1816 1817 Optimistic Duplicate Address Detection for the interface will be enabled 1818 if at least one of conf/{all,interface}/optimistic_dad is set to 1, 1819 it will be disabled otherwise. 1820 1821use_optimistic - BOOLEAN 1822 If enabled, do not classify optimistic addresses as deprecated during 1823 source address selection. Preferred addresses will still be chosen 1824 before optimistic addresses, subject to other ranking in the source 1825 address selection algorithm. 1826 0: disabled (default) 1827 1: enabled 1828 1829 This will be enabled if at least one of 1830 conf/{all,interface}/use_optimistic is set to 1, disabled otherwise. 1831 1832stable_secret - IPv6 address 1833 This IPv6 address will be used as a secret to generate IPv6 1834 addresses for link-local addresses and autoconfigured 1835 ones. All addresses generated after setting this secret will 1836 be stable privacy ones by default. This can be changed via the 1837 addrgenmode ip-link. conf/default/stable_secret is used as the 1838 secret for the namespace, the interface specific ones can 1839 overwrite that. Writes to conf/all/stable_secret are refused. 1840 1841 It is recommended to generate this secret during installation 1842 of a system and keep it stable after that. 1843 1844 By default the stable secret is unset. 1845 1846addr_gen_mode - INTEGER 1847 Defines how link-local and autoconf addresses are generated. 1848 1849 0: generate address based on EUI64 (default) 1850 1: do no generate a link-local address, use EUI64 for addresses generated 1851 from autoconf 1852 2: generate stable privacy addresses, using the secret from 1853 stable_secret (RFC7217) 1854 3: generate stable privacy addresses, using a random secret if unset 1855 1856drop_unicast_in_l2_multicast - BOOLEAN 1857 Drop any unicast IPv6 packets that are received in link-layer 1858 multicast (or broadcast) frames. 1859 1860 By default this is turned off. 1861 1862drop_unsolicited_na - BOOLEAN 1863 Drop all unsolicited neighbor advertisements, for example if there's 1864 a known good NA proxy on the network and such frames need not be used 1865 (or in the case of 802.11, must not be used to prevent attacks.) 1866 1867 By default this is turned off. 1868 1869enhanced_dad - BOOLEAN 1870 Include a nonce option in the IPv6 neighbor solicitation messages used for 1871 duplicate address detection per RFC7527. A received DAD NS will only signal 1872 a duplicate address if the nonce is different. This avoids any false 1873 detection of duplicates due to loopback of the NS messages that we send. 1874 The nonce option will be sent on an interface unless both of 1875 conf/{all,interface}/enhanced_dad are set to FALSE. 1876 Default: TRUE 1877 1878icmp/*: 1879ratelimit - INTEGER 1880 Limit the maximal rates for sending ICMPv6 packets. 1881 0 to disable any limiting, 1882 otherwise the minimal space between responses in milliseconds. 1883 Default: 1000 1884 1885echo_ignore_all - BOOLEAN 1886 If set non-zero, then the kernel will ignore all ICMP ECHO 1887 requests sent to it over the IPv6 protocol. 1888 Default: 0 1889 1890xfrm6_gc_thresh - INTEGER 1891 The threshold at which we will start garbage collecting for IPv6 1892 destination cache entries. At twice this value the system will 1893 refuse new allocations. 1894 1895 1896IPv6 Update by: 1897Pekka Savola <pekkas@netcore.fi> 1898YOSHIFUJI Hideaki / USAGI Project <yoshfuji@linux-ipv6.org> 1899 1900 1901/proc/sys/net/bridge/* Variables: 1902 1903bridge-nf-call-arptables - BOOLEAN 1904 1 : pass bridged ARP traffic to arptables' FORWARD chain. 1905 0 : disable this. 1906 Default: 1 1907 1908bridge-nf-call-iptables - BOOLEAN 1909 1 : pass bridged IPv4 traffic to iptables' chains. 1910 0 : disable this. 1911 Default: 1 1912 1913bridge-nf-call-ip6tables - BOOLEAN 1914 1 : pass bridged IPv6 traffic to ip6tables' chains. 1915 0 : disable this. 1916 Default: 1 1917 1918bridge-nf-filter-vlan-tagged - BOOLEAN 1919 1 : pass bridged vlan-tagged ARP/IP/IPv6 traffic to {arp,ip,ip6}tables. 1920 0 : disable this. 1921 Default: 0 1922 1923bridge-nf-filter-pppoe-tagged - BOOLEAN 1924 1 : pass bridged pppoe-tagged IP/IPv6 traffic to {ip,ip6}tables. 1925 0 : disable this. 1926 Default: 0 1927 1928bridge-nf-pass-vlan-input-dev - BOOLEAN 1929 1: if bridge-nf-filter-vlan-tagged is enabled, try to find a vlan 1930 interface on the bridge and set the netfilter input device to the vlan. 1931 This allows use of e.g. "iptables -i br0.1" and makes the REDIRECT 1932 target work with vlan-on-top-of-bridge interfaces. When no matching 1933 vlan interface is found, or this switch is off, the input device is 1934 set to the bridge interface. 1935 0: disable bridge netfilter vlan interface lookup. 1936 Default: 0 1937 1938proc/sys/net/sctp/* Variables: 1939 1940addip_enable - BOOLEAN 1941 Enable or disable extension of Dynamic Address Reconfiguration 1942 (ADD-IP) functionality specified in RFC5061. This extension provides 1943 the ability to dynamically add and remove new addresses for the SCTP 1944 associations. 1945 1946 1: Enable extension. 1947 1948 0: Disable extension. 1949 1950 Default: 0 1951 1952pf_enable - INTEGER 1953 Enable or disable pf (pf is short for potentially failed) state. A value 1954 of pf_retrans > path_max_retrans also disables pf state. That is, one of 1955 both pf_enable and pf_retrans > path_max_retrans can disable pf state. 1956 Since pf_retrans and path_max_retrans can be changed by userspace 1957 application, sometimes user expects to disable pf state by the value of 1958 pf_retrans > path_max_retrans, but occasionally the value of pf_retrans 1959 or path_max_retrans is changed by the user application, this pf state is 1960 enabled. As such, it is necessary to add this to dynamically enable 1961 and disable pf state. See: 1962 https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-failover for 1963 details. 1964 1965 1: Enable pf. 1966 1967 0: Disable pf. 1968 1969 Default: 1 1970 1971addip_noauth_enable - BOOLEAN 1972 Dynamic Address Reconfiguration (ADD-IP) requires the use of 1973 authentication to protect the operations of adding or removing new 1974 addresses. This requirement is mandated so that unauthorized hosts 1975 would not be able to hijack associations. However, older 1976 implementations may not have implemented this requirement while 1977 allowing the ADD-IP extension. For reasons of interoperability, 1978 we provide this variable to control the enforcement of the 1979 authentication requirement. 1980 1981 1: Allow ADD-IP extension to be used without authentication. This 1982 should only be set in a closed environment for interoperability 1983 with older implementations. 1984 1985 0: Enforce the authentication requirement 1986 1987 Default: 0 1988 1989auth_enable - BOOLEAN 1990 Enable or disable Authenticated Chunks extension. This extension 1991 provides the ability to send and receive authenticated chunks and is 1992 required for secure operation of Dynamic Address Reconfiguration 1993 (ADD-IP) extension. 1994 1995 1: Enable this extension. 1996 0: Disable this extension. 1997 1998 Default: 0 1999 2000prsctp_enable - BOOLEAN 2001 Enable or disable the Partial Reliability extension (RFC3758) which 2002 is used to notify peers that a given DATA should no longer be expected. 2003 2004 1: Enable extension 2005 0: Disable 2006 2007 Default: 1 2008 2009max_burst - INTEGER 2010 The limit of the number of new packets that can be initially sent. It 2011 controls how bursty the generated traffic can be. 2012 2013 Default: 4 2014 2015association_max_retrans - INTEGER 2016 Set the maximum number for retransmissions that an association can 2017 attempt deciding that the remote end is unreachable. If this value 2018 is exceeded, the association is terminated. 2019 2020 Default: 10 2021 2022max_init_retransmits - INTEGER 2023 The maximum number of retransmissions of INIT and COOKIE-ECHO chunks 2024 that an association will attempt before declaring the destination 2025 unreachable and terminating. 2026 2027 Default: 8 2028 2029path_max_retrans - INTEGER 2030 The maximum number of retransmissions that will be attempted on a given 2031 path. Once this threshold is exceeded, the path is considered 2032 unreachable, and new traffic will use a different path when the 2033 association is multihomed. 2034 2035 Default: 5 2036 2037pf_retrans - INTEGER 2038 The number of retransmissions that will be attempted on a given path 2039 before traffic is redirected to an alternate transport (should one 2040 exist). Note this is distinct from path_max_retrans, as a path that 2041 passes the pf_retrans threshold can still be used. Its only 2042 deprioritized when a transmission path is selected by the stack. This 2043 setting is primarily used to enable fast failover mechanisms without 2044 having to reduce path_max_retrans to a very low value. See: 2045 http://www.ietf.org/id/draft-nishida-tsvwg-sctp-failover-05.txt 2046 for details. Note also that a value of pf_retrans > path_max_retrans 2047 disables this feature. Since both pf_retrans and path_max_retrans can 2048 be changed by userspace application, a variable pf_enable is used to 2049 disable pf state. 2050 2051 Default: 0 2052 2053rto_initial - INTEGER 2054 The initial round trip timeout value in milliseconds that will be used 2055 in calculating round trip times. This is the initial time interval 2056 for retransmissions. 2057 2058 Default: 3000 2059 2060rto_max - INTEGER 2061 The maximum value (in milliseconds) of the round trip timeout. This 2062 is the largest time interval that can elapse between retransmissions. 2063 2064 Default: 60000 2065 2066rto_min - INTEGER 2067 The minimum value (in milliseconds) of the round trip timeout. This 2068 is the smallest time interval the can elapse between retransmissions. 2069 2070 Default: 1000 2071 2072hb_interval - INTEGER 2073 The interval (in milliseconds) between HEARTBEAT chunks. These chunks 2074 are sent at the specified interval on idle paths to probe the state of 2075 a given path between 2 associations. 2076 2077 Default: 30000 2078 2079sack_timeout - INTEGER 2080 The amount of time (in milliseconds) that the implementation will wait 2081 to send a SACK. 2082 2083 Default: 200 2084 2085valid_cookie_life - INTEGER 2086 The default lifetime of the SCTP cookie (in milliseconds). The cookie 2087 is used during association establishment. 2088 2089 Default: 60000 2090 2091cookie_preserve_enable - BOOLEAN 2092 Enable or disable the ability to extend the lifetime of the SCTP cookie 2093 that is used during the establishment phase of SCTP association 2094 2095 1: Enable cookie lifetime extension. 2096 0: Disable 2097 2098 Default: 1 2099 2100cookie_hmac_alg - STRING 2101 Select the hmac algorithm used when generating the cookie value sent by 2102 a listening sctp socket to a connecting client in the INIT-ACK chunk. 2103 Valid values are: 2104 * md5 2105 * sha1 2106 * none 2107 Ability to assign md5 or sha1 as the selected alg is predicated on the 2108 configuration of those algorithms at build time (CONFIG_CRYPTO_MD5 and 2109 CONFIG_CRYPTO_SHA1). 2110 2111 Default: Dependent on configuration. MD5 if available, else SHA1 if 2112 available, else none. 2113 2114rcvbuf_policy - INTEGER 2115 Determines if the receive buffer is attributed to the socket or to 2116 association. SCTP supports the capability to create multiple 2117 associations on a single socket. When using this capability, it is 2118 possible that a single stalled association that's buffering a lot 2119 of data may block other associations from delivering their data by 2120 consuming all of the receive buffer space. To work around this, 2121 the rcvbuf_policy could be set to attribute the receiver buffer space 2122 to each association instead of the socket. This prevents the described 2123 blocking. 2124 2125 1: rcvbuf space is per association 2126 0: rcvbuf space is per socket 2127 2128 Default: 0 2129 2130sndbuf_policy - INTEGER 2131 Similar to rcvbuf_policy above, this applies to send buffer space. 2132 2133 1: Send buffer is tracked per association 2134 0: Send buffer is tracked per socket. 2135 2136 Default: 0 2137 2138sctp_mem - vector of 3 INTEGERs: min, pressure, max 2139 Number of pages allowed for queueing by all SCTP sockets. 2140 2141 min: Below this number of pages SCTP is not bothered about its 2142 memory appetite. When amount of memory allocated by SCTP exceeds 2143 this number, SCTP starts to moderate memory usage. 2144 2145 pressure: This value was introduced to follow format of tcp_mem. 2146 2147 max: Number of pages allowed for queueing by all SCTP sockets. 2148 2149 Default is calculated at boot time from amount of available memory. 2150 2151sctp_rmem - vector of 3 INTEGERs: min, default, max 2152 Only the first value ("min") is used, "default" and "max" are 2153 ignored. 2154 2155 min: Minimal size of receive buffer used by SCTP socket. 2156 It is guaranteed to each SCTP socket (but not association) even 2157 under moderate memory pressure. 2158 2159 Default: 4K 2160 2161sctp_wmem - vector of 3 INTEGERs: min, default, max 2162 Currently this tunable has no effect. 2163 2164addr_scope_policy - INTEGER 2165 Control IPv4 address scoping - draft-stewart-tsvwg-sctp-ipv4-00 2166 2167 0 - Disable IPv4 address scoping 2168 1 - Enable IPv4 address scoping 2169 2 - Follow draft but allow IPv4 private addresses 2170 3 - Follow draft but allow IPv4 link local addresses 2171 2172 Default: 1 2173 2174 2175/proc/sys/net/core/* 2176 Please see: Documentation/sysctl/net.txt for descriptions of these entries. 2177 2178 2179/proc/sys/net/unix/* 2180max_dgram_qlen - INTEGER 2181 The maximum length of dgram socket receive queue 2182 2183 Default: 10 2184 2185