xref: /freebsd/share/man/man4/ip.4 (revision 4b2eaea43fec8e8792be611dea204071a10b655a)
1.\" Copyright (c) 1983, 1991, 1993
2.\"	The Regents of the University of California.  All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\"    notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\"    notice, this list of conditions and the following disclaimer in the
11.\"    documentation and/or other materials provided with the distribution.
12.\" 3. All advertising materials mentioning features or use of this software
13.\"    must display the following acknowledgement:
14.\"	This product includes software developed by the University of
15.\"	California, Berkeley and its contributors.
16.\" 4. Neither the name of the University nor the names of its contributors
17.\"    may be used to endorse or promote products derived from this software
18.\"    without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\"     @(#)ip.4	8.2 (Berkeley) 11/30/93
33.\" $FreeBSD$
34.\"
35.Dd March 3, 2001
36.Dt IP 4
37.Os
38.Sh NAME
39.Nm ip
40.Nd Internet Protocol
41.Sh SYNOPSIS
42.In sys/types.h
43.In sys/socket.h
44.In netinet/in.h
45.Ft int
46.Fn socket AF_INET SOCK_RAW proto
47.Sh DESCRIPTION
48.Tn IP
49is the transport layer protocol used
50by the Internet protocol family.
51Options may be set at the
52.Tn IP
53level
54when using higher-level protocols that are based on
55.Tn IP
56(such as
57.Tn TCP
58and
59.Tn UDP ) .
60It may also be accessed
61through a
62.Dq raw socket
63when developing new protocols, or
64special-purpose applications.
65.Pp
66There are several
67.Tn IP-level
68.Xr setsockopt 2
69and
70.Xr getsockopt 2
71options.
72.Dv IP_OPTIONS
73may be used to provide
74.Tn IP
75options to be transmitted in the
76.Tn IP
77header of each outgoing packet
78or to examine the header options on incoming packets.
79.Tn IP
80options may be used with any socket type in the Internet family.
81The format of
82.Tn IP
83options to be sent is that specified by the
84.Tn IP
85protocol specification (RFC-791), with one exception:
86the list of addresses for Source Route options must include the first-hop
87gateway at the beginning of the list of gateways.
88The first-hop gateway address will be extracted from the option list
89and the size adjusted accordingly before use.
90To disable previously specified options,
91use a zero-length buffer:
92.Bd -literal
93setsockopt(s, IPPROTO_IP, IP_OPTIONS, NULL, 0);
94.Ed
95.Pp
96.Dv IP_TOS
97and
98.Dv IP_TTL
99may be used to set the type-of-service and time-to-live
100fields in the
101.Tn IP
102header for
103.Dv SOCK_STREAM , SOCK_DGRAM ,
104and certain types of
105.Dv SOCK_RAW
106sockets.
107For example,
108.Bd -literal
109int tos = IPTOS_LOWDELAY;       /* see <netinet/ip.h> */
110setsockopt(s, IPPROTO_IP, IP_TOS, &tos, sizeof(tos));
111
112int ttl = 60;                   /* max = 255 */
113setsockopt(s, IPPROTO_IP, IP_TTL, &ttl, sizeof(ttl));
114.Ed
115.Pp
116If the
117.Dv IP_RECVDSTADDR
118option is enabled on a
119.Dv SOCK_DGRAM
120socket,
121the
122.Xr recvmsg 2
123call will return the destination
124.Tn IP
125address for a
126.Tn UDP
127datagram.
128The msg_control field in the msghdr structure points to a buffer
129that contains a cmsghdr structure followed by the
130.Tn IP
131address.
132The cmsghdr fields have the following values:
133.Bd -literal
134cmsg_len = sizeof(struct in_addr)
135cmsg_level = IPPROTO_IP
136cmsg_type = IP_RECVDSTADDR
137.Ed
138.Pp
139The source address to be used for outgoing
140.Tn UDP
141datagrams on a socket that is not bound to a specific
142.Tn IP
143address can be specified as ancillary data with a type code of
144.Dv IP_SENDSRCADDR .
145The msg_control field in the msghdr structure should point to a buffer
146that contains a cmsghdr structure followed by the
147.Tn IP
148address.
149The cmsghdr fields should have the following values:
150.Bd -literal
151cmsg_len = sizeof(struct in_addr)
152cmsg_level = IPPROTO_IP
153cmsg_type = IP_SENDSRCADDR
154.Ed
155.Pp
156For convenience,
157.Dv IP_SENDSRCADDR
158is defined to have the same value as
159.Dv IP_RECVDSTADDR ,
160so the
161.Dv IP_RECVDSTADDR
162control message from
163.Xr recvmsg 2
164can be used directly as a control message for
165.Xr sendmsg 2 .
166.Pp
167.Dv IP_PORTRANGE
168may be used to set the port range used for selecting a local port number
169on a socket with an unspecified (zero) port number.
170It has the following
171possible values:
172.Bl -tag -width IP_PORTRANGE_DEFAULT
173.It Dv IP_PORTRANGE_DEFAULT
174use the default range of values, normally
175.Dv IPPORT_HIFIRSTAUTO
176through
177.Dv IPPORT_HILASTAUTO .
178This is adjustable through the sysctl setting:
179.Sy net.inet.ip.portrange.first
180and
181.Sy net.inet.ip.portrange.last .
182.It Dv IP_PORTRANGE_HIGH
183use a high range of values, normally
184.Dv IPPORT_HIFIRSTAUTO
185and
186.Dv IPPORT_HILASTAUTO .
187This is adjustable through the sysctl setting:
188.Sy net.inet.ip.portrange.hifirst
189and
190.Sy net.inet.ip.portrange.hilast .
191.It Dv IP_PORTRANGE_LOW
192use a low range of ports, which are normally restricted to
193privileged processes on
194.Ux
195systems.  The range is normally from
196.Dv IPPORT_RESERVED - 1
197down to
198.Li IPPORT_RESERVEDSTART
199in descending order.
200This is adjustable through the sysctl setting:
201.Sy net.inet.ip.portrange.lowfirst
202and
203.Sy net.inet.ip.portrange.lowlast .
204.El
205.Ss "Multicast Options"
206.Pp
207.Tn IP
208multicasting is supported only on
209.Dv AF_INET
210sockets of type
211.Dv SOCK_DGRAM
212and
213.Dv SOCK_RAW ,
214and only on networks where the interface
215driver supports multicasting.
216.Pp
217The
218.Dv IP_MULTICAST_TTL
219option changes the time-to-live (TTL)
220for outgoing multicast datagrams
221in order to control the scope of the multicasts:
222.Bd -literal
223u_char ttl;	/* range: 0 to 255, default = 1 */
224setsockopt(s, IPPROTO_IP, IP_MULTICAST_TTL, &ttl, sizeof(ttl));
225.Ed
226.Pp
227Datagrams with a TTL of 1 are not forwarded beyond the local network.
228Multicast datagrams with a TTL of 0 will not be transmitted on any network,
229but may be delivered locally if the sending host belongs to the destination
230group and if multicast loopback has not been disabled on the sending socket
231(see below).  Multicast datagrams with TTL greater than 1 may be forwarded
232to other networks if a multicast router is attached to the local network.
233.Pp
234For hosts with multiple interfaces, each multicast transmission is
235sent from the primary network interface.
236The
237.Dv IP_MULTICAST_IF
238option overrides the default for
239subsequent transmissions from a given socket:
240.Bd -literal
241struct in_addr addr;
242setsockopt(s, IPPROTO_IP, IP_MULTICAST_IF, &addr, sizeof(addr));
243.Ed
244.Pp
245where "addr" is the local
246.Tn IP
247address of the desired interface or
248.Dv INADDR_ANY
249to specify the default interface.
250An interface's local IP address and multicast capability can
251be obtained via the
252.Dv SIOCGIFCONF
253and
254.Dv SIOCGIFFLAGS
255ioctls.
256Normal applications should not need to use this option.
257.Pp
258If a multicast datagram is sent to a group to which the sending host itself
259belongs (on the outgoing interface), a copy of the datagram is, by default,
260looped back by the IP layer for local delivery.
261The
262.Dv IP_MULTICAST_LOOP
263option gives the sender explicit control
264over whether or not subsequent datagrams are looped back:
265.Bd -literal
266u_char loop;	/* 0 = disable, 1 = enable (default) */
267setsockopt(s, IPPROTO_IP, IP_MULTICAST_LOOP, &loop, sizeof(loop));
268.Ed
269.Pp
270This option
271improves performance for applications that may have no more than one
272instance on a single host (such as a router daemon), by eliminating
273the overhead of receiving their own transmissions.  It should generally not
274be used by applications for which there may be more than one instance on a
275single host (such as a conferencing program) or for which the sender does
276not belong to the destination group (such as a time querying program).
277.Pp
278A multicast datagram sent with an initial TTL greater than 1 may be delivered
279to the sending host on a different interface from that on which it was sent,
280if the host belongs to the destination group on that other interface.  The
281loopback control option has no effect on such delivery.
282.Pp
283A host must become a member of a multicast group before it can receive
284datagrams sent to the group.  To join a multicast group, use the
285.Dv IP_ADD_MEMBERSHIP
286option:
287.Bd -literal
288struct ip_mreq mreq;
289setsockopt(s, IPPROTO_IP, IP_ADD_MEMBERSHIP, &mreq, sizeof(mreq));
290.Ed
291.Pp
292where
293.Fa mreq
294is the following structure:
295.Bd -literal
296struct ip_mreq {
297    struct in_addr imr_multiaddr; /* IP multicast address of group */
298    struct in_addr imr_interface; /* local IP address of interface */
299}
300.Ed
301.Pp
302.Dv imr_interface
303should
304be
305.Dv INADDR_ANY
306to choose the default multicast interface,
307or the
308.Tn IP
309address of a particular multicast-capable interface if
310the host is multihomed.
311Membership is associated with a single interface;
312programs running on multihomed hosts may need to
313join the same group on more than one interface.
314Up to
315.Dv IP_MAX_MEMBERSHIPS
316(currently 20) memberships may be added on a
317single socket.
318.Pp
319To drop a membership, use:
320.Bd -literal
321struct ip_mreq mreq;
322setsockopt(s, IPPROTO_IP, IP_DROP_MEMBERSHIP, &mreq, sizeof(mreq));
323.Ed
324.Pp
325where
326.Fa mreq
327contains the same values as used to add the membership.
328Memberships are dropped when the socket is closed or the process exits.
329.\"-----------------------
330.Ss "Raw IP Sockets"
331.Pp
332Raw
333.Tn IP
334sockets are connectionless,
335and are normally used with the
336.Xr sendto 2
337and
338.Xr recvfrom 2
339calls, though the
340.Xr connect 2
341call may also be used to fix the destination for future
342packets (in which case the
343.Xr read 2
344or
345.Xr recv 2
346and
347.Xr write 2
348or
349.Xr send 2
350system calls may be used).
351.Pp
352If
353.Fa proto
354is 0, the default protocol
355.Dv IPPROTO_RAW
356is used for outgoing
357packets, and only incoming packets destined for that protocol
358are received.
359If
360.Fa proto
361is non-zero, that protocol number will be used on outgoing packets
362and to filter incoming packets.
363.Pp
364Outgoing packets automatically have an
365.Tn IP
366header prepended to
367them (based on the destination address and the protocol
368number the socket is created with),
369unless the
370.Dv IP_HDRINCL
371option has been set.
372Incoming packets are received with
373.Tn IP
374header and options intact.
375.Pp
376.Dv IP_HDRINCL
377indicates the complete IP header is included with the data
378and may be used only with the
379.Dv SOCK_RAW
380type.
381.Bd -literal
382#include <netinet/in_systm.h>
383#include <netinet/ip.h>
384
385int hincl = 1;                  /* 1 = on, 0 = off */
386setsockopt(s, IPPROTO_IP, IP_HDRINCL, &hincl, sizeof(hincl));
387.Ed
388.Pp
389Unlike previous
390.Bx
391releases, the program must set all
392the fields of the IP header, including the following:
393.Bd -literal
394ip->ip_v = IPVERSION;
395ip->ip_hl = hlen >> 2;
396ip->ip_id = 0;  /* 0 means kernel set appropriate value */
397ip->ip_off = offset;
398.Ed
399.Pp
400If the header source address is set to
401.Dv INADDR_ANY ,
402the kernel will choose an appropriate address.
403.Sh ERRORS
404A socket operation may fail with one of the following errors returned:
405.Bl -tag -width Er
406.It Bq Er EISCONN
407when trying to establish a connection on a socket which
408already has one, or when trying to send a datagram with the destination
409address specified and the socket is already connected;
410.It Bq Er ENOTCONN
411when trying to send a datagram, but
412no destination address is specified, and the socket hasn't been
413connected;
414.It Bq Er ENOBUFS
415when the system runs out of memory for
416an internal data structure;
417.It Bq Er EADDRNOTAVAIL
418when an attempt is made to create a
419socket with a network address for which no network interface
420exists.
421.It Bq Er EACCES
422when an attempt is made to create
423a raw IP socket by a non-privileged process.
424.El
425.Pp
426The following errors specific to
427.Tn IP
428may occur when setting or getting
429.Tn IP
430options:
431.Bl -tag -width EADDRNOTAVAILxx
432.It Bq Er EINVAL
433An unknown socket option name was given.
434.It Bq Er EINVAL
435The IP option field was improperly formed;
436an option field was shorter than the minimum value
437or longer than the option buffer provided.
438.El
439.Sh SEE ALSO
440.Xr getsockopt 2 ,
441.Xr recv 2 ,
442.Xr send 2 ,
443.Xr icmp 4 ,
444.Xr inet 4 ,
445.Xr intro 4
446.Sh HISTORY
447The
448.Nm
449protocol appeared in
450.Bx 4.2 .
451