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 April 16, 2020 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. 303The 304.Vt struct tls_so_enable 305argument defines the encryption and authentication algorithms and keys 306used to encrypt the socket data as well as the maximum TLS record 307payload size. 308.Pp 309All data written to this socket will be encapsulated in TLS records 310and subsequently encrypted. 311By default all data written to this socket is treated as application data. 312Individual TLS records with a type other than application data 313(for example, handshake messages), 314may be transmitted by invoking 315.Xr sendmsg 2 316with a custom TLS record type set in a 317.Dv TLS_SET_RECORD_TYPE 318control message. 319The payload of this control message is a single byte holding the desired 320TLS record type. 321.Pp 322Data read from this socket will still be encrypted and must be parsed by 323a TLS-aware consumer. 324.Pp 325At present, only a single key may be set on a socket. 326As such, users of this option must disable rekeying. 327.It Dv TCP_TXTLS_MODE 328The integer argument can be used to get or set the current TLS mode of a 329socket. 330Setting the mode can only used to toggle between software and NIC TLS after 331TLS has been initially enabled via the 332.Dv TCP_TXTLS_ENABLE 333option. 334The available modes are: 335.Bl -tag -width "Dv TCP_TLS_MODE_IFNET" 336.It Dv TCP_TLS_MODE_NONE 337In-kernel TLS framing and encryption is not enabled for this socket. 338.It Dv TCP_TLS_MODE_SW 339TLS records are encrypted by the kernel prior to placing the data in the 340socket buffer. 341Typically this encryption is performed in software. 342.It Dv TCP_TLS_MODE_IFNET 343TLS records are encrypted by the network interface card (NIC). 344.It Dv TCP_TLS_MODE_TOE 345TLS records are encrypted by the NIC using a TCP offload engine (TOE). 346.El 347.El 348.Pp 349The option level for the 350.Xr setsockopt 2 351call is the protocol number for 352.Tn TCP , 353available from 354.Xr getprotobyname 3 , 355or 356.Dv IPPROTO_TCP . 357All options are declared in 358.In netinet/tcp.h . 359.Pp 360Options at the 361.Tn IP 362transport level may be used with 363.Tn TCP ; 364see 365.Xr ip 4 . 366Incoming connection requests that are source-routed are noted, 367and the reverse source route is used in responding. 368.Pp 369The default congestion control algorithm for 370.Tn TCP 371is 372.Xr cc_newreno 4 . 373Other congestion control algorithms can be made available using the 374.Xr mod_cc 4 375framework. 376.Ss MIB Variables 377The 378.Tn TCP 379protocol implements a number of variables in the 380.Va net.inet.tcp 381branch of the 382.Xr sysctl 3 383MIB. 384.Bl -tag -width ".Va TCPCTL_DO_RFC1323" 385.It Dv TCPCTL_DO_RFC1323 386.Pq Va rfc1323 387Implement the window scaling and timestamp options of RFC 1323 388(default is true). 389.It Dv TCPCTL_MSSDFLT 390.Pq Va mssdflt 391The default value used for the maximum segment size 392.Pq Dq MSS 393when no advice to the contrary is received from MSS negotiation. 394.It Dv TCPCTL_SENDSPACE 395.Pq Va sendspace 396Maximum 397.Tn TCP 398send window. 399.It Dv TCPCTL_RECVSPACE 400.Pq Va recvspace 401Maximum 402.Tn TCP 403receive window. 404.It Va log_in_vain 405Log any connection attempts to ports where there is not a socket 406accepting connections. 407The value of 1 limits the logging to 408.Tn SYN 409(connection establishment) packets only. 410That of 2 results in any 411.Tn TCP 412packets to closed ports being logged. 413Any value unlisted above disables the logging 414(default is 0, i.e., the logging is disabled). 415.It Va msl 416The Maximum Segment Lifetime, in milliseconds, for a packet. 417.It Va keepinit 418Timeout, in milliseconds, for new, non-established 419.Tn TCP 420connections. 421The default is 75000 msec. 422.It Va keepidle 423Amount of time, in milliseconds, that the connection must be idle 424before keepalive probes (if enabled) are sent. 425The default is 7200000 msec (2 hours). 426.It Va keepintvl 427The interval, in milliseconds, between keepalive probes sent to remote 428machines, when no response is received on a 429.Va keepidle 430probe. 431The default is 75000 msec. 432.It Va keepcnt 433Number of probes sent, with no response, before a connection 434is dropped. 435The default is 8 packets. 436.It Va always_keepalive 437Assume that 438.Dv SO_KEEPALIVE 439is set on all 440.Tn TCP 441connections, the kernel will 442periodically send a packet to the remote host to verify the connection 443is still up. 444.It Va icmp_may_rst 445Certain 446.Tn ICMP 447unreachable messages may abort connections in 448.Tn SYN-SENT 449state. 450.It Va do_tcpdrain 451Flush packets in the 452.Tn TCP 453reassembly queue if the system is low on mbufs. 454.It Va blackhole 455If enabled, disable sending of RST when a connection is attempted 456to a port where there is not a socket accepting connections. 457See 458.Xr blackhole 4 . 459.It Va delayed_ack 460Delay ACK to try and piggyback it onto a data packet. 461.It Va delacktime 462Maximum amount of time, in milliseconds, before a delayed ACK is sent. 463.It Va path_mtu_discovery 464Enable Path MTU Discovery. 465.It Va tcbhashsize 466Size of the 467.Tn TCP 468control-block hash table 469(read-only). 470This may be tuned using the kernel option 471.Dv TCBHASHSIZE 472or by setting 473.Va net.inet.tcp.tcbhashsize 474in the 475.Xr loader 8 . 476.It Va pcbcount 477Number of active process control blocks 478(read-only). 479.It Va syncookies 480Determines whether or not 481.Tn SYN 482cookies should be generated for outbound 483.Tn SYN-ACK 484packets. 485.Tn SYN 486cookies are a great help during 487.Tn SYN 488flood attacks, and are enabled by default. 489(See 490.Xr syncookies 4 . ) 491.It Va isn_reseed_interval 492The interval (in seconds) specifying how often the secret data used in 493RFC 1948 initial sequence number calculations should be reseeded. 494By default, this variable is set to zero, indicating that 495no reseeding will occur. 496Reseeding should not be necessary, and will break 497.Dv TIME_WAIT 498recycling for a few minutes. 499.It Va reass.cursegments 500The current total number of segments present in all reassembly queues. 501.It Va reass.maxsegments 502The maximum limit on the total number of segments across all reassembly 503queues. 504The limit can be adjusted as a tunable. 505.It Va reass.maxqueuelen 506The maximum number of segments allowed in each reassembly queue. 507By default, the system chooses a limit based on each TCP connection's 508receive buffer size and maximum segment size (MSS). 509The actual limit applied to a session's reassembly queue will be the lower of 510the system-calculated automatic limit and the user-specified 511.Va reass.maxqueuelen 512limit. 513.It Va rexmit_initial , rexmit_min , rexmit_slop 514Adjust the retransmit timer calculation for 515.Tn TCP . 516The slop is 517typically added to the raw calculation to take into account 518occasional variances that the 519.Tn SRTT 520(smoothed round-trip time) 521is unable to accommodate, while the minimum specifies an 522absolute minimum. 523While a number of 524.Tn TCP 525RFCs suggest a 1 526second minimum, these RFCs tend to focus on streaming behavior, 527and fail to deal with the fact that a 1 second minimum has severe 528detrimental effects over lossy interactive connections, such 529as a 802.11b wireless link, and over very fast but lossy 530connections for those cases not covered by the fast retransmit 531code. 532For this reason, we use 200ms of slop and a near-0 533minimum, which gives us an effective minimum of 200ms (similar to 534.Tn Linux ) . 535The initial value is used before an RTT measurement has been performed. 536.It Va initcwnd_segments 537Enable the ability to specify initial congestion window in number of segments. 538The default value is 10 as suggested by RFC 6928. 539Changing the value on fly would not affect connections using congestion window 540from the hostcache. 541Caution: 542This regulates the burst of packets allowed to be sent in the first RTT. 543The value should be relative to the link capacity. 544Start with small values for lower-capacity links. 545Large bursts can cause buffer overruns and packet drops if routers have small 546buffers or the link is experiencing congestion. 547.It Va newcwd 548Enable the New Congestion Window Validation mechanism as described in RFC 7661. 549This gently reduces the congestion window during periods, where TCP is 550application limited and the network bandwidth is not utilized completely. 551That prevents self-inflicted packet losses once the application starts to 552transmit data at a higher speed. 553.It Va rfc6675_pipe 554Calculate the bytes in flight using the algorithm described in RFC 6675, and 555is also a prerequisite to enable Proportional Rate Reduction. 556.It Va rfc3042 557Enable the Limited Transmit algorithm as described in RFC 3042. 558It helps avoid timeouts on lossy links and also when the congestion window 559is small, as happens on short transfers. 560.It Va rfc3390 561Enable support for RFC 3390, which allows for a variable-sized 562starting congestion window on new connections, depending on the 563maximum segment size. 564This helps throughput in general, but 565particularly affects short transfers and high-bandwidth large 566propagation-delay connections. 567.It Va sack.enable 568Enable support for RFC 2018, TCP Selective Acknowledgment option, 569which allows the receiver to inform the sender about all successfully 570arrived segments, allowing the sender to retransmit the missing segments 571only. 572.It Va sack.maxholes 573Maximum number of SACK holes per connection. 574Defaults to 128. 575.It Va sack.globalmaxholes 576Maximum number of SACK holes per system, across all connections. 577Defaults to 65536. 578.It Va maxtcptw 579When a TCP connection enters the 580.Dv TIME_WAIT 581state, its associated socket structure is freed, since it is of 582negligible size and use, and a new structure is allocated to contain a 583minimal amount of information necessary for sustaining a connection in 584this state, called the compressed TCP TIME_WAIT state. 585Since this structure is smaller than a socket structure, it can save 586a significant amount of system memory. 587The 588.Va net.inet.tcp.maxtcptw 589MIB variable controls the maximum number of these structures allocated. 590By default, it is initialized to 591.Va kern.ipc.maxsockets 592/ 5. 593.It Va nolocaltimewait 594Suppress creating of compressed TCP TIME_WAIT states for connections in 595which both endpoints are local. 596.It Va fast_finwait2_recycle 597Recycle 598.Tn TCP 599.Dv FIN_WAIT_2 600connections faster when the socket is marked as 601.Dv SBS_CANTRCVMORE 602(no user process has the socket open, data received on 603the socket cannot be read). 604The timeout used here is 605.Va finwait2_timeout . 606.It Va finwait2_timeout 607Timeout to use for fast recycling of 608.Tn TCP 609.Dv FIN_WAIT_2 610connections. 611Defaults to 60 seconds. 612.It Va ecn.enable 613Enable support for TCP Explicit Congestion Notification (ECN). 614ECN allows a TCP sender to reduce the transmission rate in order to 615avoid packet drops. 616Settings: 617.Bl -tag -compact 618.It 0 619Disable ECN. 620.It 1 621Allow incoming connections to request ECN. 622Outgoing connections will request ECN. 623.It 2 624Allow incoming connections to request ECN. 625Outgoing connections will not request ECN. 626.El 627.It Va ecn.maxretries 628Number of retries (SYN or SYN/ACK retransmits) before disabling ECN on a 629specific connection. 630This is needed to help with connection establishment 631when a broken firewall is in the network path. 632.It Va pmtud_blackhole_detection 633Enable automatic path MTU blackhole detection. 634In case of retransmits of MSS sized segments, 635the OS will lower the MSS to check if it's an MTU problem. 636If the current MSS is greater than the configured value to try 637.Po Va net.inet.tcp.pmtud_blackhole_mss 638and 639.Va net.inet.tcp.v6pmtud_blackhole_mss 640.Pc , 641it will be set to this value, otherwise, 642the MSS will be set to the default values 643.Po Va net.inet.tcp.mssdflt 644and 645.Va net.inet.tcp.v6mssdflt 646.Pc . 647Settings: 648.Bl -tag -compact 649.It 0 650Disable path MTU blackhole detection. 651.It 1 652Enable path MTU blackhole detection for IPv4 and IPv6. 653.It 2 654Enable path MTU blackhole detection only for IPv4. 655.It 3 656Enable path MTU blackhole detection only for IPv6. 657.El 658.It Va pmtud_blackhole_mss 659MSS to try for IPv4 if PMTU blackhole detection is turned on. 660.It Va v6pmtud_blackhole_mss 661MSS to try for IPv6 if PMTU blackhole detection is turned on. 662.It Va functions_available 663List of available TCP function blocks (TCP stacks). 664.It Va functions_default 665The default TCP function block (TCP stack). 666.It Va functions_inherit_listen_socket_stack 667Determines whether to inherit listen socket's tcp stack or use the current 668system default tcp stack, as defined by 669.Va functions_default . 670Default is true. 671.It Va insecure_rst 672Use criteria defined in RFC793 instead of RFC5961 for accepting RST segments. 673Default is false. 674.It Va insecure_syn 675Use criteria defined in RFC793 instead of RFC5961 for accepting SYN segments. 676Default is false. 677.It Va ts_offset_per_conn 678When initializing the TCP timestamps, use a per connection offset instead of a 679per host pair offset. 680Default is to use per connection offsets as recommended in RFC 7323. 681.It Va perconn_stats_enable 682Controls the default collection of statistics for all connections using the 683.Xr stats 3 684framework. 6850 disables, 1 enables, 2 enables random sampling across log id connection 686groups with all connections in a group receiving the same setting. 687.It Va perconn_stats_sample_rates 688A CSV list of template_spec=percent key-value pairs which controls the per 689template sampling rates when 690.Xr stats 3 691sampling is enabled. 692.El 693.Sh ERRORS 694A socket operation may fail with one of the following errors returned: 695.Bl -tag -width Er 696.It Bq Er EISCONN 697when trying to establish a connection on a socket which 698already has one; 699.It Bo Er ENOBUFS Bc or Bo Er ENOMEM Bc 700when the system runs out of memory for 701an internal data structure; 702.It Bq Er ETIMEDOUT 703when a connection was dropped 704due to excessive retransmissions; 705.It Bq Er ECONNRESET 706when the remote peer 707forces the connection to be closed; 708.It Bq Er ECONNREFUSED 709when the remote 710peer actively refuses connection establishment (usually because 711no process is listening to the port); 712.It Bq Er EADDRINUSE 713when an attempt 714is made to create a socket with a port which has already been 715allocated; 716.It Bq Er EADDRNOTAVAIL 717when an attempt is made to create a 718socket with a network address for which no network interface 719exists; 720.It Bq Er EAFNOSUPPORT 721when an attempt is made to bind or connect a socket to a multicast 722address. 723.It Bq Er EINVAL 724when trying to change TCP function blocks at an invalid point in the session; 725.It Bq Er ENOENT 726when trying to use a TCP function block that is not available; 727.El 728.Sh SEE ALSO 729.Xr getsockopt 2 , 730.Xr socket 2 , 731.Xr stats 3 , 732.Xr sysctl 3 , 733.Xr blackhole 4 , 734.Xr inet 4 , 735.Xr intro 4 , 736.Xr ip 4 , 737.Xr mod_cc 4 , 738.Xr siftr 4 , 739.Xr syncache 4 , 740.Xr setkey 8 , 741.Xr tcp_functions 9 742.Rs 743.%A "V. Jacobson" 744.%A "R. Braden" 745.%A "D. Borman" 746.%T "TCP Extensions for High Performance" 747.%O "RFC 1323" 748.Re 749.Rs 750.%A "A. Heffernan" 751.%T "Protection of BGP Sessions via the TCP MD5 Signature Option" 752.%O "RFC 2385" 753.Re 754.Rs 755.%A "K. Ramakrishnan" 756.%A "S. Floyd" 757.%A "D. Black" 758.%T "The Addition of Explicit Congestion Notification (ECN) to IP" 759.%O "RFC 3168" 760.Re 761.Sh HISTORY 762The 763.Tn TCP 764protocol appeared in 765.Bx 4.2 . 766The RFC 1323 extensions for window scaling and timestamps were added 767in 768.Bx 4.4 . 769The 770.Dv TCP_INFO 771option was introduced in 772.Tn Linux 2.6 773and is 774.Em subject to change . 775