TRB500 IGMP Proxy
The information in this page is updated in accordance with firmware version TRB5_R_00.07.04.3.
IGMPproxy is a simple dynamic Multicast Routing Daemon using only IGMP signalling (Internet Group Management Protocol). IGMP proxy enables the device to issue IGMP host messages on behalf of hosts that the device discovered through standard IGMP interfaces. The device acts as a proxy for its hosts.
Routing is done by defining an "upstream" interface on which the daemon act as a normal Multicast client, and one or more "downstream" interfaces that serves clients on the destination networks.
This chapter of the user manual provides an overview of the IGMP Proxy page in TRB500 devices.
Note: IGMP Proxy is additional software that can be installed from the Services → Package Manager page.
If you're having trouble finding this page or some of the parameters described here on your device's WebUI, you should turn on "Advanced WebUI" mode. You can do that by clicking the "Basic" button under "Mode", which is located at the top-right corner of the WebUI.
|Enable||off | on; default: off||Enables the IGMP Proxy service.|
|Quickleave||off | on; default: on||If enabled, the daemon will send a Leave IGMP message upstream as soon as it receives a Leave message for any downstream interface.|
By default, there are no routing interfaces configured. To create one, press Add.
Routing Interface Configuration
This section is used to configure the create routing interface.
|Direction||Upstream | Downstream; default: Upstream||Interface is called "upstream" if it's in the direction of the root of the multicast tree. An IGMP forwarding router must have exactly one upstream interface configured..|
|Interface||network interface; default: lan||The name of the interface the settings are for.|
|Firewall||firewall zone; default: lan||Name of a firewall zone this interface belongs to.|
|Networks||ip/netmask; default: none||A list of CIDR-masked Network entries to control what subnets are allowed to have their multicast data proxied. Multiple subnets can be configured or 0.0.0.0/0 specified to allow any network. Option can be omitted entirely to only allow same network as configured on interface.|