igmpproxy - Multicast router utilizing IGMP forwarding
igmpproxy [-h] [-n] [-d] [-v [-v]] config-file
is a simple multicast routing daemon which uses IGMP forwarding
to dynamically route multicast traffic. Routing is done by defining an
"upstream" interface on which the daemon act as a normal Multicast
client, and one or more "downstream" interfaces that serves clients
on the destination networks. This is useful in situations where other dynamic
multicast routers (like 'mrouted' or 'pimd') cannot be used.
only uses IGMP signalling, the daemon is only suited for
situations where multicast traffic comes from only one neighbouring network.
In more advanced cases, 'mrouted' or 'pimd' is probably more suited. The
daemon is not designed for cascading, and probably won't scale very well.
Currently only IGMPv1 and v2 is supported on downstream interfaces. On the
upstream interface the kernel IGMP client implementation is used, and
supported IGMP versions is therefore limited to that supported by the kernel.
- Display help.
- Verbose logging. Set logging level to INFO instead of WARNING used by
- More verbose logging. Set logging level to DEBUG.
- Do not run as a daemon.
- Output log messages to STDERR instead of to syslog(3). Implies
The current version compiles and runs fine with the Linux kernel version 2.4.
The known limits are:
more then 200
Multicast group membership:
- - contains the active multicast routes
- - contains the 'virtual' interfaces used by the active multicast routing
- - can be set to control what IGMP version the kernel should use on the
upstream interface. Ex.: 'echo 2 >
/proc/sys/net/ipv4/conf/eth0/force_igmp_version' will force the kernel to
use IGMPv2 on eth0 (provided this is the upstream interface).
, mrouted, pimd, smcroute
Currently none (but there probably will be :-/ )
Originally written by Johnny Egeland <firstname.lastname@example.org>.