Technical data

4. Packages
IGMPPROXY_WLIST_N With this parameter the number of whitelists for IGMP reports
is determined.
IGMPPROXY_WHLIST_NET_x :
Using IGMPv3 all addresses may be summarized in one report which in turn will be
ignored completely. This leads to a complete shutdown of all Multicast traffic by the
IGMP Querier assuming that it is not needed anymore. To avoid this, configuration of
whitelists is used. Only Multicast goups in this list will be requested on the WAN side.
IGMPPROXY_WLIST_N='1' # Number of Multicast sources
IGMPPROXY_WHLIST_NET_1='239.35.0.0/16' # IPTV streams - always needed
# see above
Changes In Other Config Files
As of revision 32955 it is not necessary to adapt the firewall rules for IGMP Proxy and Mul-
ticast streams if the standard rules are activated in base.txt (PF_INPUT_ACCEPT_DEF=’yes’
and PF_FORWARD_ACCEPT_DEF=’yes’). The start script will automatically add these rules if
OPT_IGMPPROXY=’yes’ is set.
There will be two rules added to the INPUT chain to let the IGMP Proxy receive incoming
messages:
Chain INPUT (policy DROP 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
[...]
0 0 ACCEPT all -- * * 0.0.0.0/0 224.0.0.1 \
/* automatically added for IGMP Proxy */
0 0 ACCEPT all -- * * 0.0.0.0/0 224.0.0.22 \
/* automatically added for IGMP Proxy */
[...]
Another rule will be added to the FORWARD chain that enables forwarding of incoming
Multicast streams to the media receiver.
Chain FORWARD (policy DROP 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
[...]
0 0 ACCEPT all -- * * 0.0.0.0/0 239.35.0.0/16 \
/* automatically added for IPTV streams */
[..]
If the standard rules are not activated at least the following rules have to be added:
PF_INPUT_x='any 224.0.0.1/32 ACCEPT'
PF_INPUT_x='any 224.0.0.22/32 ACCEPT'
[...]
PF_FORWARD_x='any 239.35.0.0/16 ACCEPT'
198