|MROUTED(8)||System Manager's Manual (smm)||MROUTED(8)|
mroutedis the original implementation of the Distance-Vector Multicast Routing Protocol (DVMRP), RFC 1075.
mroutedis simple to use. DVMRP is derived from RIP, RFC 1058, which means
mroutedworks stand-alone without any extra network setup required. You can get up and running in a matter of minutes.
mroutedmaintains topological knowledge via DVMRP, upon which it implements a multicast datagram forwarding algorithm called Reverse Path Multicasting.
mroutedforwards a multicast datagrams along the 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 been pruned back so that it does not extend beyond those subnetworks that have members of the destination group. Hence, datagrams are not forwarded along those branches which have no listeners of the multicast group. The IP time-to-live of a multicast datagram can be used to limit the range of multicast datagrams. In order to support multicasting among subnets that are separated by (unicast) routers that do not support IP multicasting,
mroutedincludes (built-in) support for IP-in-IP tunnels, which are virtual point-to-point links between pairs of DVMRP capable rotuers located anywhere in an internet. IP multicast packets are encapsulated for transmission through tunnels, so that they look like normal unicast datagrams to intervening routers and subnets. The encapsulation is added on entry to a tunnel, and stripped off on exit from a tunnel. The tunneling mechanism allows
mroutedto establish a virtual internet, for 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.
mroutedsuffers from the well-known scaling problems of any distance-vector routing protocol, and does not support hierarchical multicast routing. A more common practise today is to set up GRE tunnels between multicast capable routers and limit
mroutedto run on a select number of interfaces listed in the configuration.
mroutedhandles multicast routing only; there may or may not be unicast routing software running on the same machine as
mrouted. With the use of tunnels, it is not necessary for
mroutedto have access to more than one physical subnet in order to perform multicast forwarding.
mroutedto run in the foreground of the starting terminal, regardless of the
-lflag controls the (syslog) log level of each subsystem. Available subystems:
mroutedmust still be restarted to start listening on such interfaces, if they did not exist when
mrouteddefault behavior and assume all interfaces are disabled unless explicitly enabled with
phyint enablein /etc/mrouted.conf
mroutedin a non-pruning mode. This was previously used in routers for test purposes only. However, this is no longer supported and this option is only kept for compatibility reasons.
mroutedresponds to the following signals:
mroutedand reload the configuration file.
mroutedwrites its process ID to /var/run/mrouted.pid when it has completed its start up and is ready to receive signals.
mrouteddaemon when it has started up and is ready to receive commands.
mroutedhome page is ⟨http://github.com/troglobit/mrouted⟩
mrouted, listed in no particular order: David Waitzman,
|Mar 28 2019||Debian|