Headache - Migrating Edgerouter 4 to Mikrotik CCR2116

RouterOS General
1

Good evening everyone,

I’m new to the Mikrotik world and I’m a bit lost. I have for 8 years an ER4 router with which I have been doing quite well, but due to lack of updates and security patches, I have decided to migrate to the mikrotik world.

Currently I have the ER4 router in “Router on a Stick” mode using the SFP network interface for the ISP (Triple VLAN) and one of the network ports for the LAN (Multiple VLAN). The ER4 configuration does not make use of any bridging or anything like that.

The Internet (VLAN 6 from the ISP) works perfectly, the VoIP service works fine, but the IPTv service is giving me a headache.
Captura.png

Problem is that IGMP Proxy is not joining a group. My firewall is very basic (Masquerade to SFP interfaces and input/forward drop into pppoe interface).


Captura de pantalla -2025-05-18 23-46-39.png


2025-05-18 23:48:08 by RouterOS 7.18.2

software id = XXXXXXXX

model = CCR2116-12G-4S+

serial number = XXXXXXXXXXXXX

/interface ethernet
set [ find default-name=ether4 ] disabled=yes
set [ find default-name=ether5 ] disabled=yes
set [ find default-name=ether6 ] disabled=yes
set [ find default-name=ether7 ] disabled=yes
set [ find default-name=ether8 ] disabled=yes
set [ find default-name=ether9 ] disabled=yes
set [ find default-name=ether10 ] disabled=yes
set [ find default-name=ether11 ] disabled=yes
set [ find default-name=ether12 ] comment=LAN name=lan
set [ find default-name=ether1 ] comment=“4G Internet” name=mobile_inet
set [ find default-name=ether3 ] comment=Wireshark name=mon_wireshark
set [ find default-name=sfp-sfpplus1 ] comment=“Modulo SFP Movistar” name=
sfp-movistar
set [ find default-name=sfp-sfpplus2 ] disabled=yes
set [ find default-name=sfp-sfpplus3 ] disabled=yes
set [ find default-name=sfp-sfpplus4 ] disabled=yes
set [ find default-name=ether2 ] comment=“Switch APC” name=switch_apc
/interface vlan
add comment=“LAN - Administracion” interface=lan name=lan_admin vlan-id=999
add comment=“LAN - Cluster RPi” interface=lan name=lan_clusterpi vlan-id=2000
add comment=“LAN - DMZ” interface=lan name=lan_dmz vlan-id=900
add comment=“LAN - Domotica” interface=lan name=lan_domotica vlan-id=70
add comment=“LAN - Invitados” interface=lan name=lan_guest vlan-id=240
add comment=“LAN - Multimedia” interface=lan name=lan_media vlan-id=200
add comment=“LAN - Servidores” interface=lan name=lan_servers vlan-id=100
add comment=“LAN - Voz IP” interface=lan name=lan_voip vlan-id=150
add comment=“Movistar - Inet” interface=sfp-movistar name=movistar_inet
vlan-id=6
add comment=“Movistar - IPTv” interface=sfp-movistar mvrp=yes name=
movistar_iptv vlan-id=2
add comment=“Movistar - VoIP” interface=sfp-movistar name=movistar_voip
vlan-id=3
/interface pppoe-client
add add-default-route=yes allow=pap,chap comment=“Movistar Inet” disabled=no
interface=movistar_inet max-mtu=1492 name=pppoe-movistar user=
adslppp@telefonicanetpa
/interface list
add comment=“Movistar SFP VLANS” name=movistar_vlans
/ip dhcp-server option
add code=6 comment=“Movistar IPTv - DNS Server” name=movistar_iptv_dns value=
“‘172.26.23.3’”
add code=240 comment=“Movistar IPTv - OPCH Servers” name=movistar_iptv_opch
value=“‘:::::239.0.2.10:22222:v6.0:239.0.2.30:22222’”
/ip pool
add comment=“Pool Administration LAN” name=pool_lan_admin ranges=
10.10.10.2-10.10.10.30
add comment=“Pool Cluester RPi” name=pool_cluster_rpi ranges=
10.0.100.2-10.0.100.50
add comment=“Pool Domotica LAN” name=pool_lan_domo ranges=
10.10.70.2-10.10.70.254
add comment=“Pool Invitados LAN” name=pool_lan_guest ranges=
192.168.240.2-192.168.240.20
add comment=“Pool Multimedia LAN” name=pool_lan_media ranges=
10.10.200.2-10.10.200.49
add comment=“Pool Servidores LAN” name=pool_lan_servers ranges=
10.10.100.2-10.10.100.40
add comment=“Pool VoIP LAN” name=pool_lan_voip ranges=10.10.150.2-10.10.150.4
add comment=“Pool IPTv Decodificadores” name=pool_lan_iptv_deco ranges=
10.10.200.110-10.10.200.120
/ip dhcp-server
add address-pool=pool_lan_admin comment=“LAN - Administracion” interface=
lan_admin lease-time=3d name=dhcp_admin
add address-pool=pool_cluster_rpi comment=“LAN - Cluster RPi” interface=
lan_clusterpi lease-time=1d name=dhcp_clusterpi
add address-pool=pool_lan_domo comment=“LAN - Domotica” interface=
lan_domotica lease-time=6h name=dhcp_domo
add address-pool=pool_lan_guest comment=“LAN - Invitados” interface=lan_guest
lease-time=2h name=dhcp_guest
add address-pool=pool_lan_media comment=“LAN - Multimedia” interface=
lan_media lease-time=12h name=dhcp_media
add address-pool=pool_lan_servers comment=“LAN - Servidores” interface=
lan_servers lease-time=2w1d name=dhcp_servers
add address-pool=pool_lan_voip comment=“LAN - VoIp” interface=lan_voip
lease-time=9h name=dhcp_voip
/port
set 0 name=serial0
/routing rip instance
add disabled=no name=rip-movistar
/interface list member
add comment=“Movistar Internet” interface=pppoe-movistar list=movistar_vlans
add comment=“Movistar IPTv” interface=movistar_iptv list=movistar_vlans
add comment=“Movistar VoIP” interface=movistar_voip list=movistar_vlans
/ip address
add address=192.168.88.1/24 comment=defconf interface=ether13 network=
192.168.88.0
add address=XXX.XXX.XXX.XXX/9 comment=“Movistar IPTv IP Address” interface=
movistar_iptv network=10.128.0.0
add address=192.168.50.1/24 comment=“Switch APC IP Address” interface=
switch_apc network=192.168.50.0
add address=10.10.70.1/24 comment=“LAN - Domotica IP” interface=lan_domotica
network=10.10.70.0
add address=10.10.100.1/24 comment=“LAN - Servers IP” interface=lan_servers
network=10.10.100.0
add address=10.10.150.1/29 comment=“LAN - VoIP IP” interface=lan_voip
network=10.10.150.0
add address=10.10.200.1/24 comment=“LAN - Multimedia IP” interface=lan_media
network=10.10.200.0
add address=192.168.240.1/24 comment=“LAN - Invitados IP” interface=lan_guest
network=192.168.240.0
add address=10.10.1.1/29 comment=“LAN - DMZ” interface=lan_dmz network=
10.10.1.0
add address=10.10.10.1/24 comment=“LAN - Administracion IP” interface=
lan_admin network=10.10.10.0
add address=10.0.100.1/24 comment=“LAN - Cluster RPi IP” interface=
lan_clusterpi network=10.0.100.0
add address=192.168.20.1/29 comment=“Monitoring & Wireshark IP” interface=
mon_wireshark network=192.168.20.0
/ip dhcp-client
add add-default-route=no comment=“Movistar VoIP IP Address” !dhcp-options
interface=movistar_voip use-peer-ntp=no

