I'm puzzled by a relatively straight forward setup.
(Multicast client)192.168.82.50 -----------------192.168.82.1MikrotikRouter10.82.79.1--------------IPIP Tunnel---------------10.82.79.2MikrotikRouter2192.168.79.2---------------192.168.79.1 Multicast source

So, I've got PIM enabled on the local bridge interfaces, and on the IPIP tunnel interface.
[admin@MikrotikRouter] > routing pim export
# aug/29/2017 21:48:31 by RouterOS 6.38.7
# software id = HANY-G2QR
#
/routing pim interface
add interface=bridge-local
add interface=Tunel-MikroTik2
/routing pim rp
add address=192.168.79.2


[admin@MikrotikRouter2] > routing pim export
# aug/29/2017 21:49:01 by RouterOS 6.38.7
# software id = Q2JY-B7H6
#
/routing pim interface
add interface=Tunnel-MikroTik
add interface=bridge-local

/routing pim rp
add address=192.168.79.2

So when I register a multicast sender behind MikroTik Router on multicast group 226.94.10.1 and than try to reach it from behind MikroTik Router2 it does not work. I'm using iperf to test this:
On the sender
iperf -s -u -B 226.94.10.1 -i 1

On the receiver
iperf -c 226.94.1.1 -u -T 32 -t 3 -i 1

Am I missing something in my configuration?

An update:
Both routers see each other as PIM neighbors:
[bsotirov@Mikrotik1] > routing pim neighbors print
ADDRESS INTERFACE PRIORITY TIMEOUT
10.82.79.2 Tunel-rtsf79

[bsotirov@Mikrotik2] > routing pim neighbors print
ADDRESS INTERFACE PRIORITY TIMEOUT
10.82.79.1 Tunnel-rtsf82

I have also allowed IGMP in the input chain on both routers along with UDP. IGMP and UDP are also allowed in the forward chain on both routers. I could indeed see the IGMP messages on the tunnel interface between the routers.

Regards,
Boyan

Any ideas on how to further troubleshoot that?


Regards,
Boyan

Look in the status windows to see if the routers show your multicast group e.g. 226.94.10.1
Also - since you use two different groups with iperf - I assume that one or the other is the real group your system uses, and not 224.0.0.x (which is defined as local segment only - i.e. it doesn't pass through routers).

If you see the group and members, then I'd suspect that the firewall rules are filtering your stream. You could try placing a rule near the top of the forward chain which allows address-type=multicast in-interface / out-interface=tunnel
(or just accept all packets in/out the tunnels and then narrow it down from there if that broad stroke works)

It turned out it's working, but I have issues with the end hosts. The reason I need Multicast routing is for DLNA. It turned out though some DLNA clients use different ports in requesting content. That's the reason why it was not working. So I have to figure out a way now to change the end client behavior.


Regards,
Boyan

Look in the status windows to see if the routers show your multicast group e.g. 226.94.10.1
Also - since you use two different groups with iperf - I assume that one or the other is the real group your system uses, and not 224.0.0.x (which is defined as local segment only - i.e. it doesn't pass through routers).

If you see the group and members, then I'd suspect that the firewall rules are filtering your stream. You could try placing a rule near the top of the forward chain which allows address-type=multicast in-interface / out-interface=tunnel
(or just accept all packets in/out the tunnels and then narrow it down from there if that broad stroke works)

Hello,

I've been testing a group of 700 TV IP tuners for a long time (IP TV).
I tested PIM protcol with CCR CCR1009, CCR1036 and X86 (Ethernet Controller Intel 82599 10Gb/s).

I've always tested the same configuration.
Tests showed that CCR works very badly.
Every moment there were breaks in Video and sound.
Sometimes there was a total stoppage.


But RouterOS with X86 and Ethernet Controller Intel 82599 10Gb/s worked very well.
Works perfectly.
I always use the same configuration for the 10Gb/s port.
Always RouterOS 6.41.3 and today 6.41.4
Thought that he even works more stable than Cisco Better than CISCO!
I do not know but the question is what is the reason.