9,561
edits
Changes
Template:Networking rutos manual igmp proxy (view source)
Revision as of 14:18, 28 March 2022
, 14:18, 28 March 2022Created page with "{{Template: Networking_rutos_manual_fw_disclosure | fw_version ={{Template: Networking_rutos_manual_latest_fw | series = {{{series}}} }} }} ==Summary== <b>IGMPproxy</b> is..."
{{Template: Networking_rutos_manual_fw_disclosure
| fw_version ={{Template: Networking_rutos_manual_latest_fw
| series = {{{series}}}
}}
}}
==Summary==
<b>IGMPproxy</b> 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 {{{name}}} devices.
<b>Note:</b> IGMP Proxy is additional software that can be installed from the <b>Services → [[{{{name}}} Package Manager|Package Manager]]</b> page.
----
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
| series = {{{series}}}
}}
==General Settings==
[[File:Networking_rutos_manual_igm_proxy_general_settings_v1.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on; default: <b>off</b></td>
<td>Enables the IGMP Proxy service.</td>
</tr>
<tr>
<td>Quickleave</td>
<td>off | on; default: <b>on</b></td>
<td>If enabled, the daemon will send a Leave IGMP message upstream as soon as it receives a Leave message for any downstream interface.</td>
</tr>
</table>
==Routing Interfaces==
By default, there are no routing interfaces configured. To create one, press <b>Add</b>.
[[File:Networking_rutos_manual_igm_proxy_routing_interfaces_overview_v1.png|border|class=tlt-border]]
===Routing Interface Configuration===
----
This section is used to configure the create routing interface.
[[File:Networking_rutos_manual_igm_proxy_routing_interfaces_edit_v1.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Direction</td>
<td>Upstream | Downstream; default: <b>Upstream</b></td>
<td>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..</td>
</tr>
<tr>
<td>Interface</td>
<td>network interface; default: <b>lan</b></td>
<td>The name of the interface the settings are for.</td>
</tr>
<tr>
<td>Firewall</td>
<td>firewall zone; default: <b>lan</b></td>
<td>Name of a firewall zone this interface belongs to.</td>
</tr>
<tr>
<td>Networks</td>
<td>ip/netmask; default: <b>none</b></td>
<td>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.</td>
</tr>
</table>
| fw_version ={{Template: Networking_rutos_manual_latest_fw
| series = {{{series}}}
}}
}}
==Summary==
<b>IGMPproxy</b> 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 {{{name}}} devices.
<b>Note:</b> IGMP Proxy is additional software that can be installed from the <b>Services → [[{{{name}}} Package Manager|Package Manager]]</b> page.
----
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
| series = {{{series}}}
}}
==General Settings==
[[File:Networking_rutos_manual_igm_proxy_general_settings_v1.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on; default: <b>off</b></td>
<td>Enables the IGMP Proxy service.</td>
</tr>
<tr>
<td>Quickleave</td>
<td>off | on; default: <b>on</b></td>
<td>If enabled, the daemon will send a Leave IGMP message upstream as soon as it receives a Leave message for any downstream interface.</td>
</tr>
</table>
==Routing Interfaces==
By default, there are no routing interfaces configured. To create one, press <b>Add</b>.
[[File:Networking_rutos_manual_igm_proxy_routing_interfaces_overview_v1.png|border|class=tlt-border]]
===Routing Interface Configuration===
----
This section is used to configure the create routing interface.
[[File:Networking_rutos_manual_igm_proxy_routing_interfaces_edit_v1.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Direction</td>
<td>Upstream | Downstream; default: <b>Upstream</b></td>
<td>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..</td>
</tr>
<tr>
<td>Interface</td>
<td>network interface; default: <b>lan</b></td>
<td>The name of the interface the settings are for.</td>
</tr>
<tr>
<td>Firewall</td>
<td>firewall zone; default: <b>lan</b></td>
<td>Name of a firewall zone this interface belongs to.</td>
</tr>
<tr>
<td>Networks</td>
<td>ip/netmask; default: <b>none</b></td>
<td>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.</td>
</tr>
</table>