Interface not active

add comment=“4G Router IP Address” default-route-tables=main !dhcp-options
interface=mobile_inet use-peer-dns=no use-peer-ntp=no
/ip dhcp-server matcher
add address-pool=pool_lan_iptv_deco code=60 comment=
“Comprueba si es un deco IPTv Movistar” matching-type=substring name=
check_movistar_iptv_deco option-set=movistar_iptv_options server=
dhcp_media value=“[IAL]”
/ip dhcp-server network
add address=10.0.100.0/24 comment=“LAN - ClusterPi” dns-server=8.8.8.8
gateway=10.0.100.1
add address=10.10.10.0/24 comment=“LAN - Administracion” dns-server=
10.10.10.1 gateway=10.10.10.1 ntp-server=10.10.10.1
add address=10.10.70.0/24 comment=“LAN - Domotica” dns-server=10.10.70.1
gateway=10.10.70.1
add address=10.10.100.0/27 comment=“LAN - Servidores” dns-server=10.10.100.1
gateway=10.10.100.1
add address=10.10.150.0/29 comment=“LAN - VoIP” dns-none=yes gateway=
10.10.150.1
add address=10.10.200.0/24 comment=“LAN - Multimedia” dns-server=10.10.200.1
gateway=10.10.200.1 ntp-server=10.10.200.1
add address=192.168.240.0/24 comment=“LAN - Invitados” dns-server=1.0.0.1
gateway=192.168.240.1
/ip dhcp-server option sets
add name=movistar_iptv_options options=
movistar_iptv_dns,movistar_iptv_opch,*3
/ip dns
set allow-remote-requests=yes cache-size=8192KiB servers=
1.0.0.1,8.8.8.8,1.1.1.1
/ip firewall filter
add action=accept chain=forward connection-state=established,related
add action=drop chain=input connection-state=new in-interface=pppoe-movistar
add action=drop chain=forward connection-nat-state=!dstnat connection-state=
new in-interface=pppoe-movistar
/ip firewall mangle
add action=set-priority chain=postrouting new-priority=4 out-interface=
movistar_iptv
add action=change-mss chain=postrouting new-mss=1452 out-interface=
pppoe-movistar protocol=tcp tcp-flags=syn
add action=set-priority chain=postrouting new-priority=1 out-interface=
pppoe-movistar
add action=set-priority chain=postrouting new-priority=4 out-interface=
movistar_voip
/ip firewall nat
add action=masquerade chain=srcnat comment=“Masquerade Movistar SFP”
out-interface-list=movistar_vlans
add action=masquerade chain=srcnat comment=“Masquerade SFP Module”
dst-address=192.168.100.1 out-interface=sfp-movistar
/ip firewall service-port
set rtsp disabled=no
/ip route
add comment=“Movistar IPTv” disabled=no dst-address=10.64.0.0/10 gateway=
10.128.0.1 routing-table=main suppress-hw-offload=no
add comment=“Movistar IPTv” disabled=no dst-address=172.23.103.0/24 gateway=
10.128.0.1 routing-table=main suppress-hw-offload=no
add comment=“Movistar IPTv” disabled=no dst-address=172.26.22.0/26 gateway=
10.128.0.1 routing-table=main suppress-hw-offload=no
add comment=“Movistar IPTv” disabled=no dst-address=172.26.23.0/27 gateway=
10.128.0.1 routing-table=main suppress-hw-offload=no
add comment=“Movistar IPTv” disabled=no dst-address=172.26.80.0/21 gateway=
10.128.0.1 routing-table=main suppress-hw-offload=no
/routing igmp-proxy
set quick-leave=yes
/routing igmp-proxy interface
add alternative-subnets=0.0.0.0/0 comment=“Movistar IPTv Upstream” interface=
movistar_iptv upstream=yes
add alternative-subnets=10.10.200.0/24 comment=
“Movistar IPTv Downstream Decos” interface=lan_media
/routing rip interface-template
add disabled=no instance=rip-movistar interfaces=movistar_voip,movistar_iptv
mode=passive
/system clock
set time-zone-name=Europe/Madrid
/system logging
add action=disk topics=firewall
/system note
set show-at-login=no
/system ntp client
set enabled=yes
/system ntp server
set broadcast=yes broadcast-addresses=10.10.200.1,10.10.10.1 enabled=yes
/system ntp client servers
add address=es.pool.ntp.org

