Community discussions

MikroTik App
 
Dindihi
newbie
Topic Author
Posts: 27
Joined: Tue Jan 07, 2014 7:12 pm

SOLVED: IPTV on vlan and IGMP Proxy

Thu Jun 30, 2016 12:29 am

Hi,

i'm trying to configure my MT 951G with IPTV.
My provider sends all data through Vlan35. So i configured my LAN1 port with a Vlan35, and on this Vlan35, i configured my pppoe connection.
Works fine since month.
On Lan5, my Local net is connected.(bridge-local)
On Lan3, i have connected a laptop to test.

The TV stream is also transported through the same Vlan 35 as multicast 224.0.10.x.
I tried everything with the IGMP proxy and PIM. Does not work.

When i put the Vlan35 interface to my local lan bridge then the TV stream works fine, but internet connection is down.
Same with a separate bridge (e3 & vlan35 interface), TV ok, Inet NOK.

Maybe someone already had the same problem?

Thanks!




EDIT:
Problem solved. Had to add a dummy IP (192.168.10.1) to the vlan35 interface. Then the igmp proxy works fine.
No MFC added. Only Igmp proxy interfaces
Last edited by Dindihi on Wed Jul 13, 2016 10:04 am, edited 1 time in total.
 
Dindihi
newbie
Topic Author
Posts: 27
Joined: Tue Jan 07, 2014 7:12 pm

Re: IPTV on vlan and IGMP Proxy

Sat Jul 02, 2016 10:21 am

Some mor informations.

I installed a linux pc with 3 NIC, Masq for default inet traffic, and installed igmpproxy.
The config is really simple:
quickleave
phyint eth0.35 upstream  ratelimit 0  threshold 1
       altnet 224.0.0.0/4;
         altnet 172.19.7.1/32;
        altnet 88.207.164.58/32;

phyint eth2 downstream ratelimit 0 threshold 1
 altnet 192.168.215.0/24;


/routing igmp-proxy
set quick-leave=yes
/routing igmp-proxy interface
add alternative-subnets=224.0.0.0/4,172.19.7.1/32,88.207.164.58/32 interface=vlan35 upstream=yes
add interface=e3
/routing igmp-proxy mfc
add downstream-interfaces=e3 group=172.19.7.1 source=192.168.213.0 upstream-interface=vlan35
add downstream-interfaces=e3 group=224.0.0.0 source=192.168.213.0 upstream-interface=vlan35
add downstream-interfaces=e3 group=88.207.164.58 source=192.168.213.0 upstream-interface=vlan35



I also allowed the igmp and udp traffic to test:
/ip firewall filter
add chain=forward disabled=no protocol=udp
add chain=input disabled=no protocol=udp
add chain=forward disabled=no protocol=igmp
add chain=input disabled=no protocol=igmp


But on the MT with this config it does not work (ip address range changed here!)
 
omahena
just joined
Posts: 3
Joined: Wed Sep 28, 2016 3:07 pm

Re: SOLVED: IPTV on vlan and IGMP Proxy

Wed Sep 28, 2016 8:24 pm

Thank you for posting. We have the same provider and it was very useful to see what you did.

I did very much the same thing on my CRS109-8G-1S-2HnD-IN. The connection to the ISP required that I added vlan35 to the eth1-gatweay interface and then a PPPoE connection that binds to the vlan35.

It was very useful to be able to see what is going on with IGMP proxy in the log. To turn on logging for IGMP Proxy do:
/system logging add topics=igmp-proxy action=memory
Then the IGMP gateway config looks like this:
/routing igmp-proxy
set quick-leave=yes
/routing igmp-proxy interface
add alternative-subnets=172.19.7.1/32,172.19.9.4/32,192.168.1.0/24 interface=vnet35 upstream=yes
add interface=all
From logs it looks like I have to use both alternative subnets 172.19.7.1/32 and 172.19.9.4/32 to be able to watch all channels. And adding my own subnet 192.168.1.0/24 doesn't appear to influence the stream from starting to work, but from logs it looks like it may be needed for group membership upkeep... Although I find it strange that I need to add it as the network is directly accessible to the router and as such should be accepted by the igmp-proxy.

Any insight on why the local subnet was needed in the alternative-subnets is more than welcome.
 
Dindihi
newbie
Topic Author
Posts: 27
Joined: Tue Jan 07, 2014 7:12 pm

Re: SOLVED: IPTV on vlan and IGMP Proxy

Wed Sep 28, 2016 11:30 pm

