I’m using 2 RouterBoard 450g’s with RouterOS v4.5 on each for a test pim-sm multicast network. I followed the instructions on the “Multicast detailed example” page http://wiki.mikrotik.com/wiki/Multicast_detailed_example. Everything was working fine a few days ago. Then I had the routers shutdown for a few days and now the Rendezvous Point is not forwarding multicast traffic.
Everything can ping everything else. Using the RouterOS packet sniffer, I verified that the proper PIM-Join messages are being sent from 192.168.3.2 to 192.168.3.1. The MFC even shows the proper incoming and outgoing interfaces for my multicast traffic. However, the multicast data is never sent from 192.168.3.1 to 192.168.3.2 and I have no idea why; I don’t remember changing any configuration settings from when it was previously working.
Any help will be greatly appreciated. Has anyone else experienced something similar?
first of, please upgrade to current RouterOS version (4.10) there where huge changes in PIM between now and 4.5
basics - multicast packet installed, routing-test is not, interfaces are added to /routing pim interfaces, and set to use same IGMP version across the intended multicast cloud. check if correct RP address is set on all routers, so there are no confusions where is the RP. Then, weather closest router to source is indicated as DR (designated router) for that multicast group you are multicasting.
Things i check -
first if first hop is receiving the source data stream.
second - check if RP is receiving the data stream, if RP is set to first router, move it further away from source. If first hop is receiving data stream, but RP is not, check weather you have set up correct TTL on multicast source, or on DR (designated router) change TTL of packets in mange chain=prerouting TTL from 1 to value higher, so it could reach the client.
after that usually i do not have to look any further
VLC have nasty bug, that it does not set correct TTL value for multicast streams it produces.
Here is the situation:
We are using just one Mikrotik, RB600A, with new RouterOS 4.10. We have multicast package installed.
We have done “[admin@MikroTik] > system reset-configuration”, upgrade version to 4.10 and installed multicast package too.
We have just configured ip addresses for eth1 and eth2(see the squeme below)
This is the scenario:
(VLC sending stream)Windows7 eth 172.16.0.2 → eth2 172.16.0.1 Mikrotik eth1 172.16.1.1 → 172.16.1.2 eth (VLC client) Windows7
It seems to receive traffic in Mikrotik eth2 (connection to server) we can see traffic in “interface menu”, but nothing is passed to eth1 to the client… The MFC is filled with the correct information also.
We set the scenario, we ping everything, and we have done a unicast stream successful!
We have tried with VLC and another program and have the same result.
I’m going to attach our router configuration file (export command output).
We have attached some screens also. In the screens we have used multicast ip 224.3.2.1 to port 1234.
Is the mikrotik’s firewall filtering by default multicast traffic??
We have set IGMP-Proxy, and obtain the same problem.
Both firewalls are turn off, the client and the server.
What happens is that Mikrotik is not passing multicast data…
Is anything wrong on the configuration file?
I have mikrotik 750g for ~5 months. I have tried igmp-proxy, pim, but multicasting isn’t working for me. RP address is correct. Few weeks ago I have “success” with multicasting.
Scenario:
run vlc
enable igmp-proxy
disable default mikrotik firewall drop filter
wait few seconds
disable igmp-proxy
enable pim http://www.youtube.com/watch?v=b0ThVoFnwRA
But after this configuration vlc shows only one channel (which was setted at the begining). I don’t know is this router OS bug or vlc. I’m tired to play with multicasting configuration…
Mikrotik support like others supports do you really set correct rp address? Are you sure you not running igmp-proxy and pim at the same time? It reminds me this illustration:
if you read this thread carefully you would notice that original poster solved the problem.
So i repeat - check if everything is ok with streams sent to you and devices directly connected to your router are responding correctly to IGMP requests. Main problem why IGMP-proxy might not work is - switch near you have snooping and does not respond to IGMP broadcasts sent by IGMP-proxy, hence IGMP-Proxy uses IGMPv3, but switch with snooping is hacked to work with IGMPv2 at best.
Static configuration is very simple for PIM, as can be read on wiki.
it can be condensed into this - add RP, add interfaces and off you go.
do you really set correct rp address? Are you sure you not running igmp-proxy and pim at the same time? It reminds me this illustration: