PS: In order to improve my knowledge of multicast and IGMP, I took a good look at this YouTube channel: [https://www.youtube.com/channel/UC2xDUkd\_PuxDvhl4zQz67Aw/featured](https://www .youtube.com/channel/UC2xDUkd_PuxDvhl4zQz67Aw/featured). So… if you have time… I found it very well prepared and quite exciting…
lostcarrier

- Joined
- Level1
- Points0
- Posts5
- Solutions1
BTW: I would recommend NOT following the Init-7 guide. A lot of effort is put into separating the interface with the Swisscom TV from the others. You can certainly do that and the instructions may also be a good help if you want to banish the Swisscom TV to its own VLAN, but it’s not necessary to just get the Swisscom TV running, so: Keep it simple , stupid!
The essentially required config is actually very simple:
- assuming the Swisscom Internet works and the Mikrotik Multicast/PIM package is installed!
- a firewall rule to allow IGMP packets from Swisscom and the internal network to pass through to the router. Everything else (UDP traffic,…) is obviously handled correctly by the usual NAT masquerading.
[admin@MikroTik] /ip firewall> filter print
Flags: X - disabled, I - invalid, D - dynamic
[…]
4 chain=input action=accept protocol=igmp in-interface=bridg1 log=no
5 chain=input action=accept protocol=igmp in-interface=vlan-swisscom log=no
[…]- a (started;-)) IGMP proxy. I configured the downstream interfaces as “all” - “bridge1” was thus configured automatically (Mikrotik say “dynamic”). This is simply my normal bridge to which more or less all devices are attached…
[admin@MikroTik] /ip firewall> /routing igmp-proxy interface print detail
Flags: X - disabled, I - inactive, D - dynamic, U - upstream
0 U interface=vlan-swisscom threshold=1 alternative-subnets=224.0.0.0/4,213.3.72.0/24,195.186.0.0/16 upstream=yes1 interface=all threshold=1 alternative-subnets="" upstream=no
2 D interface=bridge1 threshold=1 alternative-subnets="" upstream=no
For me, that’s enough for the Swisscom TV including live TV (multicast) to work on any port on the bridge.
Now you can/should activate IGMP snooping on the bridge so that the traffic is not distributed to all ports on the bridge. This obviously disables the bridge’s hardware offloading (…which should have little to no impact on at least a CCR 1009…).
I can’t claim that I understand exactly what’s happening down to the last detail, but that’s what multicast does for me.
\=> Hints / comments welcome!!!
Thank you for your tips!
- Solutionselected by ThomasS
OK - SOLVED!
@user109 In the end it wasn’t that dramatically research-heavy.
The message…
mikrotik: failed to start IGMP proxy, you probably some PIM interfaces configured
…probably actually means that the IGMP proxy is bothered by the fact that PIM is already active on one of the interfaces (-> either PIM OR proxy!).
I actually had two (supposedly “dynamically”) configured interfaces active in the PIM. However, these were probably NOT artifacts of an IGMP proxy (as I had originally suspected) but rather relics of my configuration attempts. Maybe At some point, some bug in RouterOS prevented the interfaces from actually being deleted - since then they have remained configured as “dynamic”. The solution to the riddle: “every boat is good”, unfortunately now also applies to Mikrotik! It’s annoying how much time this cost me, but after the reboot the interfaces disappeared from the PIM and the IGMP proxy could then be started…