summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorpluknet <pluknet@FreeBSD.org>2012-03-07 09:42:19 +0000
committerpluknet <pluknet@FreeBSD.org>2012-03-07 09:42:19 +0000
commit0d910635b103117f4f090aa846bfa2a69717d257 (patch)
tree84b12c67da8aa3f71bd588566fc055c8cac7b16e
parent9d4d411642d8ae4323ed9b0a43cc35dcd602a654 (diff)
downloadFreeBSD-src-0d910635b103117f4f090aa846bfa2a69717d257.zip
FreeBSD-src-0d910635b103117f4f090aa846bfa2a69717d257.tar.gz
Update ifa_rtrequest() description after post-4.4BSD change made in r85074.
3rd argument of ifa->ifa_rtrequest is now ``rt_addrinfo *'' instead of ``sockaddr *''. While here, un-document RTM_RESOLVE cmd argument for ifa_rtrequest() that became a stub after separating L2 tables in r186119. MFC after: 1 week
-rw-r--r--share/man/man9/ifnet.915
1 files changed, 6 insertions, 9 deletions
diff --git a/share/man/man9/ifnet.9 b/share/man/man9/ifnet.9
index b439623..6c2424e 100644
--- a/share/man/man9/ifnet.9
+++ b/share/man/man9/ifnet.9
@@ -28,7 +28,7 @@
.\"
.\" $FreeBSD$
.\"
-.Dd March 2, 2012
+.Dd March 7, 2012
.Dt IFNET 9
.Os
.Sh NAME
@@ -122,7 +122,7 @@
.Ss "struct ifaddr member function"
.Ft void
.Fo \*(lp*ifa_rtrequest\*(rp
-.Fa "int cmd" "struct rtentry *rt" "struct sockaddr *dst"
+.Fa "int cmd" "struct rtentry *rt" "struct rt_addrinfo *info"
.Fc
.\"
.Ss "Global Variables"
@@ -1016,22 +1016,19 @@ function.
is a pointer to a function which receives callouts from the routing
code
.Pq Fn rtrequest
-to perform link-layer-specific actions upon requests to add, resolve,
+to perform link-layer-specific actions upon requests to add,
or delete routes.
The
.Fa cmd
argument indicates the request in question:
-.Dv RTM_ADD , RTM_RESOLVE ,
+.Dv RTM_ADD ,
or
.Dv RTM_DELETE .
The
.Fa rt
argument is the route in question; the
-.Fa dst
-argument is the specific destination being manipulated
-for
-.Dv RTM_RESOLVE ,
-or a null pointer otherwise.
+.Fa info
+argument contains the specific destination being manipulated.
.Sh FUNCTIONS
The functions provided by the generic interface code can be divided
into two groups: those which manipulate interfaces, and those which
OpenPOWER on IntegriCloud