summaryrefslogtreecommitdiffstats
path: root/usr.sbin/mrouted
diff options
context:
space:
mode:
authorcharnier <charnier@FreeBSD.org>2002-07-14 14:47:15 +0000
committercharnier <charnier@FreeBSD.org>2002-07-14 14:47:15 +0000
commitd2168fe021bd1693c1038503e09d3d74dd8b6f36 (patch)
tree1cffbfcbeace5b3e6b01d3c6b67a9c10233bc810 /usr.sbin/mrouted
parent745a7b1537c2ebb511bcf928366eefe72af77dac (diff)
downloadFreeBSD-src-d2168fe021bd1693c1038503e09d3d74dd8b6f36.zip
FreeBSD-src-d2168fe021bd1693c1038503e09d3d74dd8b6f36.tar.gz
The .Nm utility
Diffstat (limited to 'usr.sbin/mrouted')
-rw-r--r--usr.sbin/mrouted/map-mbone.813
-rw-r--r--usr.sbin/mrouted/mrinfo.814
-rw-r--r--usr.sbin/mrouted/mrouted.846
-rw-r--r--usr.sbin/mrouted/mtrace.810
4 files changed, 52 insertions, 31 deletions
diff --git a/usr.sbin/mrouted/map-mbone.8 b/usr.sbin/mrouted/map-mbone.8
index 5260042..a6e9e58 100644
--- a/usr.sbin/mrouted/map-mbone.8
+++ b/usr.sbin/mrouted/map-mbone.8
@@ -16,14 +16,18 @@
.Op Fl t Ar timeout_count
.Op Ar starting_router
.Sh DESCRIPTION
-.Nm Map-mbone
+The
+.Nm
+utility
attempts to display all multicast routers that are reachable from the multicast
.Ar starting_router .
If not specified on the command line, the default multicast
.Ar starting_router
is the localhost.
.Pp
-.Nm Map-mbone
+The
+.Nm
+utility
traverses neighboring multicast routers by sending the ASK_NEIGHBORS IGMP
message to the multicast starting_router.
If this multicast router responds,
@@ -81,8 +85,9 @@ reply before retrying.
Default timeout is 2 seconds.
.El
.Sh IMPORTANT NOTE
-.Nm Map-mbone
-must be run as root.
+The
+.Nm
+utility must be run as root.
.Sh SEE ALSO
.Xr mrinfo 8 ,
.Xr mrouted 8 ,
diff --git a/usr.sbin/mrouted/mrinfo.8 b/usr.sbin/mrouted/mrinfo.8
index b06b4b9..6e655a8 100644
--- a/usr.sbin/mrouted/mrinfo.8
+++ b/usr.sbin/mrouted/mrinfo.8
@@ -13,12 +13,15 @@
.Op Fl t Ar timeout_count
.Ar multicast_router
.Sh DESCRIPTION
-.Nm Mrinfo
+The
+.Nm
+utility
attempts to display the configuration information from the multicast router
.Ar multicast_router .
.Pp
-.Nm Mrinfo
-uses the ASK_NEIGHBORS IGMP message to the specified multicast router.
+The
+.Nm
+utility uses the ASK_NEIGHBORS IGMP message to the specified multicast router.
If this
multicast router responds, the version number and a list of their neighboring
multicast router addresses is part of that response.
@@ -77,8 +80,9 @@ If
the queried multicast router has a newer version number, the type (tunnel,
srcrt) and status (disabled, down) of the connection is displayed.
.Sh IMPORTANT NOTE
-.Nm Mrinfo
-must be run as root.
+The
+.Nm
+utility must be run as root.
.Sh SEE ALSO
.Xr map-mbone 8 ,
.Xr mrouted 8 ,
diff --git a/usr.sbin/mrouted/mrouted.8 b/usr.sbin/mrouted/mrouted.8
index 695ae64..27a2256 100644
--- a/usr.sbin/mrouted/mrouted.8
+++ b/usr.sbin/mrouted/mrouted.8
@@ -14,15 +14,17 @@
.Op Fl d Op Ar debug_level
.Op Fl p
.Sh DESCRIPTION
-.Nm Mrouted
-is an implementation of the Distance-Vector Multicast Routing
+The
+.Nm
+utility is an implementation of the Distance-Vector Multicast Routing
Protocol (DVMRP), an earlier version of which is specified in RFC-1075.
It maintains topological knowledge via a distance-vector routing protocol
(like RIP, described in RFC-1058), upon which it implements a multicast
datagram forwarding algorithm called Reverse Path Multicasting.
.Pp
-.Nm Mrouted
-forwards a multicast datagram along a shortest (reverse) path tree
+The
+.Nm
+utility forwards a multicast datagram along a shortest (reverse) path tree
rooted at the subnet on which the datagram originates.
The multicast
delivery tree may be thought of as a broadcast delivery tree that has
@@ -60,11 +62,14 @@ the purpose of multicasting only, which is independent of the physical
internet, and which may span multiple Autonomous Systems. This capability
is intended for experimental support of internet multicasting only, pending
widespread support for multicast routing by the regular (unicast) routers.
-.Nm Mrouted
-suffers from the well-known scaling problems of any distance-vector
+The
+.Nm
+utility suffers from the well-known scaling problems of any distance-vector
routing protocol, and does not (yet) support hierarchical multicast routing.
.Pp
-.Nm Mrouted
+The
+.Nm
+utility
handles multicast routing only; there may or may not be unicast routing
software running on the same machine as
.Nm .
@@ -131,8 +136,9 @@ writes its pid to the file
.Pa /var/run/mrouted.pid .
.El
.Sh CONFIGURATION
-.Nm Mrouted
-automatically configures itself to forward on all multicast-capable
+The
+.Nm
+utility automatically configures itself to forward on all multicast-capable
interfaces, i.e., interfaces that have the IFF_MULTICAST flag set (excluding
the loopback "interface"), and it finds other DVMRP routers directly reachable
via those interfaces. To override the default configuration, or to add
@@ -174,7 +180,9 @@ the time to recover from a reboot. For use in this situation, the
prune_lifetime keyword may be specified on an interface as described
below.
.It noflood
-.Nm Mrouted
+The
+.Nm
+utility
uses a DVMRP optimization to prevent having to keep individual routing tables
for each neighbor; part of this optimization is that
.Nm
@@ -189,8 +197,7 @@ Turning on noflood can cause black holes on restart, which will generally
last approximately one full route report interval.
The noflood keyword can also be specified on individual interfaces.
.It rexmit_prunes Ar [on|off]
-.Nm Mrouted Ns 's
-default is to retransmit prunes on all point-to-point interfaces
+Default is to retransmit prunes on all point-to-point interfaces
(including tunnels) but no multi-access interfaces. This option
may be used to make the default on (or off) for all interfaces.
The rexmit_prunes keyword can also be specified on individual interfaces.
@@ -379,8 +386,9 @@ filters are only applied on input. Poison reverse routes are never
filtered out.
.El
.Pp
-.Nm Mrouted
-will not initiate execution if it has fewer than two enabled vifs,
+The
+.Nm
+utility will not initiate execution if it has fewer than two enabled vifs,
where a vif (virtual interface) is either a physical multicast-capable
interface or a tunnel. It will log a warning if all of its vifs are
tunnels; such an
@@ -426,8 +434,9 @@ tunnel 192.168.5.4 10.11.12.13 metric 1 threshold 32
boundary LOCAL boundary EE
.Ed
.Sh SIGNALS
-.Nm Mrouted
-responds to the following signals:
+The
+.Nm
+utility responds to the following signals:
.Bl -tag -width indent
.It HUP
Restarts
@@ -515,8 +524,9 @@ the outgoing vif is connected to a leaf of the broadcast tree rooted at the
origin, and a multicast datagram from that origin will be forwarded on that
outgoing vif only if there are members of the destination group on that leaf.
.Pp
-.Nm Mrouted
-also maintains a copy of the kernel forwarding cache table.
+The
+.Nm
+utility also maintains a copy of the kernel forwarding cache table.
Entries
are created and deleted by
.Nm .
diff --git a/usr.sbin/mrouted/mtrace.8 b/usr.sbin/mrouted/mtrace.8
index f4d1a44..e95b59d 100644
--- a/usr.sbin/mrouted/mtrace.8
+++ b/usr.sbin/mrouted/mtrace.8
@@ -64,8 +64,9 @@
.Sh DESCRIPTION
Assessing problems in the distribution of IP multicast traffic
can be difficult.
-.Nm Mtrace
-utilizes a tracing feature implemented in multicast routers that is
+The
+.Nm
+utility utilizes a tracing feature implemented in multicast routers that is
accessed via an extension to the IGMP protocol. A trace query is
passed hop-by-hop along the reverse path from the
.Ar receiver
@@ -212,7 +213,7 @@ seconds (default 3 seconds).
.Ss "How It Works"
The technique used by the
.Nm traceroute
-tool to trace unicast network paths will not work for IP multicast
+utility to trace unicast network paths will not work for IP multicast
because ICMP responses are specifically forbidden for multicast traffic.
Instead, a tracing feature has been built into the multicast routers.
This technique has the advantage that additional information about
@@ -331,8 +332,9 @@ will try to query the next hop router with a DVMRP_ASK_NEIGHBORS2
request (as used by the
.Nm mrinfo
program) to see what kind of router it is.
+The
.Nm
-will try to query three (changed with the
+utility will try to query three (changed with the
.Fl e
option) hops past a non-responding router, in the hopes that even
though it isn't capable of sending a response, it might be capable of
OpenPOWER on IntegriCloud