It is used within the kernel to communicate between
various subsystems, though this usage is not documented here, and for
communication with user-space programs.
-Network routes, ip addresses, link parameters, neighbor setups, queueing
+Network routes, IP addresses, link parameters, neighbor setups, queueing
disciplines, traffic classes and packet classifiers may all be controlled
through
.B NETLINK_ROUTE
sockets.
-It is based on netlink messages, see
+It is based on netlink messages; see
.BR netlink (7)
for more information.
.\" FIXME ? all these macros could be moved to rtnetlink(3)
.BR RTM_NEWADDR ", " RTM_DELADDR ", " RTM_GETADDR
Add, remove or receive information about an IP address associated with
an interface.
-In Linux 2.2 an interface can carry multiple IP addresses,
+In Linux 2.2, an interface can carry multiple IP addresses,
this replaces the alias device concept in 2.0.
-In Linux 2.2 these messages
+In Linux 2.2, these messages
support IPv4 and IPv6 addresses.
They contain an
.I ifaddrmsg
structure, optionally followed by
-.I rtaddr
+.I rtattr
routing attributes.
.nf
.I rtattr
structures following.
For
-.B RTM_GETROUTE
+.BR RTM_GETROUTE ,
setting
.I rtm_dst_len
and
.I rtm_src_len
to 0 means you get all entries for the specified routing table.
-For the other fields except
+For the other fields, except
.I rtm_table
and
-.I rtm_protocol
+.IR rtm_protocol ,
0 is the wildcard.
.nf
.\" FIXME
.\" document the members of the struct better
The
-.I rtaddr
+.I rtattr
struct has the following meanings for the
.I rta_type
field: