Skip to content
MikroTik RouterOS Docs

IGMP Proxy

IGMP Proxy

Section titled “IGMP Proxy”

RouterOS 7 exposes IGMP Proxy as a small global settings object under /routing igmp-proxy. On current RouterOS 7 releases, the documented enable, interface, and mfc command trees are not present, so IGMP Proxy should be treated as a limited global feature rather than a per-interface configuration system.

Validation against RouterOS 7.15.3 confirmed that /routing igmp-proxy currently provides only these writable settings:

  • quick-leave
  • query-interval
  • query-response-interval

Summary

Section titled “Summary”

Use /routing igmp-proxy print to inspect the current global settings and /routing igmp-proxy set to adjust them. Do not expect RouterOS 7 to provide these commands:

  • /routing igmp-proxy enable
  • /routing igmp-proxy interface ...
  • /routing igmp-proxy mfc ...

Those command paths fail on RouterOS 7 and should not be used in production scripts or documentation.

Available Commands

Section titled “Available Commands”

Show Current Settings

Section titled “Show Current Settings”
/routing igmp-proxy print

On the validated RouterOS 7.15.3 system, the default output was:

quick-leave=no
query-interval=2m5s
query-response-interval=10s

Change Global Settings

Section titled “Change Global Settings”
/routing igmp-proxy set quick-leave=yes
/routing igmp-proxy set query-interval=3125

quick-leave toggles fast leave processing. query-interval and query-response-interval control the global IGMP timing values exposed by RouterOS 7.

Unsupported RouterOS 7 Commands

Section titled “Unsupported RouterOS 7 Commands”

The following examples are invalid on current RouterOS 7 releases and were removed from this page because they do not exist in the CLI:

/routing igmp-proxy enable
/routing igmp-proxy interface add interface=ether1 upstream=yes
/routing igmp-proxy interface print
/routing igmp-proxy mfc print detail

If you need interface-specific multicast control, review other RouterOS features such as bridge IGMP snooping or multicast routing protocols instead of relying on non-existent IGMP proxy submenus.

Troubleshooting

Section titled “Troubleshooting”

Verify Current State

Section titled “Verify Current State”

Start by checking the current global IGMP proxy settings:

/routing igmp-proxy print

If your scripts or operational runbooks reference enable, interface, or mfc subcommands, update them. Those commands fail with bad command name on RouterOS 7.

Firewall Considerations

Section titled “Firewall Considerations”

IGMP control traffic and multicast forwarding still require matching firewall policy:

/ip firewall filter add chain=input protocol=igmp action=accept
/ip firewall filter add chain=forward protocol=igmp action=accept
/ip firewall filter add chain=forward protocol=udp dst-address=224.0.0.0/4 action=accept

Debug Logging

Section titled “Debug Logging”

Enable logging while troubleshooting multicast behavior:

/system logging add topics=igmp-proxy,debug action=memory

Example

Section titled “Example”

The following example keeps the documented configuration limited to commands that were verified on RouterOS 7:

/routing igmp-proxy print
/routing igmp-proxy set quick-leave=yes
/routing igmp-proxy set query-interval=3125


/ip firewall filter add chain=input protocol=igmp action=accept
/ip firewall filter add chain=forward protocol=igmp action=accept
/ip firewall filter add chain=forward protocol=udp dst-address=224.0.0.0/4 action=accept


/system logging add topics=igmp-proxy,debug action=memory

This example documents the currently verified RouterOS 7 command surface without inventing unsupported per-interface or MFC configuration.

See Also

Section titled “See Also”