.\" Copyright (c) 1983, 1991 The Regents of the University of California.
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the University of
.\" California, Berkeley and its contributors.
.\" 4. Neither the name of the University nor the names of its contributors
.\" may be used to endorse or promote products derived from this software
.\" without specific prior written permission.
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" @(#)tcp.4 6.5 (Berkeley) 3/28/91
.Nd Internet Transmission Control Protocol
.Fd #include <sys/socket.h>
.Fd #include <netinet/in.h>
.Fn socket AF_INET SOCK_STREAM 0
protocol provides reliable, flow-controlled, two-way
transmission of data. It is a byte-stream protocol used to
abstraction. TCP uses the standard
Internet address format and, in addition, provides a per-host
Thus, each address is composed
of an Internet address specifying the host and network, with
port on the host identifying the peer entity.
Sockets utilizing the tcp protocol are either
Active sockets initiate connections to passive
sockets are created active; to create a
after binding the socket with the
passive sockets may use the
call to accept incoming connections. Only active sockets may
call to initiate connections.
incoming connection requests from multiple networks. This
.Dq wildcard addressing ,
server to provide service to clients on multiple networks.
To create a socket which listens on all networks, the Internet
port may still be specified
at this time; if the port is not specified the system will assign one.
Once a connection has been established the socket's address is
fixed by the peer entity's location. The address assigned the
socket is the address associated with the network interface
through which packets are being transmitted and received. Normally
this address corresponds to the peer entity's network.
supports one socket option which is set with
Under most circumstances,
sends data when it is presented;
when outstanding data has not yet been acknowledged, it gathers
small amounts of output to be sent in a single packet once
an acknowledgement is received.
For a small number of clients, such as window systems
that send a stream of mouse events which receive no replies,
this packetization may cause significant delays.
provides a boolean option,
to defeat this algorithm.
call is the protocol number for
transport level may be used with
Incoming connection requests that are source-routed are noted,
and the reverse source route is used in responding.
A socket operation may fail with one of the following errors returned:
.Bl -tag -width [EADDRNOTAVAIL]
when trying to establish a connection on a socket which
when the system runs out of memory for
an internal data structure;
when a connection was dropped
due to excessive retransmissions;
forces the connection to be closed;
peer actively refuses connection establishment (usually because
no process is listening to the port);
is made to create a socket with a port which has already been
when an attempt is made to create a
socket with a network address for which no network interface
protocol stack appeared in