Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pim: igmp: T5733: adjust to latest CLI syntax #1151

Merged
merged 1 commit into from
Nov 15, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
77 changes: 77 additions & 0 deletions docs/configuration/protocols/igmp-proxy.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,77 @@
:lastproofread: 2023-11-13

.. _igmp_proxy:

##########
IGMP Proxy
##########

:abbr:`IGMP (Internet Group Management Protocol)` proxy sends IGMP host messages
on behalf of a connected client. The configuration must define one, and only one
upstream interface, and one or more downstream interfaces.

Configuration
=============

.. cfgcmd:: set protocols igmp-proxy interface <interface> role
<upstream | downstream>

* **upstream:** The upstream network interface is the outgoing interface
which is responsible for communicating to available multicast data sources.
There can only be one upstream interface.

* **downstream:** Downstream network interfaces are the distribution
interfaces to the destination networks, where multicast clients can join
groups and receive multicast data. One or more downstream interfaces must
be configured.

.. cfgcmd:: set protocols igmp-proxy interface <interface> alt-subnet <network>

Defines alternate sources for multicasting and IGMP data. The network address
must be on the following format 'a.b.c.d/n'. By default, the router will
accept data from sources on the same network as configured on an interface.
If the multicast source lies on a remote network, one must define from where
traffic should be accepted.

This is especially useful for the upstream interface, since the source for
multicast traffic is often from a remote location.

This option can be supplied multiple times.

.. cfgcmd:: set protocols igmp-proxy disable-quickleave

Disables quickleave mode. In this mode the daemon will not send a Leave IGMP
message upstream as soon as it receives a Leave message for any downstream
interface. The daemon will not ask for Membership reports on the downstream
interfaces, and if a report is received the group is not joined again the
upstream.

If it's vital that the daemon should act exactly like a real multicast client
on the upstream interface, this function should be enabled.

Enabling this function increases the risk of bandwidth saturation.

.. cfgcmd:: set protocols igmp-proxy disable

Disable this service.

.. _igmp:proxy_example:

Example
-------

Interface `eth1` LAN is behind NAT. In order to subscribe `10.0.0.0/23` subnet
multicast which is in `eth0` WAN we need to configure igmp-proxy.

.. code-block:: none

set protocols igmp-proxy interface eth0 role upstream
set protocols igmp-proxy interface eth0 alt-subnet 10.0.0.0/23
set protocols igmp-proxy interface eth1 role downstream

Operation
=========

.. opcmd:: restart igmp-proxy

Restart the IGMP proxy process.
249 changes: 0 additions & 249 deletions docs/configuration/protocols/igmp.rst

This file was deleted.

4 changes: 2 additions & 2 deletions docs/configuration/protocols/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,6 @@
Protocols
#########


.. toctree::
:maxdepth: 1
:includehidden:
Expand All @@ -11,11 +10,12 @@ Protocols
bfd
bgp
failover
igmp
igmp-proxy
isis
mpls
segment-routing
ospf
pim
pim6
rip
rpki
Expand Down
2 changes: 0 additions & 2 deletions docs/configuration/protocols/pim.disable

This file was deleted.

Loading
Loading