>

Please, your help is welcome.

Best regards
2

Good morning,

I have more updates. By default with this configuration, igmp-proxy does not create the routes when it asks a client to start receiving data:


IGMP-Proxy.png

And in the MFC tab no created routes are visible.


IGMP-Proxy-NoMFC.png

But the strange thing is that if I create a PIM-SN instance together with the IPTv upstream and multimedia network downstream interfaces…:



PIM-SN.png


The IGMP-Proxy starts to work and register addresses in the MFC tab:



IGMP-Proxy-Working.png


If I delete PIM-SN all is working after I reboot router. Why I need PIM-SN? In ER4 i don’t have anything about that, IGMP-Proxy works standalone.

I think the IGMP-Proxy is not working the right way or there is some kind of bug, because it is not able to start on the VLAN interface by itself. I also notice that after about 4 minutes, the Quick Leave does not work properly and I get cut off from the IPTv connection.

Regards

3

Not sure about IGMP Proxy but IGMP Snooping on ROS wont work without PIM-SM if you are running inside a VLAN.

As the IGMP Snooping only listens to normal Frames and not vlan tagged ones.
once you run a PIM-SM instance inside the VLAN IGMP Snooping works fine. (this is in the docs for IGMP Snooping)

4

Yes, you are right, but IGMP-Snooping only applies to switches or switch mode. In my configuration I have “Router on a Stick” on one interface so the work is made by the down switch. All other ports are not configured

