mirror of https://github.com/mkerrisk/man-pages
ffix
This commit is contained in:
parent
1da4ccb032
commit
051815fe3d
|
@ -60,7 +60,7 @@ IPv4 and IPv6 share the local port space.
|
|||
When you get an IPv4 connection
|
||||
or packet to a IPv6 socket its source address will be mapped
|
||||
to v6 and it'll be mapped to v6.
|
||||
.SH "ADDRESS FORMAT"
|
||||
.SS "Address Format"
|
||||
.sp
|
||||
.RS
|
||||
.nf
|
||||
|
@ -110,7 +110,7 @@ Special addresses are ::1 for loopback and ::FFFF:<IPv4 address>
|
|||
for IPv4-mapped-on-IPv6.
|
||||
.PP
|
||||
The port space of IPv6 is shared with IPv4.
|
||||
.SH "SOCKET OPTIONS"
|
||||
.SS "Socket Options"
|
||||
IPv6 supports some protocol specific socket options that can be set with
|
||||
.BR setsockopt (2)
|
||||
and read with
|
||||
|
@ -268,7 +268,7 @@ It is transparently passed/read by the kernel
|
|||
when the passed address length contains it.
|
||||
Some programs that pass a longer address buffer and then
|
||||
check the outgoing address length may break.
|
||||
.SH "PORTING NOTES"
|
||||
.SH "NOTES"
|
||||
The
|
||||
.I sockaddr_in6
|
||||
structure is bigger than the generic
|
||||
|
|
|
@ -35,7 +35,7 @@ It is based on netlink messages, see
|
|||
.BR netlink (7)
|
||||
for more information.
|
||||
.\" FIXME all these macros could be moved to rtnetlink(3)
|
||||
.SH "ROUTING ATTRIBUTES"
|
||||
.SS "Routing Attributes"
|
||||
Some rtnetlink messages have optional attributes after the initial header:
|
||||
|
||||
.nf
|
||||
|
@ -49,7 +49,7 @@ struct rtattr {
|
|||
These attributes should be only manipulated using the RTA_* macros
|
||||
or libnetlink, see
|
||||
.BR rtnetlink (3).
|
||||
.SH MESSAGES
|
||||
.SS Messages
|
||||
Rtnetlink consists of these message types
|
||||
(in addition to standard netlink messages):
|
||||
.TP
|
||||
|
|
Loading…
Reference in New Issue