IGMP/PIM with Sonos

RouterOS Beginner Basics
1

Hi,
I finally made the decision to switch to Mikrotik equipment on my home network :slight_smile:
Currently, I’m running the following setup:

Hex-S (RB760iGS) as a main router (router on a stick) running 6.49.7
Interfaces:

Flags: D - dynamic, X - disabled, R - running, S - slave 
 #     NAME                                TYPE       ACTUAL-MTU L2MTU  MAX-L2MTU
 0  R  ether1 - WAN                        ether            1500  1596       2026
 1  RS ether2 - HomeAssistant              ether            1500  1596       2026
 2  RS ether3 - SONOS                      ether            1500  1596       2026
 3  R  ether4 - AP1                        ether            1500  1596       2026
 4  R  ether5 - AP2                        ether            1500  1596       2026
 5  X  sfp1                                ether            1500  1596       2026
 6  R  BR-IOT                              bridge           1500  1596
 7  R  BR-LAN                              bridge           1500  1596
 8  R  BR-WIFI                             bridge           1500  1600
 9 DRS IoT 2.4Ghz-AP1-1                    cap              1500  1600
10 DRS IoT 2.4Ghz-AP2-1                    cap              1500  1600
11 DRS Owcahome 5Ghz-AP1-1                 cap              1500  1600
12 DRS Owcahome 5Ghz-AP2-1                 cap              1500  1600

via Capsman there are 2 Cap-Acs connected, which provide my wifi coverage (connected via ether4 and ether5). Owcahome is the main 5Ghz SSID where all the “regular” Clients connect to (Laptop, Phone etc.) whereby “IoT” is the 2.4Ghz Wifi which is providing my Iot Environment the necessary connectivity.

the follwing Networks have been established:

LAN - 10.10.50.0/24 (BR-LAN for ether2+3)
IOT - 10.10.20.0/24 (BR-IOT for CAP Interfaces)
WIFI - 10.10.10.0/24 (BR-WIFI for CAP Interfaces)

I’m running 4 Sonos Speakers (Play1 - old generation) whereby the one in the Livingroom is wired to ether3. All of the others are connected via SONOSNET (own Wifi provided by sonos).
All running smooth - Multicast routing is handled via PIM.
Only thing is, that i can see some warnings in the logs, whenever i open my laptop (10.10.10.130):

JoinDesired(*,G) = true: RP for group 239.255.255.250: not found
RX WHOLEPKT signal: vif_index = 31 src = 10.10.10.130 dst = 239.255.255.250 len = 153: no RP address for this group
[...]

Multicast routing is only enabled for interface BR-LAN (Players) and BR-WIFI (Controller)

/routing pim interface pr
Flags: X - disabled, I - inactive, D - dynamic, R - designated-router, 
v1 - IGMPv1, v2 - IGMPv2, v3 - IGMPv3 
 #      INTERFACE                            PROTOCOLS                          
 0  Rv2 BR-LAN                               pim                                
                                             igmp                               
 1  Rv2 BR-WIFI                              pim                                
                                             igmp                               
 2 DR   register                             pim

Playing works fine, Multicast groups do look “ok” to me (not an expert in this topic. fairly new to be honest).
Any ideas how to get rid of those warnings?

Thanks,
Ben

Sonos across VLANs
mDNS between VLANs with just bridge filters - Look Mum, no containers!
2

I could solve it by creating a “dummy” RP by using a loopback bridge interface:

interface bridge add name=BR-RP
ip address add address=10.10.99.1/32 interface=BR-RP
routing pim rp add address=10.10.99.1

as suggested in this thread : http://forum.mikrotik.com/t/no-rp-address-for-this-group/92204/1

3

After updating to ROS 7.8 this solution is no longer applicable (no multicast package exists for 7.8 - at least for my mmips HexS).
Therefore I went the route of least resistance and removed the SONOSNET by disconnecting the ethernet cable from one of the wired SONOS Speakers, updated them to latest version (they do now support 5Ghz Wifi :slight_smile:) and connected them to my main Wifi. Everything is fine now.
Only side-note, when using capsman : make sure Client To Client Forwarding is enabled - Otherwise the Controller (Sonos App) might not see the players, or they are appearing/disappearing randomly.

4

ROS 7 merged a bunch of packages into the main one, including “multicast.npk”.

If it were not so, CLI menus like “/routing/pimsm” wouldn’t exist until you installed the optional package.

Note that routing-related features got a complete overhaul in ROS 7, so your referenced post from 2015 doesn’t even give the right commands any more.

I don’t have PIM-SM working on ROS 7, but that’s because I don’t run multicast across VLANs or multiple subnets here. Plain old IGMP snooping over flat LANs does everything I want here. I’m just telling you that you aren’t even looking in the right places for solutions.

You can do worse by starting with the new docs.

5 
/routing pimsm instance
add disabled=no name=pimsm-instance1 vrf=main
/routing pimsm interface-template
add disabled=no instance=pimsm-instance1 interfaces=bridge,Guest

That made the Sonos on my main network controllable from the Guest Subnet.