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.
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.
10 .\" Redistribution and use in source and binary forms, with or without
11 .\" modification, are permitted provided that the following conditions
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.
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
34 .\" From: @(#)tcp.4 8.1 (Berkeley) 6/5/93
42 .Nd Internet Transmission Control Protocol
49 .Fn socket AF_INET SOCK_STREAM 0
53 protocol provides reliable, flow-controlled, two-way
55 It is a byte-stream protocol used to
61 Internet address format and, in addition, provides a per-host
63 .Dq "port addresses" .
64 Thus, each address is composed
65 of an Internet address specifying the host and network,
68 port on the host identifying the peer entity.
76 Active sockets initiate connections to passive
80 sockets are created active; to create a
83 system call must be used
84 after binding the socket with the
87 Only passive sockets may use the
89 call to accept incoming connections.
90 Only active sockets may use the
92 call to initiate connections.
96 their location to match
97 incoming connection requests from multiple networks.
98 This technique, termed
99 .Dq "wildcard addressing" ,
101 server to provide service to clients on multiple networks.
102 To create a socket which listens on all networks, the Internet
108 port may still be specified
109 at this time; if the port is not specified, the system will assign one.
110 Once a connection has been established, the socket's address is
111 fixed by the peer entity's location.
112 The address assigned to the
113 socket is the address associated with the network interface
114 through which packets are being transmitted and received.
115 Normally, this address corresponds to the peer entity's network.
118 supports a number of socket options which can be set with
122 .Bl -tag -width ".Dv TCP_FUNCTION_BLK"
124 Information about a socket's underlying TCP session may be retrieved
125 by passing the read-only option
129 It accepts a single argument: a pointer to an instance of
130 .Vt "struct tcp_info" .
132 This API is subject to change; consult the source to determine
133 which fields are currently filled out by this option.
135 specific additions include
139 bandwidth-controlled window space.
141 Set or query congestion control algorithm specific parameters.
145 .It Dv TCP_CONGESTION
146 Select or query the congestion control algorithm that TCP will use for the
152 Enable or disable TCP Fast Open (TFO).
153 To use this option, the kernel must be built with the
157 This option can be set on the socket either before or after the
160 Clearing this option on a listen socket after it has been set has no effect on
161 existing TFO connections or TFO connections in progress; it only prevents new
162 TFO connections from being established.
164 For passively-created sockets, the
166 socket option can be queried to determine whether the connection was established
168 Note that connections that are established via a TFO
170 but that fall back to using a non-TFO
176 In addition to the facilities defined in RFC7413, this implementation supports a
177 pre-shared key (PSK) mode of operation in which the TFO server requires the
178 client to be in posession of a shared secret in order for the client to be able
179 to successfully open TFO connections with the server.
180 This is useful, for example, in environments where TFO servers are exposed to
181 both internal and external clients and only wish to allow TFO connections from
184 In the PSK mode of operation, the server generates and sends TFO cookies to
185 requesting clients as usual.
186 However, when validating cookies received in TFO SYNs from clients, the server
187 requires the client-supplied cookie to equal
188 .Bd -literal -offset left
189 SipHash24(key=\fI16-byte-psk\fP, msg=\fIcookie-sent-to-client\fP)
192 Multiple concurrent valid pre-shared keys are supported so that time-based
193 rolling PSK invalidation policies can be implemented in the system.
194 The default number of concurrent pre-shared keys is 2.
196 This can be adjusted with the
197 .Dv TCP_RFC7413_MAX_PSKS
199 .It Dv TCP_FUNCTION_BLK
200 Select or query the set of functions that TCP will use for this connection.
201 This allows a user to select an alternate TCP stack.
202 The alternate TCP stack must already be loaded in the kernel.
203 To list the available TCP stacks, see
204 .Va functions_available
207 section further down.
208 To list the default TCP stack, see
209 .Va functions_default
216 option accepts a per-socket timeout argument of
218 in seconds, for new, non-established
221 For the global default in milliseconds see
225 section further down.
229 option accepts an argument of
231 for the amount of time, in seconds, that the connection must be idle
232 before keepalive probes (if enabled) are sent for the connection of this
234 If set on a listening socket, the value is inherited by the newly created
237 For the global default in milliseconds see
241 section further down.
245 option accepts an argument of
247 to set the per-socket interval, in seconds, between keepalive probes sent
249 If set on a listening socket, the value is inherited by the newly created
252 For the global default in milliseconds see
256 section further down.
260 option accepts an argument of
262 and allows a per-socket tuning of the number of probes sent, with no response,
263 before the connection will be dropped.
264 If set on a listening socket, the value is inherited by the newly created
267 For the global default see the
271 section further down.
273 Under most circumstances,
275 sends data when it is presented;
276 when outstanding data has not yet been acknowledged, it gathers
277 small amounts of output to be sent in a single packet once
278 an acknowledgement is received.
279 For a small number of clients, such as window systems
280 that send a stream of mouse events which receive no replies,
281 this packetization may cause significant delays.
284 defeats this algorithm.
286 By default, a sender- and
287 .No receiver- Ns Tn TCP
288 will negotiate among themselves to determine the maximum segment size
289 to be used for each connection.
292 option allows the user to determine the result of this negotiation,
293 and to reduce it if desired.
296 usually sends a number of options in each packet, corresponding to
299 extensions which are provided in this implementation.
302 is provided to disable
304 option use on a per-connection basis.
307 .No sender- Ns Tn TCP
310 bit, and begin transmission immediately (if permitted) at the end of
315 When this option is set to a non-zero value,
317 will delay sending any data at all until either the socket is closed,
318 or the internal send buffer is filled.
320 This option enables the use of MD5 digests (also known as TCP-MD5)
321 on writes to the specified socket.
322 Outgoing traffic is digested;
323 digests on incoming traffic are verified.
324 When this option is enabled on a socket, all inbound and outgoing
325 TCP segments must be signed with MD5 digests.
327 One common use for this in a
329 router deployment is to enable
330 based routers to interwork with Cisco equipment at peering points.
331 Support for this feature conforms to RFC 2385.
333 In order for this option to function correctly, it is necessary for the
334 administrator to add a tcp-md5 key entry to the system's security
335 associations database (SADB) using the
338 This entry can only be specified on a per-host basis at this time.
340 If an SADB entry cannot be found for the destination,
341 the system does not send any outgoing segments and drops any inbound segments.
342 However, during connection negotiation, a non-signed segment will be accepted if
343 an SADB entry does not exist between hosts.
344 When a non-signed segment is accepted, the established connection is not
345 protected with MD5 digests.
347 Manage collection of connection level statistics using the
351 Each dropped segment is taken into account in the TCP protocol statistics.
352 .It Dv TCP_TXTLS_ENABLE
353 Enable in-kernel Transport Layer Security (TLS) for data written to this
358 .It Dv TCP_TXTLS_MODE
359 The integer argument can be used to get or set the current TLS transmit mode
364 .It Dv TCP_RXTLS_ENABLE
365 Enable in-kernel TLS for data read from this socket.
369 .It Dv TCP_REUSPORT_LB_NUMA
370 Changes NUMA affinity filtering for an established TCP listen
372 This option takes a single integer argument which specifies
373 the NUMA domain to filter on for this listen socket.
374 The argument can also have the follwing special values:
375 .Bl -tag -width "Dv TCP_REUSPORT_LB_NUMA"
376 .It Dv TCP_REUSPORT_LB_NUMA_NODOM
377 Remove NUMA filtering for this listen socket.
378 .It Dv TCP_REUSPORT_LB_NUMA_CURDOM
379 Filter traffic associated with the domain where the calling thread is
381 This is typically used after a process or thread inherits a listen
382 socket from its parent, and sets its CPU affinity to a particular core.
384 .It Dv TCP_REMOTE_UDP_ENCAPS_PORT
385 Set and get the remote UDP encapsulation port.
386 It can only be set on a closed TCP socket.
389 The option level for the
391 call is the protocol number for
394 .Xr getprotobyname 3 ,
397 All options are declared in
402 transport level may be used with
406 Incoming connection requests that are source-routed are noted,
407 and the reverse source route is used in responding.
409 The default congestion control algorithm for
413 Other congestion control algorithms can be made available using the
419 protocol implements a number of variables in the
424 .Bl -tag -width ".Va TCPCTL_DO_RFC1323"
425 .It Dv TCPCTL_DO_RFC1323
427 Implement the window scaling and timestamp options of RFC 1323/RFC 7323
429 .It Va tolerate_missing_ts
430 Tolerate the missing of timestamps (RFC 1323/RFC 7323) for
432 segments belonging to
434 connections for which support of
436 timestamps has been negotiated.
437 As of June 2021, several TCP stacks are known to violate RFC 7323, including
438 modern widely deployed ones.
439 Therefore the default is 1, i.e., the missing of timestamps is tolerated.
440 .It Dv TCPCTL_MSSDFLT
442 The default value used for the maximum segment size
444 when no advice to the contrary is received from MSS negotiation.
445 .It Dv TCPCTL_SENDSPACE
450 .It Dv TCPCTL_RECVSPACE
456 Log any connection attempts to ports where there is not a socket
457 accepting connections.
458 The value of 1 limits the logging to
460 (connection establishment) packets only.
461 That of 2 results in any
463 packets to closed ports being logged.
464 Any value unlisted above disables the logging
465 (default is 0, i.e., the logging is disabled).
467 The Maximum Segment Lifetime, in milliseconds, for a packet.
469 Timeout, in milliseconds, for new, non-established
472 The default is 75000 msec.
474 Amount of time, in milliseconds, that the connection must be idle
475 before keepalive probes (if enabled) are sent.
476 The default is 7200000 msec (2 hours).
478 The interval, in milliseconds, between keepalive probes sent to remote
479 machines, when no response is received on a
482 The default is 75000 msec.
484 Number of probes sent, with no response, before a connection
486 The default is 8 packets.
487 .It Va always_keepalive
492 connections, the kernel will
493 periodically send a packet to the remote host to verify the connection
498 unreachable messages may abort connections in
504 reassembly queue if the system is low on mbufs.
506 If enabled, disable sending of RST when a connection is attempted
507 to a port where there is not a socket accepting connections.
511 Delay ACK to try and piggyback it onto a data packet.
513 Maximum amount of time, in milliseconds, before a delayed ACK is sent.
514 .It Va path_mtu_discovery
515 Enable Path MTU Discovery.
519 control-block hash table
521 This may be tuned using the kernel option
524 .Va net.inet.tcp.tcbhashsize
528 Number of active process control blocks
531 Determines whether or not
533 cookies should be generated for outbound
537 cookies are a great help during
539 flood attacks, and are enabled by default.
542 .It Va isn_reseed_interval
543 The interval (in seconds) specifying how often the secret data used in
544 RFC 1948 initial sequence number calculations should be reseeded.
545 By default, this variable is set to zero, indicating that
546 no reseeding will occur.
547 Reseeding should not be necessary, and will break
549 recycling for a few minutes.
550 .It Va reass.cursegments
551 The current total number of segments present in all reassembly queues.
552 .It Va reass.maxsegments
553 The maximum limit on the total number of segments across all reassembly
555 The limit can be adjusted as a tunable.
556 .It Va reass.maxqueuelen
557 The maximum number of segments allowed in each reassembly queue.
558 By default, the system chooses a limit based on each TCP connection's
559 receive buffer size and maximum segment size (MSS).
560 The actual limit applied to a session's reassembly queue will be the lower of
561 the system-calculated automatic limit and the user-specified
562 .Va reass.maxqueuelen
564 .It Va rexmit_initial , rexmit_min , rexmit_slop
565 Adjust the retransmit timer calculation for
568 typically added to the raw calculation to take into account
569 occasional variances that the
571 (smoothed round-trip time)
572 is unable to accommodate, while the minimum specifies an
577 second minimum, these RFCs tend to focus on streaming behavior,
578 and fail to deal with the fact that a 1 second minimum has severe
579 detrimental effects over lossy interactive connections, such
580 as a 802.11b wireless link, and over very fast but lossy
581 connections for those cases not covered by the fast retransmit
583 For this reason, we use 200ms of slop and a near-0
584 minimum, which gives us an effective minimum of 200ms (similar to
586 The initial value is used before an RTT measurement has been performed.
587 .It Va initcwnd_segments
588 Enable the ability to specify initial congestion window in number of segments.
589 The default value is 10 as suggested by RFC 6928.
590 Changing the value on fly would not affect connections using congestion window
593 This regulates the burst of packets allowed to be sent in the first RTT.
594 The value should be relative to the link capacity.
595 Start with small values for lower-capacity links.
596 Large bursts can cause buffer overruns and packet drops if routers have small
597 buffers or the link is experiencing congestion.
599 Enable the New Congestion Window Validation mechanism as described in RFC 7661.
600 This gently reduces the congestion window during periods, where TCP is
601 application limited and the network bandwidth is not utilized completely.
602 That prevents self-inflicted packet losses once the application starts to
603 transmit data at a higher speed.
605 Enable Lost Retransmission Detection for SACK-enabled sessions, disabled by
607 Under severe congestion, a retransmission can be lost which then leads to a
608 mandatory Retransmission Timeout (RTO), followed by slow-start.
609 LRD will try to resend the repeatedly lost packet, preventing the time-consuming
610 RTO and performance reducing slow-start.
612 Perform SACK loss recovery using the Proportional Rate Reduction (PRR) algorithm
613 described in RFC6937.
614 This improves the effectiveness of retransmissions particular in environments
615 with ACK thinning or burst loss events, as chances to run out of the ACK clock
616 are reduced, preventing lengthy and performance reducing RTO based loss recovery
618 .It Va do_prr_conservative
619 While doing Proportional Rate Reduction, remain strictly in a packet conserving
620 mode, sending only one new packet for each ACK received.
621 Helpful when a misconfigured token bucket traffic policer causes persistent
622 high losses leading to RTO, but reduces PRR effectiveness in more common settings
625 Deprecated and superseded by
628 Enable the Limited Transmit algorithm as described in RFC 3042.
629 It helps avoid timeouts on lossy links and also when the congestion window
630 is small, as happens on short transfers.
632 Enable support for RFC 3390, which allows for a variable-sized
633 starting congestion window on new connections, depending on the
634 maximum segment size.
635 This helps throughput in general, but
636 particularly affects short transfers and high-bandwidth large
637 propagation-delay connections.
639 Enable support for RFC 2018, TCP Selective Acknowledgment option,
640 which allows the receiver to inform the sender about all successfully
641 arrived segments, allowing the sender to retransmit the missing segments
644 Enables three updated mechanisms from RFC6675 (default is true).
645 Calculate the bytes in flight using the algorithm described in RFC 6675, and
646 is also an improvement when Proportional Rate Reduction is enabled.
647 Next, Rescue Retransmission helps timely loss recovery, when the trailing segments
648 of a transmission are lost, while no additional data is ready to be sent.
649 In case a partial ACK without a SACK block is received during SACK loss
650 recovery, the trailing segment is immediately resent, rather than waiting
651 for a Retransmission timeout.
652 Finally, SACK loss recovery is also engaged, once two segments plus one byte are
653 SACKed - even if no traditional duplicate ACKs were observed.
655 Maximum number of SACK holes per connection.
657 .It Va sack.globalmaxholes
658 Maximum number of SACK holes per system, across all connections.
661 When a TCP connection enters the
663 state, its associated socket structure is freed, since it is of
664 negligible size and use, and a new structure is allocated to contain a
665 minimal amount of information necessary for sustaining a connection in
666 this state, called the compressed TCP TIME_WAIT state.
667 Since this structure is smaller than a socket structure, it can save
668 a significant amount of system memory.
670 .Va net.inet.tcp.maxtcptw
671 MIB variable controls the maximum number of these structures allocated.
672 By default, it is initialized to
673 .Va kern.ipc.maxsockets
675 .It Va nolocaltimewait
676 Suppress creating of compressed TCP TIME_WAIT states for connections in
677 which both endpoints are local.
678 .It Va fast_finwait2_recycle
682 connections faster when the socket is marked as
684 (no user process has the socket open, data received on
685 the socket cannot be read).
686 The timeout used here is
687 .Va finwait2_timeout .
688 .It Va finwait2_timeout
689 Timeout to use for fast recycling of
693 Defaults to 60 seconds.
695 Enable support for TCP Explicit Congestion Notification (ECN).
696 ECN allows a TCP sender to reduce the transmission rate in order to
702 Allow incoming connections to request ECN.
703 Outgoing connections will request ECN.
705 Allow incoming connections to request ECN.
706 Outgoing connections will not request ECN.
709 .It Va ecn.maxretries
710 Number of retries (SYN or SYN/ACK retransmits) before disabling ECN on a
712 This is needed to help with connection establishment
713 when a broken firewall is in the network path.
714 .It Va pmtud_blackhole_detection
715 Enable automatic path MTU blackhole detection.
716 In case of retransmits of MSS sized segments,
717 the OS will lower the MSS to check if it's an MTU problem.
718 If the current MSS is greater than the configured value to try
719 .Po Va net.inet.tcp.pmtud_blackhole_mss
721 .Va net.inet.tcp.v6pmtud_blackhole_mss
723 it will be set to this value, otherwise,
724 the MSS will be set to the default values
725 .Po Va net.inet.tcp.mssdflt
727 .Va net.inet.tcp.v6mssdflt
732 Disable path MTU blackhole detection.
734 Enable path MTU blackhole detection for IPv4 and IPv6.
736 Enable path MTU blackhole detection only for IPv4.
738 Enable path MTU blackhole detection only for IPv6.
740 .It Va pmtud_blackhole_mss
741 MSS to try for IPv4 if PMTU blackhole detection is turned on.
742 .It Va v6pmtud_blackhole_mss
743 MSS to try for IPv6 if PMTU blackhole detection is turned on.
744 .It Va fastopen.acceptany
745 When non-zero, all client-supplied TFO cookies will be considered to be valid.
747 .It Va fastopen.autokey
749 .Va net.inet.tcp.fastopen.server_enable
750 are non-zero, a new key will be automatically generated after this specified
753 .It Va fastopen.ccache_bucket_limit
754 The maximum number of entries in a client cookie cache bucket.
755 The default value can be tuned with the
756 .Dv TCP_FASTOPEN_CCACHE_BUCKET_LIMIT_DEFAULT
757 kernel option or by setting
758 .Va net.inet.tcp.fastopen_ccache_bucket_limit
761 .It Va fastopen.ccache_buckets
762 The number of client cookie cache buckets.
764 The value can be tuned with the
765 .Dv TCP_FASTOPEN_CCACHE_BUCKETS_DEFAULT
766 kernel option or by setting
767 .Va fastopen.ccache_buckets
770 .It Va fastopen.ccache_list
771 Print the client cookie cache.
773 .It Va fastopen.client_enable
774 When zero, no new active (i.e., client) TFO connections can be created.
775 On the transition from enabled to disabled, the client cookie cache is cleared
777 The transition from enabled to disabled does not affect any active TFO
778 connections in progress; it only prevents new ones from being established.
780 .It Va fastopen.keylen
781 The key length in bytes.
783 .It Va fastopen.maxkeys
784 The maximum number of keys supported.
786 .It Va fastopen.maxpsks
787 The maximum number of pre-shared keys supported.
789 .It Va fastopen.numkeys
790 The current number of keys installed.
792 .It Va fastopen.numpsks
793 The current number of pre-shared keys installed.
795 .It Va fastopen.path_disable_time
796 When a failure occurs while trying to create a new active (i.e., client) TFO
797 connection, new active connections on the same path, as determined by the tuple
798 .Brq client_ip, server_ip, server_port ,
799 will be forced to be non-TFO for this many seconds.
800 Note that the path disable mechanism relies on state stored in client cookie
801 cache entries, so it is possible for the disable time for a given path to be
802 reduced if the corresponding client cookie cache entry is reused due to resource
803 pressure before the disable period has elapsed.
805 .Dv TCP_FASTOPEN_PATH_DISABLE_TIME_DEFAULT .
806 .It Va fastopen.psk_enable
807 When non-zero, pre-shared key (PSK) mode is enabled for all TFO servers.
808 On the transition from enabled to disabled, all installed pre-shared keys are
811 .It Va fastopen.server_enable
812 When zero, no new passive (i.e., server) TFO connections can be created.
813 On the transition from enabled to disabled, all installed keys and pre-shared
815 On the transition from disabled to enabled, if
817 is non-zero and there are no keys installed, a new key will be generated
819 The transition from enabled to disabled does not affect any passive TFO
820 connections in progress; it only prevents new ones from being established.
822 .It Va fastopen.setkey
823 Install a new key by writing
824 .Va net.inet.tcp.fastopen.keylen
825 bytes to this sysctl.
826 .It Va fastopen.setpsk
827 Install a new pre-shared key by writing
828 .Va net.inet.tcp.fastopen.keylen
829 bytes to this sysctl.
830 .It Va hostcache.enable
831 The TCP host cache is used to cache connection details and metrics to
832 improve future performance of connections between the same hosts.
833 At the completion of a TCP connection, a host will cache information
834 for the connection for some defined period of time.
837 Disable the host cache.
839 Enable the host cache. (default)
841 .It Va hostcache.purgenow
842 Immediately purge all entries once set to any value.
843 Setting this to 2 will also reseed the hash salt.
844 .It Va hostcache.purge
845 Expire all entires on next pruning of host cache entries.
846 Any non-zero setting will be reset to zero, once the pruge
850 Do not purge all entries when pruning the host cache. (default)
852 Purge all entries when doing the next pruning.
854 Purge all entries, and also reseed the hash salt.
856 .It Va hostcache.prune
857 Time in seconds between pruning expired host cache entries.
858 Defaults to 300 (5 minutes).
859 .It Va hostcache.expire
860 Time in seconds, how long a entry should be kept in the
861 host cache since last accessed.
862 Defaults to 3600 (1 hour).
863 .It Va hostcache.count
864 The current number of entries in the host cache.
865 .It Va hostcache.bucketlimit
866 The maximum number of entries for the same hash.
868 .It Va hostcache.hashsize
869 Size of TCP hostcache hashtable.
870 This number has to be a power of two, or will be rejected.
872 .It Va hostcache.cachelimit
873 Overall entry limit for hostcache.
874 Defaults to hashsize * bucketlimit.
875 .It Va hostcache.histo
876 Provide a Histogram of the hostcache hash utilization.
877 .It Va hostcache.list
878 Provide a complete list of all current entries in the host
880 .It Va functions_available
881 List of available TCP function blocks (TCP stacks).
882 .It Va functions_default
883 The default TCP function block (TCP stack).
884 .It Va functions_inherit_listen_socket_stack
885 Determines whether to inherit listen socket's tcp stack or use the current
886 system default tcp stack, as defined by
887 .Va functions_default .
890 Use criteria defined in RFC793 instead of RFC5961 for accepting RST segments.
893 Use criteria defined in RFC793 instead of RFC5961 for accepting SYN segments.
895 .It Va ts_offset_per_conn
896 When initializing the TCP timestamps, use a per connection offset instead of a
897 per host pair offset.
898 Default is to use per connection offsets as recommended in RFC 7323.
899 .It Va perconn_stats_enable
900 Controls the default collection of statistics for all connections using the
903 0 disables, 1 enables, 2 enables random sampling across log id connection
904 groups with all connections in a group receiving the same setting.
905 .It Va perconn_stats_sample_rates
906 A CSV list of template_spec=percent key-value pairs which controls the per
907 template sampling rates when
910 .It Va udp_tunneling_port
911 The local UDP encapsulation port.
912 A value of 0 indicates that UDP encapsulation is disabled.
914 .It Va udp_tunneling_overhead
915 The overhead taken into account when using UDP encapsulation.
916 Since MSS clamping by middleboxes will most likely not work, values larger than
917 8 (the size of the UDP header) are also supported.
918 Supported values are between 8 and 1024.
922 A socket operation may fail with one of the following errors returned:
925 when trying to establish a connection on a socket which
927 .It Bo Er ENOBUFS Bc or Bo Er ENOMEM Bc
928 when the system runs out of memory for
929 an internal data structure;
931 when a connection was dropped
932 due to excessive retransmissions;
935 forces the connection to be closed;
936 .It Bq Er ECONNREFUSED
938 peer actively refuses connection establishment (usually because
939 no process is listening to the port);
942 is made to create a socket with a port which has already been
944 .It Bq Er EADDRNOTAVAIL
945 when an attempt is made to create a
946 socket with a network address for which no network interface
948 .It Bq Er EAFNOSUPPORT
949 when an attempt is made to bind or connect a socket to a multicast
952 when trying to change TCP function blocks at an invalid point in the session;
954 when trying to use a TCP function block that is not available;
976 .%T "TCP Extensions for High Performance"
983 .%A "R. Scheffenegger"
984 .%T "TCP Extensions for High Performance"
989 .%T "Protection of BGP Sessions via the TCP MD5 Signature Option"
993 .%A "K. Ramakrishnan"
996 .%T "The Addition of Explicit Congestion Notification (ECN) to IP"
1002 protocol appeared in
1004 The RFC 1323 extensions for window scaling and timestamps were added
1009 option was introduced in
1012 .Em subject to change .
projects / FreeBSD / FreeBSD.git / blob