1994-05-30 19:09:18 +00:00
|
|
|
.\" Copyright (c) 1983, 1991, 1993
|
|
|
|
.\" The Regents of the University of California. All rights reserved.
|
|
|
|
.\"
|
|
|
|
.\" Redistribution and use in source and binary forms, with or without
|
|
|
|
.\" modification, are permitted provided that the following conditions
|
|
|
|
.\" are met:
|
|
|
|
.\" 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.
|
2014-03-14 03:07:51 +00:00
|
|
|
.\" 3. Neither the name of the University nor the names of its contributors
|
1994-05-30 19:09:18 +00:00
|
|
|
.\" 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
|
|
|
|
.\" SUCH DAMAGE.
|
|
|
|
.\"
|
1995-02-15 03:30:54 +00:00
|
|
|
.\" From: @(#)inet.4 8.1 (Berkeley) 6/5/93
|
1999-08-28 00:22:10 +00:00
|
|
|
.\" $FreeBSD$
|
1994-05-30 19:09:18 +00:00
|
|
|
.\"
|
2021-11-12 16:56:46 +00:00
|
|
|
.Dd November 12, 2021
|
1994-05-30 19:09:18 +00:00
|
|
|
.Dt INET 4
|
2001-07-10 15:31:11 +00:00
|
|
|
.Os
|
1994-05-30 19:09:18 +00:00
|
|
|
.Sh NAME
|
|
|
|
.Nm inet
|
|
|
|
.Nd Internet protocol family
|
|
|
|
.Sh SYNOPSIS
|
2001-10-01 16:09:29 +00:00
|
|
|
.In sys/types.h
|
|
|
|
.In netinet/in.h
|
1994-05-30 19:09:18 +00:00
|
|
|
.Sh DESCRIPTION
|
|
|
|
The Internet protocol family is a collection of protocols
|
|
|
|
layered atop the
|
2004-07-03 18:29:24 +00:00
|
|
|
.Em Internet Protocol
|
1994-05-30 19:09:18 +00:00
|
|
|
.Pq Tn IP
|
|
|
|
transport layer, and utilizing the Internet address format.
|
|
|
|
The Internet family provides protocol support for the
|
|
|
|
.Dv SOCK_STREAM , SOCK_DGRAM ,
|
|
|
|
and
|
|
|
|
.Dv SOCK_RAW
|
|
|
|
socket types; the
|
|
|
|
.Dv SOCK_RAW
|
|
|
|
interface provides access to the
|
|
|
|
.Tn IP
|
|
|
|
protocol.
|
|
|
|
.Sh ADDRESSING
|
|
|
|
Internet addresses are four byte quantities, stored in
|
2004-06-16 08:33:57 +00:00
|
|
|
network standard format (on little endian machines, such as the
|
2003-10-14 02:59:13 +00:00
|
|
|
.Tn alpha ,
|
2014-07-07 00:27:09 +00:00
|
|
|
.Tn amd64
|
2003-10-14 02:59:13 +00:00
|
|
|
and
|
2014-07-07 00:27:09 +00:00
|
|
|
.Tn i386
|
2003-10-14 02:59:13 +00:00
|
|
|
these are word and byte reversed).
|
2003-06-28 23:53:39 +00:00
|
|
|
The include file
|
2003-09-08 19:57:22 +00:00
|
|
|
.In netinet/in.h
|
1994-05-30 19:09:18 +00:00
|
|
|
defines this address
|
|
|
|
as a discriminated union.
|
|
|
|
.Pp
|
|
|
|
Sockets bound to the Internet protocol family utilize
|
|
|
|
the following addressing structure,
|
|
|
|
.Bd -literal -offset indent
|
|
|
|
struct sockaddr_in {
|
2003-03-23 08:23:43 +00:00
|
|
|
uint8_t sin_len;
|
|
|
|
sa_family_t sin_family;
|
|
|
|
in_port_t sin_port;
|
|
|
|
struct in_addr sin_addr;
|
|
|
|
char sin_zero[8];
|
1994-05-30 19:09:18 +00:00
|
|
|
};
|
|
|
|
.Ed
|
|
|
|
.Pp
|
|
|
|
Sockets may be created with the local address
|
|
|
|
.Dv INADDR_ANY
|
2001-07-16 10:52:19 +00:00
|
|
|
to affect
|
1994-05-30 19:09:18 +00:00
|
|
|
.Dq wildcard
|
2001-07-14 19:41:16 +00:00
|
|
|
matching on incoming messages.
|
1994-05-30 19:09:18 +00:00
|
|
|
The address in a
|
|
|
|
.Xr connect 2
|
|
|
|
or
|
|
|
|
.Xr sendto 2
|
|
|
|
call may be given as
|
|
|
|
.Dv INADDR_ANY
|
|
|
|
to mean
|
|
|
|
.Dq this host .
|
|
|
|
The distinguished address
|
|
|
|
.Dv INADDR_BROADCAST
|
|
|
|
is allowed as a shorthand for the broadcast address on the primary
|
|
|
|
network if the first network configured supports broadcast.
|
|
|
|
.Sh PROTOCOLS
|
|
|
|
The Internet protocol family is comprised of
|
|
|
|
the
|
|
|
|
.Tn IP
|
1995-02-15 03:30:54 +00:00
|
|
|
network protocol, Internet Control
|
1994-05-30 19:09:18 +00:00
|
|
|
Message Protocol
|
|
|
|
.Pq Tn ICMP ,
|
1995-02-15 03:30:54 +00:00
|
|
|
Internet Group Management Protocol
|
|
|
|
.Pq Tn IGMP ,
|
1994-05-30 19:09:18 +00:00
|
|
|
Transmission Control
|
|
|
|
Protocol
|
|
|
|
.Pq Tn TCP ,
|
|
|
|
and User Datagram Protocol
|
|
|
|
.Pq Tn UDP .
|
|
|
|
.Tn TCP
|
|
|
|
is used to support the
|
|
|
|
.Dv SOCK_STREAM
|
|
|
|
abstraction while
|
|
|
|
.Tn UDP
|
|
|
|
is used to support the
|
|
|
|
.Dv SOCK_DGRAM
|
2003-06-28 23:53:39 +00:00
|
|
|
abstraction.
|
|
|
|
A raw interface to
|
1994-05-30 19:09:18 +00:00
|
|
|
.Tn IP
|
|
|
|
is available
|
|
|
|
by creating an Internet socket of type
|
|
|
|
.Dv SOCK_RAW .
|
|
|
|
The
|
|
|
|
.Tn ICMP
|
|
|
|
message protocol is accessible from a raw socket.
|
|
|
|
.Pp
|
2012-01-26 10:42:25 +00:00
|
|
|
The
|
|
|
|
.Nm
|
|
|
|
address on an interface consist of the address itself, the
|
|
|
|
netmask, either broadcast address in case of a broadcast
|
|
|
|
interface or peers address in case of point-to-point interface.
|
|
|
|
The following
|
1994-05-30 19:09:18 +00:00
|
|
|
.Xr ioctl 2
|
2012-01-26 10:42:25 +00:00
|
|
|
commands are provided for a datagram socket in the Internet domain:
|
|
|
|
.Pp
|
2016-06-08 10:26:17 +00:00
|
|
|
.Bl -tag -width ".Dv SIOCGIFBRDADDR" -offset indent -compact
|
2012-01-26 10:42:25 +00:00
|
|
|
.It Dv SIOCAIFADDR
|
|
|
|
Add address to an interface.
|
|
|
|
The command requires
|
|
|
|
.Ft struct in_aliasreq
|
|
|
|
as argument.
|
|
|
|
.It Dv SIOCDIFADDR
|
|
|
|
Delete address from an interface.
|
|
|
|
The command requires
|
|
|
|
.Ft struct ifreq
|
|
|
|
as argument.
|
|
|
|
.It Dv SIOCGIFADDR
|
|
|
|
.It Dv SIOCGIFBRDADDR
|
|
|
|
.It Dv SIOCGIFDSTADDR
|
1994-05-30 19:09:18 +00:00
|
|
|
.It Dv SIOCGIFNETMASK
|
2016-06-08 08:50:35 +00:00
|
|
|
Return address information from interface.
|
|
|
|
The returned value is in
|
2012-01-26 10:42:25 +00:00
|
|
|
.Ft struct ifreq .
|
|
|
|
This way of address information retrieval is obsoleted, a
|
|
|
|
preferred way is to use
|
|
|
|
.Xr getifaddrs 3
|
|
|
|
API.
|
1994-05-30 19:09:18 +00:00
|
|
|
.El
|
2000-03-15 03:38:22 +00:00
|
|
|
.Ss MIB Variables
|
1995-02-15 03:30:54 +00:00
|
|
|
A number of variables are implemented in the net.inet branch of the
|
|
|
|
.Xr sysctl 3
|
2000-03-15 03:38:22 +00:00
|
|
|
MIB.
|
|
|
|
In addition to the variables supported by the transport protocols
|
|
|
|
(for which the respective manual pages may be consulted),
|
|
|
|
the following general variables are defined:
|
2016-02-04 21:39:58 +00:00
|
|
|
.Bl -tag -width IPCTL_ACCEPTSOURCEROUTE
|
1995-02-15 03:30:54 +00:00
|
|
|
.It Dv IPCTL_FORWARDING
|
|
|
|
.Pq ip.forwarding
|
1999-03-20 10:25:40 +00:00
|
|
|
Boolean: enable/disable forwarding of IP packets.
|
|
|
|
Defaults to off.
|
1995-02-15 03:30:54 +00:00
|
|
|
.It Dv IPCTL_SENDREDIRECTS
|
|
|
|
.Pq ip.redirect
|
|
|
|
Boolean: enable/disable sending of ICMP redirects in response to
|
|
|
|
.Tn IP
|
2004-10-23 18:45:53 +00:00
|
|
|
packets for which a better, and for the sender directly reachable, route
|
|
|
|
and next hop is known.
|
2000-03-01 14:50:24 +00:00
|
|
|
Defaults to on.
|
1995-02-15 03:30:54 +00:00
|
|
|
.It Dv IPCTL_DEFTTL
|
|
|
|
.Pq ip.ttl
|
|
|
|
Integer: default time-to-live
|
|
|
|
.Pq Dq TTL
|
2001-07-14 19:41:16 +00:00
|
|
|
to use for outgoing
|
1995-02-15 03:30:54 +00:00
|
|
|
.Tn IP
|
|
|
|
packets.
|
2003-01-17 14:07:03 +00:00
|
|
|
.It Dv IPCTL_ACCEPTSOURCEROUTE
|
|
|
|
.Pq ip.accept_sourceroute
|
|
|
|
Boolean: enable/disable accepting of source-routed IP packets (default false).
|
1995-03-16 18:24:19 +00:00
|
|
|
.It Dv IPCTL_SOURCEROUTE
|
|
|
|
.Pq ip.sourceroute
|
|
|
|
Boolean: enable/disable forwarding of source-routed IP packets (default false).
|
2004-07-02 15:47:47 +00:00
|
|
|
.It Va ip.process_options
|
|
|
|
Integer: control IP options processing.
|
|
|
|
By setting this variable to 0, all IP options in the incoming packets
|
|
|
|
will be ignored, and the packets will be passed unmodified.
|
|
|
|
By setting to 1, IP options in the incoming packets will be processed
|
|
|
|
accordingly.
|
|
|
|
By setting to 2, an
|
|
|
|
.Tn ICMP
|
|
|
|
.Dq "prohibited by filter"
|
2006-12-14 16:40:57 +00:00
|
|
|
message will be sent back in response to incoming packets with IP options.
|
2004-07-02 15:47:47 +00:00
|
|
|
Default is 1.
|
|
|
|
This
|
|
|
|
.Xr sysctl 8
|
|
|
|
variable affects packets destined for a local host as well as packets
|
|
|
|
forwarded to some other host.
|
2021-11-12 16:56:46 +00:00
|
|
|
.It Va ip.rfc1122_strong_es
|
|
|
|
Boolean: in non-forwarding mode
|
|
|
|
.Pq ip.forwarding is disabled
|
|
|
|
partially implement the Strong End System model per RFC1122.
|
|
|
|
If a packet with destination address that is local arrives on a different
|
|
|
|
interface than the interface the address belongs to, the packet would be
|
|
|
|
silently dropped.
|
|
|
|
Enabling this option may break certain setups, e.g. having an alias address(es)
|
|
|
|
on loopback that are expected to be reachable by outside traffic.
|
|
|
|
Enabling some other network features, e.g.
|
|
|
|
.Xr carp 4
|
|
|
|
or destination address rewriting
|
|
|
|
.Xr pfil 4
|
|
|
|
filters may override and bypass this check.
|
|
|
|
Disabled by default.
|
2021-11-12 17:00:33 +00:00
|
|
|
.It Va ip.source_address_validation
|
|
|
|
Boolean: perform source address validation for packets destined for the local
|
|
|
|
host.
|
|
|
|
Consider this as following Section 3.2 of RFC3704/BCP84, where we treat local
|
|
|
|
host as our own infrastructure.
|
|
|
|
This has no effect on packets to be forwarded, so don't consider it as
|
|
|
|
anti-spoof feature for a router.
|
|
|
|
Enabled by default.
|
2015-04-01 22:26:39 +00:00
|
|
|
.It Va ip.rfc6864
|
|
|
|
Boolean: control IP IDs generation behaviour.
|
|
|
|
True value enables RFC6864 support, which specifies that IP ID field of
|
|
|
|
.Em atomic
|
|
|
|
datagrams can be set to any value.
|
|
|
|
The
|
|
|
|
.Fx implementation sets it to zero.
|
|
|
|
Enabled by default.
|
2004-08-15 17:32:31 +00:00
|
|
|
.It Va ip.random_id
|
|
|
|
Boolean: control IP IDs generation behaviour.
|
|
|
|
Setting this
|
|
|
|
.Xr sysctl 8
|
2015-04-01 22:26:39 +00:00
|
|
|
to 1 causes the ID field in
|
|
|
|
.Em non-atomic
|
|
|
|
IP datagrams (or all IP datagrams, if
|
|
|
|
.Va ip.rfc6864
|
|
|
|
is disabled) to be randomized instead of incremented by 1 with each packet
|
|
|
|
generated.
|
2015-04-07 19:39:23 +00:00
|
|
|
This closes a minor information leak which allows remote observers to
|
|
|
|
determine the rate of packet generation on the machine by watching the
|
|
|
|
counter.
|
2015-04-03 14:00:08 +00:00
|
|
|
At the same time, on high-speed links, it can decrease the ID reuse
|
2004-08-16 06:30:58 +00:00
|
|
|
cycle greatly.
|
2004-08-15 17:32:31 +00:00
|
|
|
Default is 0 (sequential IP IDs).
|
|
|
|
IPv6 flow IDs and fragment IDs are always random.
|
2018-08-14 17:36:21 +00:00
|
|
|
.It Va ip.maxfrags
|
|
|
|
Integer: maximum number of fragments the host will accept and simultaneously
|
|
|
|
hold across all reassembly queues in all VNETs.
|
|
|
|
If set to 0, reassembly is disabled.
|
|
|
|
If set to -1, this limit is not applied.
|
|
|
|
This limit is recalculated when the number of mbuf clusters is changed.
|
|
|
|
This is a global limit.
|
2005-04-09 08:44:57 +00:00
|
|
|
.It Va ip.maxfragpackets
|
2018-08-14 17:36:21 +00:00
|
|
|
Integer: maximum number of fragmented packets the host will accept and
|
|
|
|
simultaneously hold in the reassembly queue for a particular VNET.
|
|
|
|
0 means that the host will not accept any fragmented packets for that VNET.
|
|
|
|
\-1 means that the host will not apply this limit for that VNET.
|
|
|
|
This limit is recalculated when the number of mbuf clusters is changed.
|
|
|
|
This is a per-VNET limit.
|
|
|
|
.It Va ip.maxfragbucketsize
|
|
|
|
Integer: maximum number of reassembly queues per bucket.
|
|
|
|
Fragmented packets are hashed to buckets.
|
|
|
|
Each bucket has a list of reassembly queues.
|
|
|
|
The system must compare the incoming packets to the existing reassembly queues
|
|
|
|
in the bucket to find a matching reassembly queue.
|
|
|
|
To preserve system resources, the system limits the number of reassembly
|
|
|
|
queues allowed in each bucket.
|
|
|
|
This limit is recalculated when the number of mbuf clusters is changed or
|
|
|
|
when the value of
|
|
|
|
.Va ip.maxfragpackets
|
|
|
|
changes.
|
|
|
|
This is a per-VNET limit.
|
2005-04-09 08:44:57 +00:00
|
|
|
.It Va ip.maxfragsperpacket
|
|
|
|
Integer: maximum number of fragments the host will accept and hold
|
2018-08-14 17:36:21 +00:00
|
|
|
in the reassembly queue for a packet.
|
|
|
|
0 means that the host will not accept any fragmented packets for the VNET.
|
|
|
|
This is a per-VNET limit.
|
1995-02-15 03:30:54 +00:00
|
|
|
.El
|
1994-05-30 19:09:18 +00:00
|
|
|
.Sh SEE ALSO
|
|
|
|
.Xr ioctl 2 ,
|
|
|
|
.Xr socket 2 ,
|
2012-01-26 10:42:25 +00:00
|
|
|
.Xr getifaddrs 3 ,
|
1995-02-15 03:30:54 +00:00
|
|
|
.Xr sysctl 3 ,
|
1996-12-26 16:16:37 +00:00
|
|
|
.Xr icmp 4 ,
|
1994-05-30 19:09:18 +00:00
|
|
|
.Xr intro 4 ,
|
1996-12-26 16:16:37 +00:00
|
|
|
.Xr ip 4 ,
|
1999-03-20 10:25:40 +00:00
|
|
|
.Xr ipfirewall 4 ,
|
2004-10-23 18:45:53 +00:00
|
|
|
.Xr route 4 ,
|
1994-05-30 19:09:18 +00:00
|
|
|
.Xr tcp 4 ,
|
2005-01-12 10:14:43 +00:00
|
|
|
.Xr udp 4 ,
|
2004-10-23 18:45:53 +00:00
|
|
|
.Xr pfil 9
|
1994-05-30 19:09:18 +00:00
|
|
|
.Rs
|
|
|
|
.%T "An Introductory 4.3 BSD Interprocess Communication Tutorial"
|
|
|
|
.%B PS1
|
|
|
|
.%N 7
|
|
|
|
.Re
|
|
|
|
.Rs
|
|
|
|
.%T "An Advanced 4.3 BSD Interprocess Communication Tutorial"
|
|
|
|
.%B PS1
|
|
|
|
.%N 8
|
|
|
|
.Re
|
|
|
|
.Sh HISTORY
|
|
|
|
The
|
|
|
|
.Nm
|
|
|
|
protocol interface appeared in
|
|
|
|
.Bx 4.2 .
|
1995-02-15 03:30:54 +00:00
|
|
|
The
|
|
|
|
.Dq protocol cloning
|
|
|
|
code appeared in
|
1996-08-22 23:51:58 +00:00
|
|
|
.Fx 2.1 .
|
2010-05-13 12:07:55 +00:00
|
|
|
.Sh CAVEATS
|
|
|
|
The Internet protocol support is subject to change as
|
|
|
|
the Internet protocols develop.
|
|
|
|
Users should not depend
|
|
|
|
on details of the current implementation, but rather
|
|
|
|
the services exported.
|