1 .\" Copyright (c) 1983, 1990, 1991, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
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.
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
32 .\" From: @(#)inet.3 8.1 (Berkeley) 6/4/93
33 .\" $FreeBSD: src/lib/libc/net/inet.3,v 1.25 2002/09/06 11:23:49 tjr Exp $
48 .Nd Internet address manipulation routines
57 .Fn inet_aton "const char *cp" "struct in_addr *pin"
59 .Fn inet_addr "const char *cp"
61 .Fn inet_network "const char *cp"
63 .Fn inet_ntoa "struct in_addr in"
67 .Fa "const void * restrict src"
68 .Fa "char * restrict dst"
72 .Fn inet_pton "int af" "const char * restrict src" "void * restrict dst"
74 .Fn inet_makeaddr "in_addr_t net" "in_addr_t lna"
76 .Fn inet_lnaof "struct in_addr in"
78 .Fn inet_netof "struct in_addr in"
85 interpret character strings representing
86 numbers expressed in the Internet standard
92 function converts a presentation format address (that is, printable form
93 as held in a character string) to network format (usually a
95 or some other internal binary representation, in network byte order).
96 It returns 1 if the address was valid for the specified address family, or
97 0 if the address wasn't parseable in the specified address family, or -1
98 if some system error occurred (in which case
101 This function is presently valid for
108 routine interprets the specified character string as an Internet address,
109 placing the address into the structure provided.
110 It returns 1 if the string was successfully interpreted,
111 or 0 if the string is invalid.
116 functions return numbers suitable for use
117 as Internet addresses and Internet network
118 numbers, respectively.
122 converts an address from network format (usually a
124 or some other binary form, in network byte order) to presentation format
125 (suitable for external display purposes).
126 It returns NULL if a system error occurs (in which case,
128 will have been set), or it returns a pointer to the destination string.
129 This function is presently valid for
136 takes an Internet address and returns an
138 string representing the address in
140 notation. The routine
142 takes an Internet network number and a local
143 network address and constructs an Internet address
144 from it. The routines
148 break apart Internet host addresses, returning
149 the network number and local network address part,
152 All Internet addresses are returned in network
153 order (bytes ordered from left to right).
154 All network numbers and local address parts are
155 returned as machine byte order integer values.
156 .Sh INTERNET ADDRESSES
157 Values specified using the
160 of the following forms:
161 .Bd -literal -offset indent
168 When four parts are specified, each is interpreted
169 as a byte of data and assigned, from left to right,
170 to the four bytes of an Internet address. Note
171 that when an Internet address is viewed as a 32-bit
172 integer quantity on the
174 the bytes referred to
180 ordered from right to left.
182 When a three part address is specified, the last
183 part is interpreted as a 16-bit quantity and placed
184 in the right-most two bytes of the network address.
185 This makes the three part address format convenient
186 for specifying Class B network addresses as
187 .Dq Li 128.net.host .
189 When a two part address is supplied, the last part
190 is interpreted as a 24-bit quantity and placed in
191 the right most three bytes of the network address.
192 This makes the two part address format convenient
193 for specifying Class A network addresses as
196 When only one part is given, the value is stored
197 directly in the network address without any byte
200 All numbers supplied as
205 may be decimal, octal, or hexadecimal, as specified
206 in the C language (i.e., a leading 0x or 0X implies
207 hexadecimal; otherwise, a leading 0 implies octal;
208 otherwise, the number is interpreted as decimal).
214 functions are semi-deprecated in favor of the
216 family. However, since those functions are not yet widely implemented,
217 portable programs cannot rely on their presence and will continue
220 functions for some time.
228 for malformed requests.
232 .Xr gethostbyname 3 ,
241 .%T "IP Version 6 Addressing Architecture"
252 does not accept 1-, 2-, or 3-part dotted addresses; all four parts
253 must be specified and are interpreted only as decimal values.
254 This is a narrower input set than that accepted by
258 functions appeared in
263 (0xffffffff) is a valid broadcast address, but
265 cannot return that value without indicating failure.
268 function does not share this problem.
269 The problem of host byte ordering versus network byte ordering is
271 The string returned by
273 resides in a static memory area.
275 Inet_addr should return a