mirror of https://github.com/mkerrisk/man-pages
ipv6.7: minor: wording and grammar fixes
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
f08b799c9c
commit
acae032272
20
man7/ipv6.7
20
man7/ipv6.7
|
@ -26,39 +26,39 @@ is based on the BSD sockets interface; see
|
||||||
.BR socket (7).
|
.BR socket (7).
|
||||||
.PP
|
.PP
|
||||||
The IPv6 API aims to be mostly compatible with the
|
The IPv6 API aims to be mostly compatible with the
|
||||||
.BR ip (7)
|
IPv4 API (see
|
||||||
v4 API.
|
.BR ip (7)).
|
||||||
Only differences are described in this man page.
|
Only differences are described in this man page.
|
||||||
.PP
|
.PP
|
||||||
To bind an
|
To bind an
|
||||||
.B AF_INET6
|
.B AF_INET6
|
||||||
socket to any process the local address should be copied from the
|
socket to any process, the local address should be copied from the
|
||||||
.I in6addr_any
|
.I in6addr_any
|
||||||
variable which has
|
variable which has
|
||||||
.I in6_addr
|
.I in6_addr
|
||||||
type.
|
type.
|
||||||
In static initializations
|
In static initializations,
|
||||||
.B IN6ADDR_ANY_INIT
|
.B IN6ADDR_ANY_INIT
|
||||||
may also be used, which expands to a constant expression.
|
may also be used, which expands to a constant expression.
|
||||||
Both of them are in network order.
|
Both of them are in network byte order.
|
||||||
.PP
|
.PP
|
||||||
The IPv6 loopback address (::1) is available in the global
|
The IPv6 loopback address (::1) is available in the global
|
||||||
.I in6addr_loopback
|
.I in6addr_loopback
|
||||||
variable.
|
variable.
|
||||||
For initializations
|
For initializations,
|
||||||
.B IN6ADDR_LOOPBACK_INIT
|
.B IN6ADDR_LOOPBACK_INIT
|
||||||
should be used.
|
should be used.
|
||||||
.PP
|
.PP
|
||||||
IPv4 connections can be handled with the v6 API by using the
|
IPv4 connections can be handled with the v6 API by using the
|
||||||
v4-mapped-on-v6 address type;
|
v4-mapped-on-v6 address type;
|
||||||
thus a program only needs only to support this API type to
|
thus a program only needs to support this API type to
|
||||||
support both protocols.
|
support both protocols.
|
||||||
This is handled transparently by the address
|
This is handled transparently by the address
|
||||||
handling functions in libc.
|
handling functions in the C library.
|
||||||
.PP
|
.PP
|
||||||
IPv4 and IPv6 share the local port space.
|
IPv4 and IPv6 share the local port space.
|
||||||
When you get an IPv4 connection
|
When you get an IPv4 connection
|
||||||
or packet to a IPv6 socket its source address will be mapped
|
or packet to a IPv6 socket, its source address will be mapped
|
||||||
to v6 and it will be mapped to v6.
|
to v6 and it will be mapped to v6.
|
||||||
.SS "Address Format"
|
.SS "Address Format"
|
||||||
.in +4n
|
.in +4n
|
||||||
|
@ -90,7 +90,7 @@ is the IPv6 flow identifier;
|
||||||
.I sin6_addr
|
.I sin6_addr
|
||||||
is the 128-bit IPv6 address.
|
is the 128-bit IPv6 address.
|
||||||
.I sin6_scope_id
|
.I sin6_scope_id
|
||||||
is an ID of depending of on the scope of the address.
|
is an ID depending on the scope of the address.
|
||||||
It is new in Linux 2.4.
|
It is new in Linux 2.4.
|
||||||
Linux only supports it for link scope addresses, in that case
|
Linux only supports it for link scope addresses, in that case
|
||||||
.I sin6_scope_id
|
.I sin6_scope_id
|
||||||
|
|
Loading…
Reference in New Issue