Unfortunately i can't test anymore.
I had the TV Stream only for a few weeks to test (with MT), they disabled the stream again :-(
But maybe in the future, i fill book the IPTV service........
 
Dindihi
newbie
Topic Author
Posts: 27
Joined: Tue Jan 07, 2014 7:12 pm

Re: SOLVED: IPTV on vlan and IGMP Proxy

Thu Oct 27, 2016 11:14 pm

Just to let you know, i tested again my config, and i don't have to add my own subnet:
/routing igmp-proxy
set quick-leave=yes
/routing igmp-proxy interface
add alternative-subnets=224.0.0.0/4,172.19.7.1/32,88.207.164.58/32,172.19.9.4/32 interface=vlan35 upstream=yes
add interface=bridge-local
Did not tested each channel (don't have complete playlist), but ARD, ZDF, RTl, Sat1 are working fine.
However, i have some strange messages in my log:
Oct 27 22:07:55 192.168.215.154 igmp-proxy,debug igmp-proxy: ignoring request from unknown address  - "alternative-subnets" configuration may be required:
Oct 27 22:07:55 192.168.215.154 igmp-proxy,debug igmp-proxy:   source=192.168.215.254
Oct 27 22:07:55 192.168.215.154 igmp-proxy,debug igmp-proxy:   destination=239.255.255.250
Oct 27 22:07:56 192.168.215.154 igmp-proxy,debug igmp-proxy: ignoring IGMP message: source address is local:
Oct 27 22:07:56 192.168.215.154 igmp-proxy,debug igmp-proxy:   source=192.168.200.154
Oct 27 22:07:56 192.168.215.154 igmp-proxy,debug igmp-proxy:   interface=vlan35
Oct 27 22:07:56 192.168.215.154 igmp-proxy,debug igmp-proxy: ignoring request from myself:
Oct 27 22:07:56 192.168.215.154 igmp-proxy,debug igmp-proxy:   source=192.168.200.154
Oct 27 22:07:56 192.168.215.154 igmp-proxy,debug igmp-proxy:   destination=239.0.0.250
Oct 27 22:08:05 192.168.215.154 igmp-proxy,debug igmp-proxy: ignoring request from unknown address  - "alternative-subnets" configuration may be required:
Oct 27 22:08:05 192.168.215.154 igmp-proxy,debug igmp-proxy:   source=192.168.215.254
Oct 27 22:08:05 192.168.215.154 igmp-proxy,debug igmp-proxy:   destination=239.255.255.250
Oct 27 22:08:17 192.168.215.154 igmp-proxy,debug igmp-proxy: ignoring request from unknown address  - "alternative-subnets" configuration may be required:
Oct 27 22:08:17 192.168.215.154 igmp-proxy,debug igmp-proxy:   source=192.168.215.70
Oct 27 22:08:17 192.168.215.154 igmp-proxy,debug igmp-proxy:   destination=239.255.255.250
Oct 27 22:08:37 192.168.215.154 igmp-proxy,debug igmp-proxy: ignoring request from unknown address  - "alternative-subnets" configuration may be required:
Oct 27 22:08:37 192.168.215.154 igmp-proxy,debug igmp-proxy:   source=192.168.215.59
Oct 27 22:08:37 192.168.215.154 igmp-proxy,debug igmp-proxy:   destination=239.255.255.250
Oct 27 22:08:53 192.168.215.154 igmp-proxy,debug ignoring request from unknown address  - "alternative-subnets" configuration may be required:
Oct 27 22:08:53 192.168.215.154 igmp-proxy,debug   source=192.168.215.254
Oct 27 22:08:53 192.168.215.154 igmp-proxy,debug   destination=239.255.255.250
If i add my subnet, the "ignoring request from unknown address - "alternative-subnets" configuration may be required:" disappeared, but still the channels are working fine. So no change.
Oct 27 22:12:16 192.168.215.154 igmp-proxy,debug ignoring request from myself:
Oct 27 22:12:16 192.168.215.154 igmp-proxy,debug   source=192.168.200.154
Oct 27 22:12:16 192.168.215.154 igmp-proxy,debug   destination=239.0.0.250
Oct 27 22:12:17 192.168.215.154 igmp-proxy,debug ignoring IGMP message: source address is local:
Oct 27 22:12:17 192.168.215.154 igmp-proxy,debug   source=192.168.200.154
Oct 27 22:12:17 192.168.215.154 igmp-proxy,debug   interface=vlan35
Oct 27 22:12:17 192.168.215.154 igmp-proxy,debug ignoring request from myself:
Oct 27 22:12:17 192.168.215.154 igmp-proxy,debug   source=192.168.200.154
Oct 27 22:12:17 192.168.215.154 igmp-proxy,debug   destination=239.255.255.250
Oct 27 22:12:21 192.168.215.154 igmp-proxy,debug ignoring IGMP message: source address is local:
Oct 27 22:12:21 192.168.215.154 igmp-proxy,debug   source=192.168.200.154
Oct 27 22:12:21 192.168.215.154 igmp-proxy,debug   interface=vlan35
Oct 27 22:12:21 192.168.215.154 igmp-proxy,debug ignoring request from myself:
Oct 27 22:12:21 192.168.215.154 igmp-proxy,debug   source=192.168.200.154
Oct 27 22:12:21 192.168.215.154 igmp-proxy,debug   destination=224.10.0.17
 
thanhdiepts
just joined
Posts: 4
Joined: Fri Jun 17, 2016 5:30 am

Re: SOLVED: IPTV on vlan and IGMP Proxy

Tue Mar 03, 2020 3:14 pm

which version of routerOS bro?
 
Dindihi
newbie
Topic Author
Posts: 27
Joined: Tue Jan 07, 2014 7:12 pm

Re: SOLVED: IPTV on vlan and IGMP Proxy

Tue Mar 03, 2020 3:37 pm

When i wrote this post, don't remember.
Actual 6.46.3
 
shimatani
just joined
Posts: 1
Joined: Sun Sep 16, 2012 2:01 am

Re: SOLVED: IPTV on vlan and IGMP Proxy

Tue May 04, 2021 3:34 pm

Hi guys! Is there a problem with the igmp proxy in mikrotik version 6.48.2?
 
Dindihi
newbie
Topic Author
Posts: 27
Joined: Tue Jan 07, 2014 7:12 pm

Re: SOLVED: IPTV on vlan and IGMP Proxy

Wed May 05, 2021 10:33 am

Sorry, can't tell you. I stopped using the MT for IGMP. Had to place a Fritzbox infront of the MT to full use the IPTV properly :-(
 
ccanto
just joined
Posts: 10
Joined: Mon Apr 22, 2019 11:36 am

Re: SOLVED: IPTV on vlan and IGMP Proxy

Sat Jun 26, 2021 3:54 pm

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.

Who is online

Users browsing this forum: No registered users and 18 guests