Enables quickleave mode. In this mode the daemon will send a Leave IGMP message upstream as soon as it receives a Leave message for any downstream interface. The daemon will then ask for Membership reports on the downstream interfaces, and if a report is received the group is joined again upstream. Normally this is not noticed at all by clients on the downstream networks. If it's vital that the daemon should act exactly as a real multicast client on the upstream interface, this function should not be used. Disabling this function increases the risk of bandwidth saturation.

Defines the state and settings of a network interface.

The name of the interface the settings are for. This option is required for phyint settings.

The role of the interface. This should be either upstream (only one interface), downstream (one or more interfaces) or disabled . This option is required.

Defines a ratelimit for the network interface. If ratelimit is set to 0 (default), no ratelimit will be applied. This setting is optional.

Defines the TTL threshold for the network interface. Packets with a lower TTL than the threshols value will be ignored. This setting is optional, and by default the threshold is 1.

Defines alternate sources for multicasting and IGMP data. The network address must be on the following format 'a.b.c.d/n'. By default the router will accept data from sources on the same network as configured on an interface. If the multicast source lies on a remote network, one must define from where traffic should be accepted.

This is especially useful for the upstream interface, since the source for multicast traffic is often from a remote location. Any number of altnet parameters can be specified.

Defines a whitelist for multicast groups. The network address must be in the following format 'a.b.c.d/n'. If you want to allow one single group use a network mask of /32, i.e. 'a.b.c.d/32'.

By default all multicast groups are allowed on any downstream interface. If at least one whitelist entry is defined, all igmp membership reports for not explicitly whitelisted multicast groups will be ignored and therefore not be served by igmpproxy. This is especially useful, if your provider does only allow a predefined set of multicast groups. These whitelists are only obeyed by igmpproxy itself, they won't prevent any other igmp client running on the same machine as igmpproxy from requesting 'unallowed' multicast groups.

You may specify as many whitelist entries as needed. Although you should keep it as simple as possible, as this list is parsed for every membership report and therefore this increases igmp response times. Often used or large groups should be defined first, as parsing ends as soon as a group matches an entry.

You may also specify whitelist entries for the upstream interface. Only igmp membership reports for explicitly whitelisted multicast groups will be sent out on the upstream interface. This is useful if you want to use multicast groups only between your downstream interfaces, like SSDP from a UPnP server.