Specify an alternative file for configuration commands. Default is /etc/mrouted.conf.
If no -d option is given, or if the debug level is specified as 0, mrouted detaches from the invoking terminal. Otherwise, it remains attached to the invoking terminal and responsive to signals from that terminal. Regardless of the debug level, mrouted always writes warning and error messages to the system log daemon. The -debug-level argument is a comma-separated list of any of the following:
Display the type, source and destination of all packets sent or received.
Display more information about prunes sent or received.
Display more information about routing update packets sent or received.
Display routing updates in excruciating detail. This is generally way too much information.
Display information about neighbor discovery.
Display insertions, deletions and refreshes of entries in the kernel forwarding cache.
Debug timeouts and periodic processes.
Display information about interfaces and their configuration.
Display information about group memberships on physical interfaces.
Display information about multicast traceroute requests passing through this router.
Display IGMP operation including group membership and querier election.
Monitor ICMP handling.
Monitor RSRR operation.
Upon startup, mrouted writes its pid to the file /var/run/mrouted.pid.
Specifies, in seconds, the lifetime of a multicast forwarding cache entry in the kernel. Multicast forwarding cache entries in the kernel are checked every secs seconds, and are refreshed if the source is still active or deleted if not. Care should be taken when setting this value, as a low value can keep the kernel cache small at the cost of "thrashing" the cache for periodic senders, but high values can cause the kernel cache to grow unacceptably large. The default is 300 seconds (5 minutes).
Specifies, in seconds, the average lifetime of prunes that are sent towards parents. The actual lifetimes will be randomized in the range [.5secs,1.5secs]. The default is 7200 (2 hours). Smaller values cause less state to be kept both at this router and the parent, at the cost of more frequent broadcasts. However, some routers (e.g. mrouted <3.3 and all currently known versions of ciscos IOS) do not use the DVMRP generation ID to determine that a neighbor has rebooted. Prunes sent towards these neighbors should be kept short, in order to shorten 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.
The mrouted utility uses a DVMRP optimization to prevent having to keep individual routing tables for each neighbor; part of this optimization is that mrouted assumes that it is the forwarder for each of its attached subnets on startup. This can cause duplicates for a short period (approximately one full route report interval), since both the router that just started up and the proper forwarder will be forwarding traffic. This behavior can be turned off with the noflood keyword; mrouted will not assume that it is the forwarder on startup. 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.
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.
name "boundary-name scoped-addr/mask-len"
Associates boundary-name with the boundary described by scoped-addr/mask-len, to help make interface configurations more readable and reduce repetition in the configuration file.
The second section of the configuration file, which may optionally be empty, describes options that apply to physical interfaces.
The phyint command does nothing by itself; it is simply a place holder which interface-specific commands may follow. An interface address or name may be specified.
Disables multicast forwarding on this interface. By default, mrouted discovers all locally attached multicast capable interfaces and forwards on all of them.
If the kernels netmask does not accurately reflect the subnet (e.g. you are using proxy-ARP in lieu of IP subnetting), use the netmask command to describe the real netmask.
If a phyint is attached to multiple IP subnets, describe each additional subnet with the altnet keyword. This command may be specified multiple times to describe multiple subnets.
If there are any IGMPv1 routers on the phyint, use the igmpv1 keyword to force mrouted into IGMPv1 mode. All routers on the phyint must use the same version of IGMP.
Force mrouted to ignore other routers on this interface. mrouted will never send or accept neighbor probes or route reports on this interface.
In addition, the common vif commands described later may all be used on a phyint.
The third section of the configuration file, also optional, describes the configuration of any DVMRP tunnels this router might have.
This command establishes a DVMRP tunnel between this host (on the interface described by local-addr or ifname) and a remote host (identified by remote-addr or remote-hostname). A remote hostname may only be used if it maps to a single IP address. A tunnel must be configured on both routers before it can be used.
Be careful that the unicast route to the remote address goes out the interface specified by the "local-addr|ifname" argument. Some UNIX kernels rewrite the source address of s packets on their way out to contain the address of the transmission interface. This is best assured via a static host route.
The common vif commands described below may all be used on tunnels or phyints.
The metric is the "cost" associated with receiving a datagram on the given interface or tunnel; it may be used to influence the choice of routes. The metric defaults to 1. Metrics should be kept as small as possible, because DVMRP cannot route along paths with a sum of metrics greater than 31.
The advert_metric is the "cost" associated with sending a datagram on the given interface or tunnel; it may be used to influence the choice of routes. The advert_metric defaults to 0. Note that the effective metric of a link is one ends metric plus the other ends advert_metric.
The threshold is the minimum IP time-to-live required for a multicast datagram to be forwarded to the given interface or tunnel. It is used to control the scope of multicast datagrams. (The TTL of forwarded packets is only compared to the threshold, it is not decremented by the threshold. Every multicast router decrements the TTL by exactly 1.) The default threshold is 1.
In general, all multicast routers connected to a particular subnet or tunnel should use the same metric and threshold for that subnet or tunnel.
The rate_limit option allows the network administrator to specify a certain bandwidth in Kbits/second which would be allocated to multicast traffic. It defaults 0 (unlimited).
The boundary option allows an interface to be configured as an administrative boundary for the specified scoped address. Packets belonging to this address will not be forwarded on a scoped interface. The boundary option accepts either a name or a boundary spec. This command may be specified several times on an interface in order to describe multiple boundaries.
No packets will be sent on this link or tunnel until we hear from the other end. This is useful for the "server" end of a tunnel that goes over a dial-on-demand link; configure the "server" end as passive and it will not send its periodic probes until it hears one from the other side, so will not keep the link up. If this option is specified on both ends of a tunnel, the tunnel will never come up.
As described above, but only applicable to this interface/tunnel.
As described above, but only applicable to this interface/tunnel.
As described above, but only applicable to this interface/tunnel. Recall that prune retransmission defaults to on for point-to-point links and tunnels, and to off for multi-access links.
By default, mrouted refuses to peer with DVMRP neighbors that do not claim to support pruning. This option allows such peerings on this interface.
A specialized case of route filtering; no route learned from an interface marked "notransit" will be advertised on another interface marked "notransit". Marking only a single interface "notransit" has no meaning.
accept|deny "(route/mask-len [exact])+" [bidir]
The accept and deny commands allow rudimentary route filtering. The accept command causes mrouted to accept only the listed routes on the configured interface; the deny command causes mrouted to accept all but the listed routes. Only one of accept or deny commands may be used on a given interface.
The list of routes follows the accept or deny keyword. If the keyword exact follows a route, then only that route is matched; otherwise, that route and any more specific route is matched. For example, deny 0/0 denys all routes, while deny 0/0 exact denys only the default route. The default route may also be specified with the default keyword.
The bidir keyword enables bidirectional route filtering; the filter will be applied to routes on both output and input. Without the bidir keyword, accept and deny filters are only applied on input. Poison reverse routes are never filtered out.
The mrouted 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 mrouted configuration would be better replaced by more direct tunnels (i.e., eliminate the middle man).