EDIT: This is IGMP-Proxy Edgerouter 4 Log:

root@xxxxxxxx:~# igmpproxy -d -v
Using default configuration file “/etc/igmpproxy.conf”
14:33:29.678541 adding VIF, Ix 0 Fl 0x0 IP 0x0aae476d eth3.2, Threshold: 1, Ratelimit: 0
14:33:29.678747 adding VIF, Ix 1 Fl 0x0 IP 0x0a0ac801 eth2.200, Threshold: 1, Ratelimit: 0
14:33:29.678905 joinMcGroup: 224.0.0.2 on eth2.200
14:33:29.679019 joinMcGroup: 224.0.0.22 on eth2.200
14:33:29.733031 The IGMP message was local multicast. Ignoring.
14:33:29.947959 RECV V2 member report from 10.10.200.120 to 239.0.2.155
14:33:29.948110 Inserted route table entry for 239.0.2.155 on VIF #1
14:33:29.948164 joinMcGroup: 239.0.2.155 on eth3.2
14:33:29.975413 RECV V2 member report from 10.174.71.109 to 239.0.2.155
14:33:29.975500 The IGMP message was from myself. Ignoring.
14:33:29.975549 Route activation request from 10.174.71.109 for 239.0.2.155 is from myself. Ignoring.
14:33:30.000904 Adding MFC: 172.26.20.39 → 239.0.2.155, InpVIf: 0
14:33:31.347942 The IGMP message was local multicast. Ignoring.
14:33:31.450973 RECV V2 member report from 10.10.200.119 to 239.0.2.132
14:33:31.451075 Inserted route table entry for 239.0.2.132 on VIF #1
14:33:31.451115 joinMcGroup: 239.0.2.132 on eth3.2
14:33:31.475393 RECV V2 member report from 10.174.71.109 to 239.0.2.132
14:33:31.475479 The IGMP message was from myself. Ignoring.
14:33:31.475527 Route activation request from 10.174.71.109 for 239.0.2.132 is from myself. Ignoring.
14:33:31.509204 RECV V2 member report from 10.10.200.119 to 239.0.2.155
14:33:31.509288 Updated route entry for 239.0.2.155 on VIF #1
14:33:31.509328 Adding MFC: 172.26.20.39 → 239.0.2.155, InpVIf: 0
14:33:31.553586 Adding MFC: 172.26.20.39 → 239.0.2.132, InpVIf: 0
14:33:32.999703 RECV V2 member report from 10.10.200.118 to 239.0.2.2
14:33:32.999849 Inserted route table entry for 239.0.2.2 on VIF #1
14:33:32.999891 joinMcGroup: 239.0.2.2 on eth3.2
14:33:33.025498 RECV V2 member report from 10.174.71.109 to 239.0.2.2
14:33:33.025624 The IGMP message was from myself. Ignoring.
14:33:33.025679 Route activation request from 10.174.71.109 for 239.0.2.2 is from myself. Ignoring.
14:33:33.063441 The IGMP message was local multicast. Ignoring.
14:33:33.478061 RECV V2 member report from 10.10.200.120 to 239.0.2.30
14:33:33.478172 Inserted route table entry for 239.0.2.30 on VIF #1
14:33:33.478212 joinMcGroup: 239.0.2.30 on eth3.2
14:33:33.505404 RECV V2 member report from 10.174.71.109 to 239.0.2.30
14:33:33.505486 The IGMP message was from myself. Ignoring.
14:33:33.505533 Route activation request from 10.174.71.109 for 239.0.2.30 is from myself. Ignoring.
14:33:33.562813 Adding MFC: 172.26.20.41 → 239.0.2.30, InpVIf: 0
14:33:33.696849 RECV V2 member report from 10.10.200.119 to 239.0.2.30
14:33:33.696953 Updated route entry for 239.0.2.30 on VIF #1
14:33:33.696992 Adding MFC: 172.26.20.41 → 239.0.2.30, InpVIf: 0
14:33:33.929010 RECV V2 member report from 10.10.200.119 to 239.0.2.129
14:33:33.929119 Inserted route table entry for 239.0.2.129 on VIF #1
14:33:33.929158 joinMcGroup: 239.0.2.129 on eth3.2
14:33:33.955398 RECV V2 member report from 10.174.71.109 to 239.0.2.129
14:33:33.955484 The IGMP message was from myself. Ignoring.
14:33:33.955531 Route activation request from 10.174.71.109 for 239.0.2.129 is from myself. Ignoring.
14:33:34.367169 Adding MFC: 172.26.20.39 → 239.0.2.129, InpVIf: 0
14:33:34.605377 RECV V2 member report from 10.174.71.109 to 239.0.2.155
14:33:34.605464 The IGMP message was from myself. Ignoring.
14:33:34.645358 RECV V2 member report from 10.174.71.109 to 239.0.2.155
14:33:34.645434 The IGMP message was from myself. Ignoring.
14:33:34.685344 RECV V2 member report from 10.174.71.109 to 239.0.2.129
14:33:34.685420 The IGMP message was from myself. Ignoring.
14:33:35.085397 RECV V2 member report from 10.174.71.109 to 239.0.2.30
14:33:35.085501 The IGMP message was from myself. Ignoring.
14:33:35.425516 RECV V2 member report from 10.174.71.109 to 239.0.2.30
14:33:35.425637 The IGMP message was from myself. Ignoring.
14:33:35.631780 RECV V2 member report from 10.10.200.119 to 239.0.2.2
14:33:35.631889 Updated route entry for 239.0.2.2 on VIF #1
14:33:36.391625 RECV V2 member report from 10.10.200.118 to 239.0.2.129
14:33:36.391735 Updated route entry for 239.0.2.129 on VIF #1
14:33:36.391775 Adding MFC: 172.26.20.39 → 239.0.2.129, InpVIf: 0
14:33:36.903919 RECV V2 member report from 10.10.200.119 to 239.0.0.176
14:33:36.904046 Inserted route table entry for 239.0.0.176 on VIF #1
14:33:36.904086 joinMcGroup: 239.0.0.176 on eth3.2
14:33:36.925492 RECV V2 member report from 10.174.71.109 to 239.0.0.176
14:33:36.925599 The IGMP message was from myself. Ignoring.
14:33:36.925649 Route activation request from 10.174.71.109 for 239.0.0.176 is from myself. Ignoring.
14:33:36.934402 Adding MFC: 172.26.72.10 → 239.0.0.176, InpVIf: 0
14:33:37.415782 RECV V2 member report from 10.10.200.118 to 239.0.2.30
14:33:37.415906 Updated route entry for 239.0.2.30 on VIF #1
14:33:37.415947 Adding MFC: 172.26.20.41 → 239.0.2.30, InpVIf: 0
14:33:38.438260 RECV V2 member report from 10.10.200.120 to 239.0.2.2
14:33:38.438381 Updated route entry for 239.0.2.2 on VIF #1
14:33:38.439052 RECV V2 member report from 10.10.200.120 to 239.0.2.129
14:33:38.439131 Updated route entry for 239.0.2.129 on VIF #1
14:33:38.439168 Adding MFC: 172.26.20.39 → 239.0.2.129, InpVIf: 0
14:33:38.951876 RECV V2 member report from 10.10.200.118 to 239.0.2.155
14:33:38.952041 Updated route entry for 239.0.2.155 on VIF #1
14:33:38.952091 Adding MFC: 172.26.20.39 → 239.0.2.155, InpVIf: 0
14:33:40.525435 RECV V2 member report from 10.174.71.109 to 239.0.2.132
14:33:40.525541 The IGMP message was from myself. Ignoring.
14:33:41.725397 RECV V2 member report from 10.174.71.109 to 239.0.0.176
14:33:41.725502 The IGMP message was from myself. Ignoring.
14:33:42.445605 RECV V2 member report from 10.174.71.109 to 239.0.2.129
14:33:42.445704 The IGMP message was from myself. Ignoring.
14:33:42.445755 RECV V2 member report from 10.174.71.109 to 239.0.2.2
14:33:42.445784 The IGMP message was from myself. Ignoring.
14:33:45.001008 Inserted route table entry for 239.255.250.250 on VIF #-1
14:33:45.001189 Adding MFC: 10.10.200.5 → 239.255.250.250, InpVIf: 0
14:33:45.405436 RECV V2 member report from 10.174.71.109 to 239.0.2.2
14:33:45.405545 The IGMP message was from myself. Ignoring.
14:33:45.405595 Route activation request from 10.174.71.109 for 239.0.2.2 is from myself. Ignoring.
14:33:48.205634 RECV V2 member report from 10.174.71.109 to 239.0.2.132
14:33:48.205739 The IGMP message was from myself. Ignoring.
14:33:48.205792 Route activation request from 10.174.71.109 for 239.0.2.132 is from myself. Ignoring.
14:33:50.765536 RECV V2 member report from 10.174.71.109 to 239.0.0.176
14:33:50.765632 The IGMP message was from myself. Ignoring.
14:33:50.765685 Route activation request from 10.174.71.109 for 239.0.0.176 is from myself. Ignoring.
14:34:00.790290 RECV V2 member report from 10.10.200.119 to 239.0.2.30
14:34:00.790404 Updated route entry for 239.0.2.30 on VIF #1
14:34:00.790447 Adding MFC: 172.26.20.41 → 239.0.2.30, InpVIf: 0
14:34:00.992885 The IGMP message was local multicast. Ignoring.
14:34:01.353066 RECV V2 member report from 10.10.200.119 to 239.0.0.176
14:34:01.353168 Updated route entry for 239.0.0.176 on VIF #1
14:34:01.353208 Adding MFC: 172.26.72.10 → 239.0.0.176, InpVIf: 0
14:34:03.153092 RECV V2 member report from 10.10.200.119 to 239.0.2.155
14:34:03.153204 Updated route entry for 239.0.2.155 on VIF #1
14:34:03.153251 Adding MFC: 172.26.20.39 → 239.0.2.155, InpVIf: 0
14:34:03.157779 RECV V2 member report from 10.10.200.120 to 239.0.2.2
14:34:03.157872 Updated route entry for 239.0.2.2 on VIF #1
14:34:03.551155 RECV V2 member report from 10.10.200.119 to 239.0.2.2
14:34:03.551258 Updated route entry for 239.0.2.2 on VIF #1
14:34:04.104042 RECV V2 member report from 10.10.200.118 to 239.0.2.30
14:34:04.104158 Updated route entry for 239.0.2.30 on VIF #1
14:34:04.104198 Adding MFC: 172.26.20.41 → 239.0.2.30, InpVIf: 0
14:34:04.488068 RECV V2 member report from 10.10.200.118 to 239.0.2.129
14:34:04.488181 Updated route entry for 239.0.2.129 on VIF #1
14:34:04.488221 Adding MFC: 172.26.20.39 → 239.0.2.129, InpVIf: 0
14:34:04.872005 RECV V2 member report from 10.10.200.119 to 239.0.2.129
14:34:04.872123 Updated route entry for 239.0.2.129 on VIF #1
14:34:04.872162 Adding MFC: 172.26.20.39 → 239.0.2.129, InpVIf: 0
14:34:04.997971 RECV V2 member report from 10.10.200.120 to 239.0.2.30
14:34:04.998078 Updated route entry for 239.0.2.30 on VIF #1
14:34:04.998115 Adding MFC: 172.26.20.41 → 239.0.2.30, InpVIf: 0
14:34:05.071418 The IGMP message was local multicast. Ignoring.
14:34:05.253002 RECV V2 member report from 10.10.200.119 to 239.0.2.132
14:34:05.253110 Updated route entry for 239.0.2.132 on VIF #1
14:34:05.253148 Adding MFC: 172.26.20.39 → 239.0.2.132, InpVIf: 0
14:34:05.627890 The IGMP message was local multicast. Ignoring.
14:34:05.957896 RECV V2 member report from 10.10.200.120 to 239.0.2.155
14:34:05.958013 Updated route entry for 239.0.2.155 on VIF #1
14:34:05.958052 Adding MFC: 172.26.20.39 → 239.0.2.155, InpVIf: 0
14:34:06.597896 RECV V2 member report from 10.10.200.120 to 239.0.2.129
14:34:06.597997 Updated route entry for 239.0.2.129 on VIF #1
14:34:06.598035 Adding MFC: 172.26.20.39 → 239.0.2.129, InpVIf: 0
14:34:06.599950 RECV V2 member report from 10.10.200.118 to 239.0.2.2
14:34:06.600033 Updated route entry for 239.0.2.2 on VIF #1
14:34:07.112066 RECV V2 member report from 10.10.200.118 to 239.0.2.155
14:34:07.112181 Updated route entry for 239.0.2.155 on VIF #1
14:34:07.112219 Adding MFC: 172.26.20.39 → 239.0.2.155, InpVIf: 0
14:34:19.251821 The IGMP message was local multicast. Ignoring.
^C^C14:34:20.177754 select() failure; Errno(4): Interrupted system call
14:34:20.177853 Got a interrupt signal. Exiting.
14:34:20.177904 Removing MFC: 172.26.72.10 → 239.0.0.176, InpVIf: 0
14:34:20.177976 leaveMcGroup: 239.0.0.176 on eth3.2
14:34:20.178125 leaveMcGroup: 239.0.2.2 on eth3.2
14:34:20.178270 Removing MFC: 172.26.20.41 → 239.0.2.30, InpVIf: 0
14:34:20.178351 leaveMcGroup: 239.0.2.30 on eth3.2
14:34:20.178464 Removing MFC: 172.26.20.39 → 239.0.2.129, InpVIf: 0
14:34:20.178541 leaveMcGroup: 239.0.2.129 on eth3.2
14:34:20.178659 Removing MFC: 172.26.20.39 → 239.0.2.132, InpVIf: 0
14:34:20.178737 leaveMcGroup: 239.0.2.132 on eth3.2
14:34:20.178852 Removing MFC: 172.26.20.39 → 239.0.2.155, InpVIf: 0
14:34:20.178927 leaveMcGroup: 239.0.2.155 on eth3.2
14:34:20.179035 Removing MFC: 10.10.200.5 → 239.255.250.250, InpVIf: 0
14:34:20.179104 All routes removed. Routing table is empty.

You can see adding MFC Routes perfectly.