Manual:Routing/IGMP-Proxy: Difference between revisions

From MikroTik Wiki
Jump to navigation Jump to search
Line 11: Line 11:
==routing igmp-proxy==
==routing igmp-proxy==


* '''query-interval''' (integer[s|m|h] in range from 00:00:01 to 01:00:00) : it can be set as, an example, 685 or 685s or 00:11:25
* '''query-interval''' (integer[s|m|h] in range from 00:00:01 to 01:00:00) : it can be set as, an example, 685 or 685s or 00:11:25 sends you queries on interfaces that are not upstream for clients that want to join some IGMP groups
* '''query-response-interval''' (integer[s|m|h] in range from 00:00:01 to 01:00:00) : it can be set as, an example, 685 or 685s or 00:11:25
* '''query-response-interval''' (integer[s|m|h] in range from 00:00:01 to 01:00:00) : it can be set as, an example, 685 or 685s or 00:11:25 time when query failes
* '''quick-leave''' (yes|no) : should router itself stop sending igmp data stream or should it forward igmp leave request forward, so next IGMP aware device tops sending igmp data stream after leave command was initiated.
* '''quick-leave''' (yes|no) : should router itself stop sending igmp data stream or should it forward igmp leave request forward, so next IGMP aware device tops sending igmp data stream after leave command was initiated.



Revision as of 14:11, 22 December 2008

IGMP-Proxy

Internet Group Management Protocol Proxy allows users to proxy non-standard IGMP solution IGMP traffic over to other networks behind the router, thus allowing proprietary solution to distribute their content over network where network devices does not know anything about used inner workings of proprietary solution.

IGMP-Proxy features:

  • Distribute different IGMP based solution packets over network
  • Manage distribution of IGMP based solutions
  • On less powerful hardware when PIM-SM would be too heavy to run for it

routing igmp-proxy

  • query-interval (integer[s|m|h] in range from 00:00:01 to 01:00:00) : it can be set as, an example, 685 or 685s or 00:11:25 sends you queries on interfaces that are not upstream for clients that want to join some IGMP groups
  • query-response-interval (integer[s|m|h] in range from 00:00:01 to 01:00:00) : it can be set as, an example, 685 or 685s or 00:11:25 time when query failes
  • quick-leave (yes|no) : should router itself stop sending igmp data stream or should it forward igmp leave request forward, so next IGMP aware device tops sending igmp data stream after leave command was initiated.

routing igmp-proxy interface

It is used to configure what interfaces will participate as IGMP proxy interfaces on router. If interface is not configured as IGMP proxy interface, then all IGMP traffic received on port will be ignore.

  • alternative-subnets (ip address/subnet) : if IGMP data source comes from other network then configure on interface with upsrteam=yes then you have to set up this field to network, or address of source.
  • comment (text) : commentary on the entry in the entry in imgp-proxy interface list
  • disabled (yes|no) : is interface disabled
  • interface (interface name) : interface that this entry is set up for
  • rate-limit (integer) : does not work, will be omitted in the future
  • threshold (integer) : minimal TTL
  • upstream (yes|no) : set to yes if a proxy device's interface in the direction of the root of the tree, if no then a proxy device's interfaces that is not in the direction of the root of the tree. Router should have one and only one upstream interface. Upstream interface is responsible for forwarding IGMP membership requests.

routing igmp-proxy mfc

Here you can see what active group streams are going through the router

  • group (IP address) : IGMP group that is the owner of the data pasing
  • source (IP address) : router that these packets are originating from
  • incoming-interface (interface name) : packet stream is coming in router through this interface
  • outgoing-interface (interface name) : packet stream is going out of router through this interface