Cross VLAN Multicast / PIM Config

[broderick]

I set 3 interfaces in bridge (my main LAN), set also services on it. On another interface I set a different subnet for GUEST.
Would your setup work for DLNA discovery too? A device on the GUEST subnet needs to contact a service running on the LAN side.
Unfortunately I can’t set up VLANs at the moment. Thanks

If you don’t have VLANs, you don’t need PIM nor IGMP Proxy. The basic IGMP/MLD snooping configuration should be sufficient.

PIM/IGMP Proxy is for inter-VLAN routing.

I have most likely failed to understand it correctly, but by reading this wiki:
https://help.mikrotik.com/docs/pages/viewpage.action?pageId=59277403
The IGMP/MLD snooping can be set only for ports on the same bridge, which it doesn’t seem to be my case.

Thanks

[DarkNate]

The IGMP/MLD snooping can be set only for ports on the same bridge, which it doesn’t seem to be my case.

You are not supposed to be using multiple bridges, read this:
http://forum.mikrotik.com/t/mdns-repeater-feature/148334/326

[broderick]

The IGMP/MLD snooping can be set only for ports on the same bridge, which it doesn’t seem to be my case.

You are not supposed to be using multiple bridges, read this:
http://forum.mikrotik.com/t/mdns-repeater-feature/148334/326

It is a temporary setup. I’ll will set VLANs on the same bridge when I buy another VLAN-capable device to plug to ether 3 (GUEST now) which is going to be set as a trunk port so that I can have multiple VLANs on the new device.

[DarkNate]

It is a temporary setup. I’ll will set VLANs on the same bridge when I buy another VLAN-capable device to plug to ether 3 (GUEST now) which is going to be set as a trunk port so that I can have multiple VLANs on the new device.

You only need to configure access port based VLAN for your current setup, works fine on single bridge, doesn’t need to be trunked.

[broderick]

It is a temporary setup. I’ll will set VLANs on the same bridge when I buy another VLAN-capable device to plug to ether 3 (GUEST now) which is going to be set as a trunk port so that I can have multiple VLANs on the new device.

You only need to configure access port based VLAN for your current setup, works fine on single bridge, doesn’t need to be trunked.

Maybe I’m missing something here. Yes same bridge but I meant that Ether3 must be connected to a VLAN-capable switch/AP (it will most likely be another Mikrotik device, I guess), so it needs to be set as tagged port (this is why I called it “trunk” port). I can set the rest of the other ethernet ports on my current MK router as access/untagged ports, except Ether1 , the WAN port. Does it make sense? Thanks

[llamajaja]

I noticed the following on 7.12rc…
*) pimsm - improved system stability;
but more importantly in my case
*) wifiwave2 - implemented an option to transmit IP multicast packets as unicasts;

Reason being is I am going to attempt on an AX3, replacing ppoe internet on vlan, and IPTV on vlan on my brothers movistar modem/router to the mt router.
The good news is that both the internet and iptv seem to be sent untagged out on the wifi LAN being put out by the movistar router part…

Will post a separate thread…https://forum.mikrotik.com/viewtopic.php?t=200364

Q. Will I need to change from 7.11.2 to 7.12rc ( if that feature is absolutely required - seems like an IGMPv2 proxy requirement thus far )

[DarkNate]

I have a CCR<>ax2 setup, where ax2 is a layer 2 devices only.

I never actually see PIM packets on my Wi-Fi clients for some reason, it seems wifiwave2 blocks PIM packets? I am not sure, but the MDB table is properly populated so not sure what’s going on.

I check with WireShark on client side. I see PIM packets on ethernet though.

[pfturner]

I am currently using an mDNS repeater that works fine between VLAN10 (Personal), VLAN20 (Guest) and VLAN30 (IoT). I have Rokus, Printer and an Apple Airport Express (only purpose here is the 3.5mm connection to home speakers) all connected to switch access ports assigned to VLAN30 (IoT). However, I also have Unifi APs, using the PC controller it seems to require the native vlan “1”.

What I would like to do is:

(1) remove VLAN10 and simply use native vlan 1 for Personal - in which case Unifi APs are happy — but I need to get mDNS to work with the native vlan and VLAN20 and VLAN 30, instead of VLAN10) - have had no luck here despite trying to add eth0.1 or eth0 to the mDNS container config.

or

(2) replace the mDNS with a functioning PIM-SM configuration like DarkNate posted – will this work with a native vlan and VLAN20/VLAN30 setup? What do I put in the source-address IP entries in that example? The receiver device IPs?

Thanks for any insights!

[pfturner]

I was able to solve the Unifi AP/native vlan issue today. Still would be happy for thoughts on the PIM implementation VLAN10-20-30 and what source-address refers to in that context. Regards.

[Amm0]

(2) replace the mDNS with a functioning PIM-SM configuration like DarkNate posted – will this work with a native vlan and VLAN20/VLAN30 setup? What do I put in the source-address IP entries in that example? The receiver device IPs?

I believe PIM-SM follows the RFCs, so the link-local 224.0.0.51/24 of mDNS cannot be distributed via PIM (e.g. it’s the 224.0.0 “dst-address” that’s not allowed so src-address does not even come into play).

If you have Ruckus AP, and those are connected to all the needed VLANs, Ruckus has a good mDNS repeater features – I’d probably use that to deal with mDNS between VLANs.

@UpRunTech has tried a few approaches, which result in avoiding PIM / IGMP Proxy, and using bridge filters: http://forum.mikrotik.com/t/mdns-between-vlans-with-just-bridge-filters-look-mum-no-containers/173295/1

Mikrotik, well a year ago, discussed adding proper mDNS / DNS-SD support

MikroTik is working on mDNS repeater, but that will come together with a global DNS overhaul and it will be an improvement in all areas, not just this one. This is also why it takes some time to make.

…in the ~100K x viewed thread on the mDNS topic (and started in 2021): http://forum.mikrotik.com/t/mdns-repeater-feature/148334/1

[pfturner]

Thanks, I’ll read up on those suggestions. At least the mDNSNs repeater works well between VLAN10-20-30.