How to add a IGMP querier on a tagged VLAN

Hi,

I have mutliple multicasts on different VLANs. As I understand the documentation (Bridge IGMP/MLD snooping - RouterOS - MikroTik Documentation), the Mirkotik bridge is not able to create IGMP querier on different VLANs.

So, is there a way to create mutliple querier on different VLANs? In older documentation there is a way via a PIM interface, but this is not there anymore.

Please help me! Thanks!

Geez, the docs still suck on the topic of IGMP and VLANs...

The bridge docs suggest:

Bridge IGMP querier implementation can only send untagged IGMP queries. In case tagged IGMP queries should be sent or IGMP queries should be generated in multiple VLANs, it is possible to install a multicast package, add a VLAN interface and configure a PIM interface on VLAN. The PIM interface can be used as an IGMP querier.

First, it info buried in a "call-out". And it's also confusing since ignores that the "multicast package" is no longer needed since V6. Most importantly, it ignores the "IGMP Proxy" in /routing/igmp-proxy/... which can operate on VLAN interface, since there just interfaces to the IGMP proxy (and makes to a bridge VLAN via an /interface/vlan port). While PIM also works, the bridge docs should at least mention the IGMP Proxy method, not steer folks to more complicated PIM-SM unless needed. See,

The IGMP proxy service can also act as quierier too. If you search forum for the IGMP proxy, you'll find some examples/discussions — since docs on IGMP proxy are rather "sparse" (geeky pin intended). That's what I'd recommend.

If you're looking for just mDNS discovery (used by Apple devices, and many others, to find devices/services via multicast)... newer RouterOS does support proxying multicast DNS/mDNS /"Bonjour" without any IGMP needed by just adding the interface where mDNS should be "shared".

Thanks for your kind reply. For your understanding, we use several VLANs with multicast (e.g. KNX, HDMI and audio streams).

 > /routing/igmp-proxy/export
/routing igmp-proxy
set query-interval=15s quick-leave=yes
/routing igmp-proxy interface
add alternative-subnets=0.0.0.0/0 interface=vlan1170 upstream=yes

but my IGMP porxy does not activat the "Querier" and stays "inactive".

What am I doing wrong?

To run IGMP proxy, you must configure both upstream and downstream (upstream=no) interfaces. All interfaces must be running and have assigned IP addresses. Downstream interfaces generate IGMP queries, while the upstream interface only forwards IGMP membership reports (joins) received from downstream interfaces, it does not generate queries.

If you only need querier functionality, you can configure a loopback (lo) interface as the upstream interface.

1 Like

Thanks for your support, but I am wondering why the proxy stays in INACTIVE state:

/routing igmp-proxy
set quick-leave=yes
/routing igmp-proxy interface
add interface=vlan1170
add alternative-subnets=0.0.0.0/0 interface=lo upstream=yes

State:

> /routing/igmp-proxy/interface/print 
Flags: I - INACTIVE; U - UPSTREAM
Columns: INTERFACE, THRESHOLD
#    INTERFACE  THRESHOLD
0 I  vlan1170           1
1 IU lo                 1

Make sure /ip/address is added to vlan1170 and lo.

@EdPa is right you can use a lo as a querier (and IGMP proxy'ed interface all need an IP address too).

But you don't need any querier if you only have one VLAN, since there is no need for multicast routing. So need to add all the VLAN you want part of the same multicast group, not just use vlan1170 and lo as that does nothing. Perhaps you're trying to see if you can remove Invalid status first... but just note you need 2+ VLANs for it do anything.

@EdPa - you should really add this info to the IGMP Proxy help page, and cross-reference from the Bridging page. I know there are some forum articles that suggest using lo/bridge to pin multicast reports... but the scheme belongs in docs IMO. Especially since PIM-SM is even tricker to setup and often overkill when "sharing" multicast across a set of VLANs - but the bridge docs point reader to only PIM-SM

Hi there,
IP adresses are set fine, but still INACTIVE:

/interface vlan
add interface=bridge1 name=vlan1170 vlan-id=1170
add interface=bridge1 name=vlan1180 vlan-id=1180

/ip address
add address=172.18.48.33/27 interface=vlan1180 network=172.18.48.32
add address=10.49.17.27/27 interface=vlan1170 network=10.49.17.0
add address=192.168.88.1/24 interface=lo network=192.168.88.0

/routing igmp-proxy
set quick-leave=yes

/routing igmp-proxy interface
add interface=vlan1170
add alternative-subnets=0.0.0.0/0 interface=lo upstream=yes

Interfaces are set, ping to other devices on same VLAN is working fine.

Thanks!

Is there a reason you don't add the other VLAN, presumable you want part same IGMP group:
/routing igmp-proxy interface add interface=vlan1180

HI, VLAN 1180 is my management VLAN.

If you have only one VLAN, there is no need for any IGMP proxy. Using lo allows you bridge two (or more) VLAN/other interfaces to mimic a querier.

Sorry, my bad. There are more VLANs to come. Even some with more IGMP networks.

Do you have any configuration under /routing/pimsm ? If you have added interfaces to PIM, it will not allow IGMP proxy to start.

Yeah, that was my fault. Thank you, everything is working fine now!

1 Like