mon/tripemon.in: Show per-peer crypto details in peer info sheet.

[tripe] / svc / tripe-ifup.8.in

diff --git a/svc/tripe-ifup.8.in b/svc/tripe-ifup.8.in
index 440c284247e0bde114e0351bfcb15c3fd2b31f29..2b500412aeba6a344776d637b5daa95c93f67d9e 100644 (file)
--- a/svc/tripe-ifup.8.in
+++ b/svc/tripe-ifup.8.in
@@ -103,16 +103,15 @@ performed using the new interface name.
 .hP 2.
 Configure the interface addresses.  If
 .I laddr
-is set, it should be a space-separated list of IPv4 and IPv6 addresses:
-there may be any number of either.
-If
+is set, it should be a space-separated list of IPv4 and IPv6 addresses
+with optional prefix lengths; there may be any number of either.  If
 .I raddr
-is set, it should be an IPv4 and/or an IPv6 address, separated by space:
-these are the addresses to configure as the remote end point of the
-point-to-point link.  (Further remote addresses can be configured as
-host routes: see below.)  IPv4 addresses are expected to be in
-dotted-quad form; IPv6 addresses should be in RFC4291 hex-and-colons
-form.
+is set, it should be a list IPv4 and/or an IPv6 addresses, with optional
+prefix lengths, separated by space: these are the addresses to
+configure as the remote end point of the point-to-point link.  (Further
+remote addresses can be configured as host routes: see below.)  IPv4
+addresses are expected to be in dotted-quad form; IPv6 addresses should
+be in RFC4291 hex-and-colons form.
 .hP 3.
 Establish routes.  If addresses were configured, and
 .I nets