Hi guys,
I also was faced with issues trying to make igmp-proxy working properly.
I spent 3 days with a lot of different configurations, but all ended up with the same symptom:
Multicast packets hit the WAN (IPTV VLAN) and does NOT get forwarded to LAN.
I started with the latest long term version 6.47.10 and ended up with the latest stable 6.48.3, without any difference in behavior.
My ISP delivers IPTV on VLAN 105 and general internet on VLAN 100.
My setup:
ether1 - directly connected to ISP
vlan100-net - dhcp client
vlan105-iptv - dhcp client
ether3 - different setup attempts:
a) directly connected to the Set-Top Box (STB), fixed ip with dhcp-server
b) member port of a bridge-lan: fixed ip with dhcp-server, without igmp-snooping
c) member port of a bridge-lan: fixed ip with dhcp-server, with igmp-snooping
the igmp-proxy config is the usual:
vlan105-iptv as upstream, alternative-subnets 10.0.0.0/8 (also tried 0.0.0.0/0 and other forum suggestions)
a) ether3
b) and c) bridge-lan
I can see that igmp-proxy is joining the right multicast group, but IS NOT adding the corresponding multicast forwarding entry:
jun/23 22:36:14 igmp-proxy,debug received notification:
jun/23 22:36:14 igmp-proxy,debug source=192.168.200.111
jun/23 22:36:14 igmp-proxy,debug destination=239.255.255.250
jun/23 22:36:14 igmp-proxy,debug RECV IGMPv2 membership report from 192.168.200.111 to 239.255.255.250 on bridgelan
jun/23 22:36:14 igmp-proxy,debug adding multicast forwarding entry
jun/23 22:36:14 igmp-proxy,debug group: 239.255.255.250
jun/23 22:36:14 igmp-proxy,debug source: 192.168.200.111
jun/23 22:36:14 igmp-proxy,debug joining multicast group 239.255.255.250 on vlan105-iptv
jun/23 22:38:11 igmp-proxy,debug RECV IGMPv2 membership report from 192.168.200.111 to 239.195.5.36 on bridgelan
jun/23 22:38:11 igmp-proxy,debug joining multicast group 239.195.5.36 on vlan105-iptv
jun/23 22:38:14 igmp-proxy,debug sending IGMP query to 239.195.5.36 on bridgelan
jun/23 22:38:14 igmp-proxy,debug leaving multicast group 239.195.5.36 on vlan105-iptv
jun/23 22:38:31 igmp-proxy,debug RECV IGMPv2 membership report from 192.168.200.111 to 239.195.5.36 on bridgelan
jun/23 22:38:31 igmp-proxy,debug joining multicast group 239.195.5.36 on vlan105-iptv
jun/23 22:38:37 igmp-proxy,debug RECV IGMPv2 membership report from 192.168.200.111 to 239.195.5.36 on bridgelan
jun/23 22:38:43 igmp-proxy,debug RECV IGMPv2 membership report from 192.168.200.111 to 239.195.5.36 on bridgelan
jun/23 22:40:48 igmp-proxy,debug RECV IGMPv2 membership report from 192.168.200.111 to 239.195.5.36 on bridgelan
jun/23 22:41:54 igmp-proxy,debug sending IGMP query to 239.195.5.36 on bridgelan
jun/23 22:41:54 igmp-proxy,debug leaving multicast group 239.195.5.36 on vlan105-iptv
jun/23 22:45:15 igmp-proxy,debug RECV IGMPv2 membership report from 192.168.200.111 to 239.195.5.36 on bridgelan
jun/23 22:45:15 igmp-proxy,debug joining multicast group 239.195.5.36 on vlan105-iptv
jun/23 22:45:25 igmp-proxy,debug RECV IGMPv2 membership report from 192.168.200.111 to 239.195.5.36 on bridgelan
jun/23 22:45:33 igmp-proxy,debug RECV IGMPv2 membership report from 192.168.200.111 to 239.195.5.36 on bridgelan
jun/23 22:47:02 igmp-proxy,debug RECV IGMPv2 membership report from 192.168.200.111 to 239.195.5.36 on bridgelan
...
192.168.200.111 is the STB
As a result, multicast packets to 239.195.5.36 is hitting the vlan105-iptv interface at 6.7Mbps without being forwarded to anywhere (btw: firewall input and forward rules are set to accept - no security for now)
I also noticed that with the c) setup (bridge with igmp-snooping), the group 239.195.5.36 was "snooped" to ether3 (bridge MDB tab), which means that igmp-snooping is correctly detecting and adding the group membership on that port.
On a side note about the same time, my Android phone joined a multicast group successfully:
jun/23 22:38:12 igmp-proxy,debug RECV IGMPv2 membership report from 192.168.200.114 to 224.0.1.187 on bridgelan
jun/23 22:38:12 igmp-proxy,debug joining multicast group 224.0.1.187 on vlan105-iptv
jun/23 22:38:28 igmp-proxy,debug received notification:
jun/23 22:38:28 igmp-proxy,debug source=192.168.200.114
jun/23 22:38:28 igmp-proxy,debug destination=224.0.1.187
jun/23 22:38:28 igmp-proxy,debug adding multicast forwarding entry
jun/23 22:38:28 igmp-proxy,debug group: 224.0.1.187
jun/23 22:38:28 igmp-proxy,debug source: 192.168.200.114
Trying to troubleshoot, I added the multicast entry for group 239.195.5.36 to source 192.168.200.111 manually in the igmp-proxy MFC table, increased "Query Interval" and "Query Response Interval", rebooted several times, and lots of other combinations, etc.. to no avail.
Why is the igmp-proxy behaving this way with the STB, I do not know as there isn't anything being logged that could explain it or to be any misconfiguration.
I also do not know why I do not see the "received notification" regarding the "source=192.168.200.111" and "destination=239.195.5.36" and why is he "leaving multicast group 239.195.5.36 on vlan105-iptv" at the same second as "sending IGMP query to 239.195.5.36 on bridgelan".
If someone has any insights as of why... please.
But having spent 3 days around this issue, I was pressured to solve it. So I ended up following @Dindihi advice and I simply bridged the vlan105-iptv to ether3 and used a cheap (€20) IGMP-proxy ready consumer router between ether3 and the STB and has been working fine ever since.