summaryrefslogtreecommitdiff
path: root/src/lib/libc/net/inet.3
diff options
context:
space:
mode:
authoraaron <>2000-04-18 03:01:33 +0000
committeraaron <>2000-04-18 03:01:33 +0000
commit6e79b911ce0057b5b91d0f9cedd766e0163fb043 (patch)
tree9478c878ca3f3846100f116eeb1bed16f321f335 /src/lib/libc/net/inet.3
parent59ca3f5f8991ab72904434fb49ef0999d64ae2e8 (diff)
downloadopenbsd-6e79b911ce0057b5b91d0f9cedd766e0163fb043.tar.gz
openbsd-6e79b911ce0057b5b91d0f9cedd766e0163fb043.tar.bz2
openbsd-6e79b911ce0057b5b91d0f9cedd766e0163fb043.zip
Repairs, mostly removing hard sentence breaks.
Diffstat (limited to 'src/lib/libc/net/inet.3')
-rw-r--r--src/lib/libc/net/inet.345
1 files changed, 28 insertions, 17 deletions
diff --git a/src/lib/libc/net/inet.3 b/src/lib/libc/net/inet.3
index 1e38bdc056..eb95f6c364 100644
--- a/src/lib/libc/net/inet.3
+++ b/src/lib/libc/net/inet.3
@@ -1,4 +1,4 @@
1.\" $OpenBSD: inet.3,v 1.8 1999/07/05 04:40:59 aaron Exp $ 1.\" $OpenBSD: inet.3,v 1.9 2000/04/18 03:01:32 aaron Exp $
2.\" $NetBSD: inet.3,v 1.7 1997/06/18 02:25:24 lukem Exp $ 2.\" $NetBSD: inet.3,v 1.7 1997/06/18 02:25:24 lukem Exp $
3.\" 3.\"
4.\" Copyright (c) 1983, 1990, 1991, 1993 4.\" Copyright (c) 1983, 1990, 1991, 1993
@@ -85,12 +85,13 @@ The
85function converts a presentation format address (that is, printable form 85function converts a presentation format address (that is, printable form
86as held in a character string) to network format (usually a 86as held in a character string) to network format (usually a
87.Li struct in_addr 87.Li struct in_addr
88or some other internal binary representation, in network byte order). It 88or some other internal binary representation, in network byte order).
89returns 1 if the address was valid for the specified address family, or 89It returns 1 if the address was valid for the specified address family, or
900 if the address wasn't parseable in the specified address family, or \-1 900 if the address wasn't parseable in the specified address family, or \-1
91if some system error occurred (in which case 91if some system error occurred (in which case
92.Va errno 92.Va errno
93will have been set). This function is presently valid for 93will have been set).
94This function is presently valid for
94.Dv AF_INET 95.Dv AF_INET
95and 96and
96.Dv AF_INET6 . 97.Dv AF_INET6 .
@@ -113,7 +114,8 @@ The function
113converts an address from network format (usually a 114converts an address from network format (usually a
114.Li struct in_addr 115.Li struct in_addr
115or some other binary form, in network byte order) to presentation format 116or some other binary form, in network byte order) to presentation format
116(suitable for external display purposes). It returns 117(suitable for external display purposes).
118It returns
117.Dv NULL 119.Dv NULL
118if a system 120if a system
119error occurs (in which case, 121error occurs (in which case,
@@ -125,11 +127,13 @@ takes an Internet address and returns an
125.Tn ASCII 127.Tn ASCII
126string representing the address in 128string representing the address in
127.Ql \&. 129.Ql \&.
128notation. The routine 130notation.
131The routine
129.Fn inet_makeaddr 132.Fn inet_makeaddr
130takes an Internet network number and a local 133takes an Internet network number and a local
131network address and constructs an Internet address 134network address and constructs an Internet address
132from it. The routines 135from it.
136The routines
133.Fn inet_netof 137.Fn inet_netof
134and 138and
135.Fn inet_lnaof 139.Fn inet_lnaof
@@ -155,8 +159,8 @@ a
155.Pp 159.Pp
156When four parts are specified, each is interpreted 160When four parts are specified, each is interpreted
157as a byte of data and assigned, from left to right, 161as a byte of data and assigned, from left to right,
158to the four bytes of an Internet address. Note 162to the four bytes of an Internet address.
159that when an Internet address is viewed as a 32-bit 163Note that when an Internet address is viewed as a 32-bit
160integer quantity on a system that uses little-endian 164integer quantity on a system that uses little-endian
161byte order (such as the 165byte order (such as the
162.Tn Intel 386, 486 166.Tn Intel 386, 486
@@ -214,16 +218,20 @@ every field (except for the case described in 2.).
214.It 218.It
215Due to the method of allocating certain styles of IPv6 219Due to the method of allocating certain styles of IPv6
216addresses, it will be common for addresses to contain long 220addresses, it will be common for addresses to contain long
217strings of zero bits. In order to make writing addresses 221strings of zero bits.
222In order to make writing addresses
218.Pp 223.Pp
219containing zero bits easier a special syntax is available to 224containing zero bits easier a special syntax is available to
220compress the zeros. The use of 225compress the zeros.
226The use of
221.Dq \&:\&: 227.Dq \&:\&:
222indicates multiple groups 228indicates multiple groups
223of 16 bits of zeros. The 229of 16 bits of zeros.
230The
224.Dq \&:\&: 231.Dq \&:\&:
225can only appear once in an 232can only appear once in an
226address. The 233address.
234The
227.Dq \&:\&: 235.Dq \&:\&:
228can also be used to compress the leading and/or trailing zeros in an address. 236can also be used to compress the leading and/or trailing zeros in an address.
229.Pp 237.Pp
@@ -248,7 +256,8 @@ dealing with a mixed environment of IPv4 and IPv6 nodes is
248x:x:x:x:x:x:d.d.d.d, where the 'x's are the hexadecimal values 256x:x:x:x:x:x:d.d.d.d, where the 'x's are the hexadecimal values
249of the six high-order 16-bit pieces of the address, and the 'd's 257of the six high-order 16-bit pieces of the address, and the 'd's
250are the decimal values of the four low-order 8-bit pieces of the 258are the decimal values of the four low-order 8-bit pieces of the
251address (standard IPv4 representation). Examples: 259address (standard IPv4 representation).
260Examples:
252.Bd -literal -offset indent 261.Bd -literal -offset indent
2530:0:0:0:0:0:13.1.68.3 2620:0:0:0:0:0:13.1.68.3
2540:0:0:0:0:FFFF:129.144.52.38 2630:0:0:0:0:FFFF:129.144.52.38
@@ -281,10 +290,12 @@ The
281and 290and
282.Nm inet_pton 291.Nm inet_pton
283functions conforms to the IETF IPng BSD API and address formatting 292functions conforms to the IETF IPng BSD API and address formatting
284specifications. Note that 293specifications.
294Note that
285.Nm inet_pton 295.Nm inet_pton
286does not accept 1-, 2-, or 3-part dotted addresses; all four parts 296does not accept 1-, 2-, or 3-part dotted addresses; all four parts
287must be specified. This is a narrower input set than that accepted by 297must be specified.
298This is a narrower input set than that accepted by
288.Nm inet_aton . 299.Nm inet_aton .
289.Sh HISTORY 300.Sh HISTORY
290The 301The