1.\" Copyright (c) 1983, 1991, 1993 2.\" The Regents of the University of California. 3.\" Copyright (c) 2010-2011 The FreeBSD Foundation 4.\" All rights reserved. 5.\" 6.\" Portions of this documentation were written at the Centre for Advanced 7.\" Internet Architectures, Swinburne University of Technology, Melbourne, 8.\" Australia by David Hayes under sponsorship from the FreeBSD Foundation. 9.\" 10.\" Redistribution and use in source and binary forms, with or without 11.\" modification, are permitted provided that the following conditions 12.\" are met: 13.\" 1. Redistributions of source code must retain the above copyright 14.\" notice, this list of conditions and the following disclaimer. 15.\" 2. Redistributions in binary form must reproduce the above copyright 16.\" notice, this list of conditions and the following disclaimer in the 17.\" documentation and/or other materials provided with the distribution. 18.\" 3. Neither the name of the University nor the names of its contributors 19.\" may be used to endorse or promote products derived from this software 20.\" without specific prior written permission. 21.\" 22.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 23.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 24.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 25.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 26.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 27.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 28.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 29.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 30.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 31.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 32.\" SUCH DAMAGE. 33.\" 34.\" From: @(#)tcp.4 8.1 (Berkeley) 6/5/93 35.\" $FreeBSD$ 36.\" 37.Dd June 27, 2021 38.Dt TCP 4 39.Os 40.Sh NAME 41.Nm tcp 42.Nd Internet Transmission Control Protocol 43.Sh SYNOPSIS 44.In sys/types.h 45.In sys/socket.h 46.In netinet/in.h 47.In netinet/tcp.h 48.Ft int 49.Fn socket AF_INET SOCK_STREAM 0 50.Sh DESCRIPTION 51The 52.Tn TCP 53protocol provides reliable, flow-controlled, two-way 54transmission of data. 55It is a byte-stream protocol used to 56support the 57.Dv SOCK_STREAM 58abstraction. 59.Tn TCP 60uses the standard 61Internet address format and, in addition, provides a per-host 62collection of 63.Dq "port addresses" . 64Thus, each address is composed 65of an Internet address specifying the host and network, 66with a specific 67.Tn TCP 68port on the host identifying the peer entity. 69.Pp 70Sockets utilizing the 71.Tn TCP 72protocol are either 73.Dq active 74or 75.Dq passive . 76Active sockets initiate connections to passive 77sockets. 78By default, 79.Tn TCP 80sockets are created active; to create a 81passive socket, the 82.Xr listen 2 83system call must be used 84after binding the socket with the 85.Xr bind 2 86system call. 87Only passive sockets may use the 88.Xr accept 2 89call to accept incoming connections. 90Only active sockets may use the 91.Xr connect 2 92call to initiate connections. 93.Pp 94Passive sockets may 95.Dq underspecify 96their location to match 97incoming connection requests from multiple networks. 98This technique, termed 99.Dq "wildcard addressing" , 100allows a single 101server to provide service to clients on multiple networks. 102To create a socket which listens on all networks, the Internet 103address 104.Dv INADDR_ANY 105must be bound. 106The 107.Tn TCP 108port may still be specified 109at this time; if the port is not specified, the system will assign one. 110Once a connection has been established, the socket's address is 111fixed by the peer entity's location. 112The address assigned to the 113socket is the address associated with the network interface 114through which packets are being transmitted and received. 115Normally, this address corresponds to the peer entity's network. 116.Pp 117.Tn TCP 118supports a number of socket options which can be set with 119.Xr setsockopt 2 120and tested with 121.Xr getsockopt 2 : 122.Bl -tag -width ".Dv TCP_FUNCTION_BLK" 123.It Dv TCP_INFO 124Information about a socket's underlying TCP session may be retrieved 125by passing the read-only option 126.Dv TCP_INFO 127to 128.Xr getsockopt 2 . 129It accepts a single argument: a pointer to an instance of 130.Vt "struct tcp_info" . 131.Pp 132This API is subject to change; consult the source to determine 133which fields are currently filled out by this option. 134.Fx 135specific additions include 136send window size, 137receive window size, 138and 139bandwidth-controlled window space. 140.It Dv TCP_CCALGOOPT 141Set or query congestion control algorithm specific parameters. 142See 143.Xr mod_cc 4 144for details. 145.It Dv TCP_CONGESTION 146Select or query the congestion control algorithm that TCP will use for the 147connection. 148See 149.Xr mod_cc 4 150for details. 151.It Dv TCP_FUNCTION_BLK 152Select or query the set of functions that TCP will use for this connection. 153This allows a user to select an alternate TCP stack. 154The alternate TCP stack must already be loaded in the kernel. 155To list the available TCP stacks, see 156.Va functions_available 157in the 158.Sx MIB Variables 159section further down. 160To list the default TCP stack, see 161.Va functions_default 162in the 163.Sx MIB Variables 164section. 165.It Dv TCP_KEEPINIT 166This 167.Xr setsockopt 2 168option accepts a per-socket timeout argument of 169.Vt "u_int" 170in seconds, for new, non-established 171.Tn TCP 172connections. 173For the global default in milliseconds see 174.Va keepinit 175in the 176.Sx MIB Variables 177section further down. 178.It Dv TCP_KEEPIDLE 179This 180.Xr setsockopt 2 181option accepts an argument of 182.Vt "u_int" 183for the amount of time, in seconds, that the connection must be idle 184before keepalive probes (if enabled) are sent for the connection of this 185socket. 186If set on a listening socket, the value is inherited by the newly created 187socket upon 188.Xr accept 2 . 189For the global default in milliseconds see 190.Va keepidle 191in the 192.Sx MIB Variables 193section further down. 194.It Dv TCP_KEEPINTVL 195This 196.Xr setsockopt 2 197option accepts an argument of 198.Vt "u_int" 199to set the per-socket interval, in seconds, between keepalive probes sent 200to a peer. 201If set on a listening socket, the value is inherited by the newly created 202socket upon 203.Xr accept 2 . 204For the global default in milliseconds see 205.Va keepintvl 206in the 207.Sx MIB Variables 208section further down. 209.It Dv TCP_KEEPCNT 210This 211.Xr setsockopt 2 212option accepts an argument of 213.Vt "u_int" 214and allows a per-socket tuning of the number of probes sent, with no response, 215before the connection will be dropped. 216If set on a listening socket, the value is inherited by the newly created 217socket upon 218.Xr accept 2 . 219For the global default see the 220.Va keepcnt 221in the 222.Sx MIB Variables 223section further down. 224.It Dv TCP_NODELAY 225Under most circumstances, 226.Tn TCP 227sends data when it is presented; 228when outstanding data has not yet been acknowledged, it gathers 229small amounts of output to be sent in a single packet once 230an acknowledgement is received. 231For a small number of clients, such as window systems 232that send a stream of mouse events which receive no replies, 233this packetization may cause significant delays. 234The boolean option 235.Dv TCP_NODELAY 236defeats this algorithm. 237.It Dv TCP_MAXSEG 238By default, a sender- and 239.No receiver- Ns Tn TCP 240will negotiate among themselves to determine the maximum segment size 241to be used for each connection. 242The 243.Dv TCP_MAXSEG 244option allows the user to determine the result of this negotiation, 245and to reduce it if desired. 246.It Dv TCP_NOOPT 247.Tn TCP 248usually sends a number of options in each packet, corresponding to 249various 250.Tn TCP 251extensions which are provided in this implementation. 252The boolean option 253.Dv TCP_NOOPT 254is provided to disable 255.Tn TCP 256option use on a per-connection basis. 257.It Dv TCP_NOPUSH 258By convention, the 259.No sender- Ns Tn TCP 260will set the 261.Dq push 262bit, and begin transmission immediately (if permitted) at the end of 263every user call to 264.Xr write 2 265or 266.Xr writev 2 . 267When this option is set to a non-zero value, 268.Tn TCP 269will delay sending any data at all until either the socket is closed, 270or the internal send buffer is filled. 271.It Dv TCP_MD5SIG 272This option enables the use of MD5 digests (also known as TCP-MD5) 273on writes to the specified socket. 274Outgoing traffic is digested; 275digests on incoming traffic are verified. 276When this option is enabled on a socket, all inbound and outgoing 277TCP segments must be signed with MD5 digests. 278.Pp 279One common use for this in a 280.Fx 281router deployment is to enable 282based routers to interwork with Cisco equipment at peering points. 283Support for this feature conforms to RFC 2385. 284.Pp 285In order for this option to function correctly, it is necessary for the 286administrator to add a tcp-md5 key entry to the system's security 287associations database (SADB) using the 288.Xr setkey 8 289utility. 290This entry can only be specified on a per-host basis at this time. 291.Pp 292If an SADB entry cannot be found for the destination, 293the system does not send any outgoing segments and drops any inbound segments. 294.It Dv TCP_STATS 295Manage collection of connection level statistics using the 296.Xr stats 3 297framework. 298.Pp 299Each dropped segment is taken into account in the TCP protocol statistics. 300.It Dv TCP_TXTLS_ENABLE 301Enable in-kernel Transport Layer Security (TLS) for data written to this 302socket. 303See 304.Xr ktls 4 305for more details. 306.It Dv TCP_TXTLS_MODE 307The integer argument can be used to get or set the current TLS transmit mode 308of a socket. 309See 310.Xr ktls 4 311for more details. 312.It Dv TCP_RXTLS_ENABLE 313Enable in-kernel TLS for data read from this socket. 314See 315.Xr ktls 4 316for more details. 317.It Dv TCP_REUSPORT_LB_NUMA 318Changes NUMA affinity filtering for an established TCP listen 319socket. 320This option takes a single integer argument which specifies 321the NUMA domain to filter on for this listen socket. 322The argument can also have the follwing special values: 323.Bl -tag -width "Dv TCP_REUSPORT_LB_NUMA" 324.It Dv TCP_REUSPORT_LB_NUMA_NODOM 325Remove NUMA filtering for this listen socket. 326.It Dv TCP_REUSPORT_LB_NUMA_CURDOM 327Filter traffic associated with the domain where the calling thread is 328currently executing. 329This is typically used after a process or thread inherits a listen 330socket from its parent, and sets its CPU affinity to a particular core. 331.El 332.It Dv TCP_REMOTE_UDP_ENCAPS_PORT 333Set and get the remote UDP encapsulation port. 334It can only be set on a closed TCP socket. 335.El 336.Pp 337The option level for the 338.Xr setsockopt 2 339call is the protocol number for 340.Tn TCP , 341available from 342.Xr getprotobyname 3 , 343or 344.Dv IPPROTO_TCP . 345All options are declared in 346.In netinet/tcp.h . 347.Pp 348Options at the 349.Tn IP 350transport level may be used with 351.Tn TCP ; 352see 353.Xr ip 4 . 354Incoming connection requests that are source-routed are noted, 355and the reverse source route is used in responding. 356.Pp 357The default congestion control algorithm for 358.Tn TCP 359is 360.Xr cc_newreno 4 . 361Other congestion control algorithms can be made available using the 362.Xr mod_cc 4 363framework. 364.Ss MIB Variables 365The 366.Tn TCP 367protocol implements a number of variables in the 368.Va net.inet.tcp 369branch of the 370.Xr sysctl 3 371MIB. 372.Bl -tag -width ".Va TCPCTL_DO_RFC1323" 373.It Dv TCPCTL_DO_RFC1323 374.Pq Va rfc1323 375Implement the window scaling and timestamp options of RFC 1323/RFC 7323 376(default is true). 377.It Va tolerate_missing_ts 378Tolerate the missing of timestamps (RFC 1323/RFC 7323) for 379.Tn TCP 380segments belonging to 381.Tn TCP 382connections for which support of 383.Tn TCP 384timestamps has been negotiated. 385As of June 2021, several TCP stacks are known to violate RFC 7323, including 386modern widely deployed ones. 387Therefore the default is 1, i.e., the missing of timestamps is tolerated. 388.It Dv TCPCTL_MSSDFLT 389.Pq Va mssdflt 390The default value used for the maximum segment size 391.Pq Dq MSS 392when no advice to the contrary is received from MSS negotiation. 393.It Dv TCPCTL_SENDSPACE 394.Pq Va sendspace 395Maximum 396.Tn TCP 397send window. 398.It Dv TCPCTL_RECVSPACE 399.Pq Va recvspace 400Maximum 401.Tn TCP 402receive window. 403.It Va log_in_vain 404Log any connection attempts to ports where there is not a socket 405accepting connections. 406The value of 1 limits the logging to 407.Tn SYN 408(connection establishment) packets only. 409That of 2 results in any 410.Tn TCP 411packets to closed ports being logged. 412Any value unlisted above disables the logging 413(default is 0, i.e., the logging is disabled). 414.It Va msl 415The Maximum Segment Lifetime, in milliseconds, for a packet. 416.It Va keepinit 417Timeout, in milliseconds, for new, non-established 418.Tn TCP 419connections. 420The default is 75000 msec. 421.It Va keepidle 422Amount of time, in milliseconds, that the connection must be idle 423before keepalive probes (if enabled) are sent. 424The default is 7200000 msec (2 hours). 425.It Va keepintvl 426The interval, in milliseconds, between keepalive probes sent to remote 427machines, when no response is received on a 428.Va keepidle 429probe. 430The default is 75000 msec. 431.It Va keepcnt 432Number of probes sent, with no response, before a connection 433is dropped. 434The default is 8 packets. 435.It Va always_keepalive 436Assume that 437.Dv SO_KEEPALIVE 438is set on all 439.Tn TCP 440connections, the kernel will 441periodically send a packet to the remote host to verify the connection 442is still up. 443.It Va icmp_may_rst 444Certain 445.Tn ICMP 446unreachable messages may abort connections in 447.Tn SYN-SENT 448state. 449.It Va do_tcpdrain 450Flush packets in the 451.Tn TCP 452reassembly queue if the system is low on mbufs. 453.It Va blackhole 454If enabled, disable sending of RST when a connection is attempted 455to a port where there is not a socket accepting connections. 456See 457.Xr blackhole 4 . 458.It Va delayed_ack 459Delay ACK to try and piggyback it onto a data packet. 460.It Va delacktime 461Maximum amount of time, in milliseconds, before a delayed ACK is sent. 462.It Va path_mtu_discovery 463Enable Path MTU Discovery. 464.It Va tcbhashsize 465Size of the 466.Tn TCP 467control-block hash table 468(read-only). 469This may be tuned using the kernel option 470.Dv TCBHASHSIZE 471or by setting 472.Va net.inet.tcp.tcbhashsize 473in the 474.Xr loader 8 . 475.It Va pcbcount 476Number of active process control blocks 477(read-only). 478.It Va syncookies 479Determines whether or not 480.Tn SYN 481cookies should be generated for outbound 482.Tn SYN-ACK 483packets. 484.Tn SYN 485cookies are a great help during 486.Tn SYN 487flood attacks, and are enabled by default. 488(See 489.Xr syncookies 4 . ) 490.It Va isn_reseed_interval 491The interval (in seconds) specifying how often the secret data used in 492RFC 1948 initial sequence number calculations should be reseeded. 493By default, this variable is set to zero, indicating that 494no reseeding will occur. 495Reseeding should not be necessary, and will break 496.Dv TIME_WAIT 497recycling for a few minutes. 498.It Va reass.cursegments 499The current total number of segments present in all reassembly queues. 500.It Va reass.maxsegments 501The maximum limit on the total number of segments across all reassembly 502queues. 503The limit can be adjusted as a tunable. 504.It Va reass.maxqueuelen 505The maximum number of segments allowed in each reassembly queue. 506By default, the system chooses a limit based on each TCP connection's 507receive buffer size and maximum segment size (MSS). 508The actual limit applied to a session's reassembly queue will be the lower of 509the system-calculated automatic limit and the user-specified 510.Va reass.maxqueuelen 511limit. 512.It Va rexmit_initial , rexmit_min , rexmit_slop 513Adjust the retransmit timer calculation for 514.Tn TCP . 515The slop is 516typically added to the raw calculation to take into account 517occasional variances that the 518.Tn SRTT 519(smoothed round-trip time) 520is unable to accommodate, while the minimum specifies an 521absolute minimum. 522While a number of 523.Tn TCP 524RFCs suggest a 1 525second minimum, these RFCs tend to focus on streaming behavior, 526and fail to deal with the fact that a 1 second minimum has severe 527detrimental effects over lossy interactive connections, such 528as a 802.11b wireless link, and over very fast but lossy 529connections for those cases not covered by the fast retransmit 530code. 531For this reason, we use 200ms of slop and a near-0 532minimum, which gives us an effective minimum of 200ms (similar to 533.Tn Linux ) . 534The initial value is used before an RTT measurement has been performed. 535.It Va initcwnd_segments 536Enable the ability to specify initial congestion window in number of segments. 537The default value is 10 as suggested by RFC 6928. 538Changing the value on fly would not affect connections using congestion window 539from the hostcache. 540Caution: 541This regulates the burst of packets allowed to be sent in the first RTT. 542The value should be relative to the link capacity. 543Start with small values for lower-capacity links. 544Large bursts can cause buffer overruns and packet drops if routers have small 545buffers or the link is experiencing congestion. 546.It Va newcwd 547Enable the New Congestion Window Validation mechanism as described in RFC 7661. 548This gently reduces the congestion window during periods, where TCP is 549application limited and the network bandwidth is not utilized completely. 550That prevents self-inflicted packet losses once the application starts to 551transmit data at a higher speed. 552.It Va do_lrd 553Enable Lost Retransmission Detection for SACK-enabled sessions, disabled by 554default. 555Under severe congestion, a retransmission can be lost which then leads to a 556mandatory Retransmission Timeout (RTO), followed by slow-start. 557LRD will try to resend the repeatedly lost packet, preventing the time-consuming 558RTO and performance reducing slow-start. 559.It Va do_prr 560Perform SACK loss recovery using the Proportional Rate Reduction (PRR) algorithm 561described in RFC6937. 562This improves the effectiveness of retransmissions particular in environments 563with ACK thinning or burst loss events, as chances to run out of the ACK clock 564are reduced, preventing lengthy and performance reducing RTO based loss recovery 565(default is true). 566.It Va do_prr_conservative 567While doing Proportional Rate Reduction, remain strictly in a packet conserving 568mode, sending only one new packet for each ACK received. 569Helpful when a misconfigured token bucket traffic policer causes persistent 570high losses leading to RTO, but reduces PRR effectiveness in more common settings 571(default is false). 572.It Va rfc6675_pipe 573Deprecated and superseded by 574.Va sack.revised 575.It Va rfc3042 576Enable the Limited Transmit algorithm as described in RFC 3042. 577It helps avoid timeouts on lossy links and also when the congestion window 578is small, as happens on short transfers. 579.It Va rfc3390 580Enable support for RFC 3390, which allows for a variable-sized 581starting congestion window on new connections, depending on the 582maximum segment size. 583This helps throughput in general, but 584particularly affects short transfers and high-bandwidth large 585propagation-delay connections. 586.It Va sack.enable 587Enable support for RFC 2018, TCP Selective Acknowledgment option, 588which allows the receiver to inform the sender about all successfully 589arrived segments, allowing the sender to retransmit the missing segments 590only. 591.It Va sack.revised 592Enables three updated mechanisms from RFC6675 (default is true). 593Calculate the bytes in flight using the algorithm described in RFC 6675, and 594is also an improvement when Proportional Rate Reduction is enabled. 595Next, Rescue Retransmission helps timely loss recovery, when the trailing segments 596of a transmission are lost, while no additional data is ready to be sent. 597In case a partial ACK without a SACK block is received during SACK loss 598recovery, the trailing segment is immediately resent, rather than waiting 599for a Retransmission timeout. 600Finally, SACK loss recovery is also engaged, once two segments plus one byte are 601SACKed - even if no traditional duplicate ACKs were observed. 602.It Va sack.maxholes 603Maximum number of SACK holes per connection. 604Defaults to 128. 605.It Va sack.globalmaxholes 606Maximum number of SACK holes per system, across all connections. 607Defaults to 65536. 608.It Va maxtcptw 609When a TCP connection enters the 610.Dv TIME_WAIT 611state, its associated socket structure is freed, since it is of 612negligible size and use, and a new structure is allocated to contain a 613minimal amount of information necessary for sustaining a connection in 614this state, called the compressed TCP TIME_WAIT state. 615Since this structure is smaller than a socket structure, it can save 616a significant amount of system memory. 617The 618.Va net.inet.tcp.maxtcptw 619MIB variable controls the maximum number of these structures allocated. 620By default, it is initialized to 621.Va kern.ipc.maxsockets 622/ 5. 623.It Va nolocaltimewait 624Suppress creating of compressed TCP TIME_WAIT states for connections in 625which both endpoints are local. 626.It Va fast_finwait2_recycle 627Recycle 628.Tn TCP 629.Dv FIN_WAIT_2 630connections faster when the socket is marked as 631.Dv SBS_CANTRCVMORE 632(no user process has the socket open, data received on 633the socket cannot be read). 634The timeout used here is 635.Va finwait2_timeout . 636.It Va finwait2_timeout 637Timeout to use for fast recycling of 638.Tn TCP 639.Dv FIN_WAIT_2 640connections. 641Defaults to 60 seconds. 642.It Va ecn.enable 643Enable support for TCP Explicit Congestion Notification (ECN). 644ECN allows a TCP sender to reduce the transmission rate in order to 645avoid packet drops. 646.Bl -tag -compact 647.It 0 648Disable ECN. 649.It 1 650Allow incoming connections to request ECN. 651Outgoing connections will request ECN. 652.It 2 653Allow incoming connections to request ECN. 654Outgoing connections will not request ECN. 655(default) 656.El 657.It Va ecn.maxretries 658Number of retries (SYN or SYN/ACK retransmits) before disabling ECN on a 659specific connection. 660This is needed to help with connection establishment 661when a broken firewall is in the network path. 662.It Va pmtud_blackhole_detection 663Enable automatic path MTU blackhole detection. 664In case of retransmits of MSS sized segments, 665the OS will lower the MSS to check if it's an MTU problem. 666If the current MSS is greater than the configured value to try 667.Po Va net.inet.tcp.pmtud_blackhole_mss 668and 669.Va net.inet.tcp.v6pmtud_blackhole_mss 670.Pc , 671it will be set to this value, otherwise, 672the MSS will be set to the default values 673.Po Va net.inet.tcp.mssdflt 674and 675.Va net.inet.tcp.v6mssdflt 676.Pc . 677Settings: 678.Bl -tag -compact 679.It 0 680Disable path MTU blackhole detection. 681.It 1 682Enable path MTU blackhole detection for IPv4 and IPv6. 683.It 2 684Enable path MTU blackhole detection only for IPv4. 685.It 3 686Enable path MTU blackhole detection only for IPv6. 687.El 688.It Va pmtud_blackhole_mss 689MSS to try for IPv4 if PMTU blackhole detection is turned on. 690.It Va v6pmtud_blackhole_mss 691MSS to try for IPv6 if PMTU blackhole detection is turned on. 692.It Va hostcache.enable 693The TCP host cache is used to cache connection details and metrics to 694improve future performance of connections between the same hosts. 695At the completion of a TCP connection, a host will cache information 696for the connection for some defined period of time. 697.Bl -tag -compact 698.It 0 699Disable the host cache. 700.It 1 701Enable the host cache. (default) 702.El 703.It Va hostcache.purgenow 704Immediately purge all entries once set to any value. 705Setting this to 2 will also reseed the hash salt. 706.It Va hostcache.purge 707Expire all entires on next pruning of host cache entries. 708Any non-zero setting will be reset to zero, once the pruge 709is running. 710.Bl -tag -compact 711.It 0 712Do not purge all entries when pruning the host cache. (default) 713.It 1 714Purge all entries when doing the next pruning. 715.It 2 716Purge all entries, and also reseed the hash salt. 717.El 718.It Va hostcache.prune 719Time in seconds between pruning expired host cache entries. 720Defaults to 300 (5 minutes). 721.It Va hostcache.expire 722Time in seconds, how long a entry should be kept in the 723host cache since last accessed. 724Defaults to 3600 (1 hour). 725.It Va hostcache.count 726The current number of entries in the host cache. 727.It Va hostcache.bucketlimit 728The maximum number of entries for the same hash. 729Defaults to 30. 730.It Va hostcache.hashsize 731Size of TCP hostcache hashtable. 732This number has to be a power of two, or will be rejected. 733Defaults to 512. 734.It Va hostcache.cachelimit 735Overall entry limit for hostcache. 736Defaults to hashsize * bucketlimit. 737.It Va hostcache.histo 738Provide a Histogram of the hostcache hash utilization. 739.It Va hostcache.list 740Provide a complete list of all current entries in the host 741cache. 742.It Va functions_available 743List of available TCP function blocks (TCP stacks). 744.It Va functions_default 745The default TCP function block (TCP stack). 746.It Va functions_inherit_listen_socket_stack 747Determines whether to inherit listen socket's tcp stack or use the current 748system default tcp stack, as defined by 749.Va functions_default . 750Default is true. 751.It Va insecure_rst 752Use criteria defined in RFC793 instead of RFC5961 for accepting RST segments. 753Default is false. 754.It Va insecure_syn 755Use criteria defined in RFC793 instead of RFC5961 for accepting SYN segments. 756Default is false. 757.It Va ts_offset_per_conn 758When initializing the TCP timestamps, use a per connection offset instead of a 759per host pair offset. 760Default is to use per connection offsets as recommended in RFC 7323. 761.It Va perconn_stats_enable 762Controls the default collection of statistics for all connections using the 763.Xr stats 3 764framework. 7650 disables, 1 enables, 2 enables random sampling across log id connection 766groups with all connections in a group receiving the same setting. 767.It Va perconn_stats_sample_rates 768A CSV list of template_spec=percent key-value pairs which controls the per 769template sampling rates when 770.Xr stats 3 771sampling is enabled. 772.It Va udp_tunneling_port 773The local UDP encapsulation port. 774A value of 0 indicates that UDP encapsulation is disabled. 775The default is 0. 776.It Va udp_tunneling_overhead 777The overhead taken into account when using UDP encapsulation. 778Since MSS clamping by middleboxes will most likely not work, values larger than 7798 (the size of the UDP header) are also supported. 780Supported values are between 8 and 1024. 781The default is 8. 782.El 783.Sh ERRORS 784A socket operation may fail with one of the following errors returned: 785.Bl -tag -width Er 786.It Bq Er EISCONN 787when trying to establish a connection on a socket which 788already has one; 789.It Bo Er ENOBUFS Bc or Bo Er ENOMEM Bc 790when the system runs out of memory for 791an internal data structure; 792.It Bq Er ETIMEDOUT 793when a connection was dropped 794due to excessive retransmissions; 795.It Bq Er ECONNRESET 796when the remote peer 797forces the connection to be closed; 798.It Bq Er ECONNREFUSED 799when the remote 800peer actively refuses connection establishment (usually because 801no process is listening to the port); 802.It Bq Er EADDRINUSE 803when an attempt 804is made to create a socket with a port which has already been 805allocated; 806.It Bq Er EADDRNOTAVAIL 807when an attempt is made to create a 808socket with a network address for which no network interface 809exists; 810.It Bq Er EAFNOSUPPORT 811when an attempt is made to bind or connect a socket to a multicast 812address. 813.It Bq Er EINVAL 814when trying to change TCP function blocks at an invalid point in the session; 815.It Bq Er ENOENT 816when trying to use a TCP function block that is not available; 817.El 818.Sh SEE ALSO 819.Xr getsockopt 2 , 820.Xr socket 2 , 821.Xr stats 3 , 822.Xr sysctl 3 , 823.Xr blackhole 4 , 824.Xr inet 4 , 825.Xr intro 4 , 826.Xr ip 4 , 827.Xr ktls 4 , 828.Xr mod_cc 4 , 829.Xr siftr 4 , 830.Xr syncache 4 , 831.Xr tcp_bbr 4 , 832.Xr setkey 8 , 833.Xr tcp_functions 9 834.Rs 835.%A "V. Jacobson" 836.%A "B. Braden" 837.%A "D. Borman" 838.%T "TCP Extensions for High Performance" 839.%O "RFC 1323" 840.Re 841.Rs 842.%A "D. Borman" 843.%A "B. Braden" 844.%A "V. Jacobson" 845.%A "R. Scheffenegger" 846.%T "TCP Extensions for High Performance" 847.%O "RFC 7323" 848.Re 849.Rs 850.%A "A. Heffernan" 851.%T "Protection of BGP Sessions via the TCP MD5 Signature Option" 852.%O "RFC 2385" 853.Re 854.Rs 855.%A "K. Ramakrishnan" 856.%A "S. Floyd" 857.%A "D. Black" 858.%T "The Addition of Explicit Congestion Notification (ECN) to IP" 859.%O "RFC 3168" 860.Re 861.Sh HISTORY 862The 863.Tn TCP 864protocol appeared in 865.Bx 4.2 . 866The RFC 1323 extensions for window scaling and timestamps were added 867in 868.Bx 4.4 . 869The 870.Dv TCP_INFO 871option was introduced in 872.Tn Linux 2.6 873and is 874.Em subject to change . 875