Hubbry Logo
search
logo
Internet Group Management Protocol avatar
Internet Group Management Protocol
Internet Group Management Protocol
current hub
I

Internet Group Management Protocol

logo
Community Hub0 Subscribers
Read side by side
Internet Group Management Protocol
View on Wikipedia
from Wikipedia

The Internet Group Management Protocol (IGMP) is a communications protocol used by hosts and adjacent routers on IPv4 networks to establish multicast group memberships. IGMP is an integral part of IP multicast and allows the network to direct multicast transmissions only to hosts that have requested them.

IGMP can be used for one-to-many networking applications such as online streaming video and gaming, and allows more efficient use of resources when supporting these types of applications.

IGMP is used on IPv4 networks. Multicast management on IPv6 networks is handled by Multicast Listener Discovery (MLD) which is a part of ICMPv6 in contrast to IGMP's bare IP encapsulation.

Architecture

[edit]

A network designed to deliver a multicast service using IGMP might use this basic architecture:

IGMP operates between a host and a local multicast router. Switches featuring IGMP snooping also derive useful information by observing these IGMP transactions. Protocol Independent Multicast (PIM) is then used between the local and remote multicast routers to direct multicast traffic from hosts sending multicasts to hosts that have registered through IGMP to receive them.

IGMP operates on the network layer (layer 3), just the same as other network management protocols like ICMP.[1]

The IGMP protocol is implemented on hosts and within routers. A host requests membership to a group through its local router while a router listens for these requests and periodically sends out subscription queries. A single router per subnet is elected to perform this querying function. Some multilayer switches include an IGMP querier capability to allow their IGMP snooping features to work in the absence of an IGMP-capable router in the layer 2 network.

IGMP is vulnerable to some attacks,[2][3][4][5] and firewalls commonly allow the user to disable it if not needed.

Versions

[edit]

There are three versions of IGMP.[6] IGMPv1 was defined in 1989.[7] IGMPv2, defined in 1997,[8] improves IGMPv1 by adding the ability for a host to signal a desire to leave a multicast group.

In 2002, IGMPv3 improved IGMPv2 by supporting source-specific multicast[9] and introduces membership report aggregation.[10] The support for source-specific multicast was improved in 2006.[11]

The three versions of IGMP are backward compatible. A router supporting IGMPv3 can support clients running IGMPv1, IGMPv2, and IGMPv3. IGMPv1 uses a query-response model. Queries are sent to 224.0.0.1. Membership reports are sent to the group's multicast address. IGMPv2 accelerates the process of leaving a group and adjusts other timeouts. Leave-group messages are sent to 224.0.0.2. A group-specific query is introduced. Group-specific queries are sent to the group's multicast address. A means for routers to select an IGMP querier for the network is introduced. IGMPv3 introduces source-specific multicast capability. Membership reports are sent to 224.0.0.22.

Messages

[edit]

There are several types of IGMP messages:

General membership queries
Sent by multicast routers to determine which multicast addresses are of interest to systems attached to the network(s) they serve to refresh the group membership state for all systems on its network.
Group-specific membership queries
Used for determining the reception state for a particular multicast address.
Group-and-source-specific queries
Allow the router to determine if any systems desire reception of messages sent to a multicast group from a source address specified in a list of unicast addresses.
Membership reports
Sent by multicast receivers in response to a membership query or asynchronously when first registering for a multicast group.
Leave group messages
Sent by multicast receivers when specified multicast transmissions are no longer needed at the receiver.

IGMP messages are carried in bare IP packets with IP protocol number 2.[10]: §4  Similar to the Internet Control Message Protocol, there is no transport layer used with IGMP messaging.

IGMPv2 messages

[edit]
IGMPv2 packet structure[8]: §2 
Offset Octet 0 1 2 3
Octet Bit 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
0 0 Type Maximum Response Time Checksum
4 32 Group Address
Type: 8 bits
Indicates the message type as follows:
Message Type value
Membership Query 0x11
IGMPv1 Membership Report 0x12
IGMPv2 Membership Report 0x16
IGMPv3 Membership Report 0x22
Leave Group 0x17
Maximum Response Time: 8 bits
Specifies the required responsiveness of replies to a Membership Query (0x11). This field is meaningful only in Membership Query; in other messages, it is set to 0 and ignored by the receiver. The field specifies time in units of 0.1 second (a field value of 10 specifies 1 second). Larger values reduce IGMP traffic burstiness and smaller values improve protocol responsiveness when the last host leaves a group.[8]: §2.2 
Checksum: 16 bits
This is the 16-bit ones' complement of the ones' complement sum of the entire IGMP message. Computed before sending, with this field set to zero. When re-computed on reception of the packet, this field is included, and the result should be zero.
Group Address: 32 bits
This is the multicast address being queried when sending a Group-Specific or Group-and-Source-Specific Query. The field is zeroed when sending a General Query.
The message is sent to the following IP multicast addresses:[8]: §9 
Message type Multicast address
General Query All hosts (224.0.0.1)
Group-Specific Query The group being queried
Membership Report (all IGMP versions) The group being reported
Leave Group All routers (224.0.0.2)

IGMPv3 membership query

[edit]
IGMPv3 membership query[10]: §4.1 
Offset Octet 0 1 2 3
Octet Bit 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
0 0 Type (0x11) Maximum Response Code Checksum
4 32 Group Address
8 64 Reserved S QRV QQIC Number of Sources (N)
12 96 Source Address[1]
16 128 Source Address[2]
⋮ ⋮ ⋮
⁠⁠ ⁠⁠ Source Address[n]
Type: 8 bits
Indicates the type of the packet. A value of 0x11 indicates IGMPv3 Membership Query.
Maximum Response Code: 8 bits
This field is used to compute the Maximum Response Time (in 1/10 second increments) allowed before sending a responding report. If the number is below 128, the value is used directly. If the value is 128 or more, it is interpreted as an exponent and mantissa.
Checksum: 16 bits
This is the 16-bit ones' complement of the ones' complement sum of the entire IGMP message. Computed before sending, with this field set to zero. When re-computed on reception of the packet, this field is included, and the result should be zero.
Group Address: 32 bits
This is the multicast address being queried when sending a Group-Specific or Group-and-Source-Specific Query. The field is zeroed when sending a General Query.
Reserved: 4 bits
This field is reserved. It should be zeroed when sent and ignored when received.
Suppress Router-side Processing (S): 1 bit
When this flag is set, it indicates to receiving routers that they are to suppress the normal timer updates.
Querier's Robustness Variable (QRV): 3 bits
If this is non-zero, it contains the Robustness Variable value used by the sender of the query. Routers should update their Robustness Variable to match the most recently received query unless the value is zero. QRV sets tolerance for packet loss, allowing up to QRV - 1 lost packets. Zero is invalid, one is discouraged; default is 2.
Querier's Query Interval Code (QQIC): 8 bits
This code is used to specify the Query Interval value (in seconds) used by the querier. If the number is below 128, the value is used directly. If the value is 128 or more, it is interpreted as an exponent and mantissa.
Number of Sources (N): 16 bits
This field specifies the number of source addresses present in the query. For General and Group-Specific Queries, this value is zero. For Group-and-Source-Specific Queries, this value is non-zero, but limited by the network's MTU.
Source Address [i]: 32 bits
The Source Address [i] fields are a vector of n IP unicast addresses, where n is the value in the Number of Sources (N) field.

Implementations

[edit]

FreeBSD,[note 1] Linux[note 2] and Windows all support IGMP on the host side.

See also

[edit]

Notes

[edit]

References

[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Internet Group Management Protocol

View on Grokipedia
from Grokipedia
The Internet Group Management Protocol (IGMP) is a network-layer communications protocol used by hosts and multicast routers on IPv4 networks to manage and report memberships in IP multicast groups, enabling efficient delivery of multicast traffic to interested receivers.[1] IGMP allows hosts to notify adjacent routers of their interest in receiving traffic addressed to specific multicast group addresses, which routers use to determine which multicast streams to forward on local network segments.[2] IGMP has evolved through three main versions to address growing needs in multicast networking. Version 1 (IGMPv1), specified in RFC 1112 and published in 1989, introduced the basic query-response mechanism for hosts to join multicast groups, though it lacked explicit leave notifications and relied on timeouts for group departures.[2] IGMPv2, defined in RFC 2236 in 1997, improved upon this by adding explicit leave group messages to reduce unnecessary traffic and introducing querier election for better router coordination.[3] The current version, IGMPv3 (updated in RFC 9776 in 2025, obsoleting RFC 3376), enhances functionality with support for source-specific multicast (SSM) through INCLUDE and EXCLUDE filtering modes, allowing hosts to specify desired or blocked sources for a group, and maintains backward compatibility with prior versions.[1] In operation, IGMP relies on periodic membership queries sent by elected multicast routers (typically to the all-systems multicast address 224.0.0.1) to solicit reports from hosts, which respond with membership reports detailing their active groups and sources.[1] This process maintains per-interface state in routers, ensuring multicast traffic is only forwarded to segments with interested hosts, thereby optimizing bandwidth in applications like video streaming, online gaming, and resource discovery protocols.[1] IGMP works in conjunction with multicast routing protocols such as Protocol Independent Multicast (PIM) but is limited to the local network segment, with no provisions for authentication or encryption in its core specification.[1]

Introduction

Purpose and Functionality

The Internet Group Management Protocol (IGMP) is a communications protocol used by hosts and adjacent routers on IPv4 networks to establish and maintain multicast group memberships.[1] IGMP enables hosts to inform routers about their interest in receiving traffic destined for specific IP multicast addresses, allowing routers to forward multicast packets only to subnets with interested receivers rather than flooding the entire network.[2] This mechanism supports efficient one-to-many and many-to-many communications, conserving bandwidth in applications such as IPTV, online gaming, video conferencing, and collaborative tools where multiple recipients need simultaneous data delivery.[4][5] IGMP operates exclusively at the link-local scope, facilitating communications between hosts and routers on the same subnet without propagating messages across routers.[1] It is assigned IP protocol number 2 in the IPv4 header, positioning it at the network layer (OSI Layer 3) to manage multicast routing decisions. IGMP specifically handles memberships for IPv4 multicast addresses in the Class D range, from 224.0.0.0 to 239.255.255.255, which are reserved for group communications. Later versions, such as IGMPv3, extend support to source-specific multicast, allowing hosts to filter traffic from specific sources.[2] By limiting multicast traffic to interested parties, IGMP reduces network congestion and enhances scalability for real-time data distribution.[2]

Historical Development

The development of the Internet Group Management Protocol (IGMP) originated from early research on IP multicast at Stanford University in the mid-1980s, led by Steve Deering, who explored multicast routing mechanisms to enable efficient group communication in datagram internetworks. This work built on experiments with multicast addressing and routing in ARPANET environments during the late 1980s, aiming to extend IP capabilities beyond unicast for applications like distributed computing and video conferencing.[2] Deering's efforts culminated in the initial standardization of IGMP as part of the host extensions for IP multicasting, defined in RFC 1112 in August 1989, which introduced IGMPv1 to allow hosts to report multicast group memberships to adjacent routers.[2] Subsequent evolution addressed limitations in group management efficiency, with IGMPv2 specified in RFC 2236 in November 1997 by William C. Fenner, updating RFC 1112 to include mechanisms for faster group leave notifications and improved query handling.[3] This version emerged from the IETF's Inter-Domain Multicast Routing Working Group, reflecting growing needs for scalable multicast in expanding internetworks. By the mid-1990s, IGMP had seen widespread adoption in Unix-based systems, including BSD variants, integrating into kernel-level support for multicast applications and becoming a standard component of IP networking stacks.[3] Further advancements came with IGMPv3 in RFC 3376, published in October 2002 by a team including Deering and Fenner, which obsoleted RFC 2236 and added support for source-specific multicast to enable finer-grained control over multicast traffic.[1] This specification was refined in 2006 through RFC 4604 by Holbrook, Cain, and Haberman, which clarified IGMPv3 behaviors for source-specific multicast implementations, ensuring better interoperability in diverse network environments.[6] IGMPv3 was further updated in RFC 9776 in March 2025 to address errata and provide clarifications while maintaining backward compatibility.[1] IGMP's integration into IETF standards track documents solidified its role in IPv4 multicast, as focus shifted toward IPv6 equivalents like Multicast Listener Discovery (MLD).[7]

Architecture

Roles of Hosts and Routers

In the Internet Group Management Protocol (IGMP), hosts and routers play distinct roles in managing multicast group memberships on local networks. Hosts are responsible for reporting their interest in receiving multicast traffic for specific groups, while routers act as queriers to solicit and process these reports to determine which multicast traffic to forward onto the local segment.[2][3][1] Hosts initiate group membership by sending unsolicited membership reports upon joining a multicast group, announcing their interest to all routers on the local network; these reports are typically transmitted immediately and may be repeated 1-2 times with short intervals to ensure reception. When a router sends a query, hosts respond with membership reports after a random delay to prevent message implosion, suppressing their own report if they detect another host's report for the same group during the delay period. In IGMP versions 2 and later, hosts that are the last reporter for a group send a leave message upon departing to promptly notify routers, reducing unnecessary traffic forwarding. Hosts also maintain internal timers for report suppression and group membership states to optimize local communications.[2][3][1] Multicast routers, particularly the elected querier, periodically send general queries to all hosts on the attached network to discover and refresh group memberships, using the all-systems multicast address 224.0.0.1 with a time-to-live (TTL) of 1 to limit scope to the local link. The querier processes incoming reports to update its forwarding tables, enabling efficient multicast distribution based on active group interests. On local area networks (LANs) with multiple routers, a querier election occurs, where the router with the lowest IP address assumes the querier role, and others become non-queriers that passively listen for reports and queries without initiating them. Non-querier routers adjust their timers upon detecting a querier but do not send queries or leave messages. These roles operate in an all-senders-to-all-receivers model on shared LANs, where IGMP messages are link-local and processed by all participants.[2][3][1] IGMP employs several foundational timer mechanisms to manage membership states reliably: the Query Interval (QI) governs the periodicity of general queries from the querier; the Query Response Interval (QRI) sets the maximum time hosts wait before responding to queries; and the Group Membership Interval (GMI) defines the duration after which a router assumes a group has no members if no reports are received, typically derived as (Robustness Variable × QI) + QRI. These timers help mitigate packet loss and ensure timely updates to multicast forwarding.[3][1] The roles defined in IGMP integrate with multicast routing protocols such as Protocol Independent Multicast (PIM), where routers use IGMP reports to inform tree-building decisions for wider network distribution.[8]

Interaction with Other Protocols

IGMP operates as an integral component of the IPv4 multicast framework, with its messages encapsulated directly within IPv4 datagrams using the IP protocol number 2. This encapsulation ensures that IGMP communications are treated as a distinct protocol layer atop IP, facilitating the exchange of group membership information between hosts and routers on the same local network segment. Additionally, all IGMP messages are transmitted with an IP Time-to-Live (TTL) value of 1, restricting their scope to the local link and preventing unintended propagation beyond the immediate subnet.[9][1] IGMP integrates closely with multicast routing protocols by supplying edge-network information on host group memberships, enabling routers to construct and maintain efficient multicast distribution trees across the wider network. For instance, in Protocol Independent Multicast (PIM), IGMP reports inform routers about local receiver interests, allowing PIM to build shared or source-specific trees that direct traffic only to subnets with active members, thereby optimizing bandwidth usage. Similarly, the Distance Vector Multicast Routing Protocol (DVMRP) relies on IGMP queries and reports to track local group memberships, using this data to propagate route advertisements and prune unnecessary branches in the multicast forwarding tree.[1][10] At the Layer 2 level, IGMP interacts with switch mechanisms such as IGMP snooping, where Ethernet switches monitor IGMP messages to dynamically build port-based membership tables, forwarding multicast traffic only to ports associated with interested hosts rather than flooding all ports. This optimization reduces unnecessary traffic replication, conserves bandwidth, and mitigates the risk of broadcast storms in environments with high multicast activity.[11] For IPv6 networks, IGMP's functionality is mirrored by Multicast Listener Discovery (MLD), an ICMPv6-based protocol that performs analogous group membership reporting but uses distinct message types, such as Multicast Listener Query (type 130) and Report (type 131). MLD versions align with IGMP's evolution—MLDv1 corresponds to IGMPv2, while MLDv2 supports source-specific filtering akin to IGMPv3—ensuring consistent multicast behavior across IP versions without direct protocol-level interaction between IGMP and MLD.[12][13] While IGMP has no direct interaction with unicast protocols such as ICMP, its reliance on the IP layer provides indirect connectivity, as IGMP datagrams traverse the same IP infrastructure used for unicast traffic.[9]

Protocol Versions

IGMPv1

IGMPv1, the initial version of the Internet Group Management Protocol, was specified in 1989 to enable hosts to report their multicast group memberships to adjacent routers on IPv4 networks.[14] It operates using IP protocol number 2 and supports any-source multicast (ASM), where traffic from any source address can be received for a group without source-specific filtering.[14] Hosts join a multicast group by invoking a socket option and immediately transmitting a membership report to the group address, ensuring prompt inclusion in the forwarding state.[14] Routers maintain membership information through periodic general queries sent to the all-hosts address (224.0.0.1) with a TTL of 1, typically at intervals not exceeding 60 seconds to minimize overhead while refreshing group states.[14] The protocol defines only two message types in a fixed 8-byte format: Host Membership Query (type 1), which has a group address field set to zero for general queries, and Host Membership Report (type 2), which specifies the group address for which membership is being reported.[14] Each message includes a version field (set to 1), type, unused bits, checksum, and the 32-bit group address.[14] To prevent report implosion on shared networks, hosts delay their responses randomly between 0 and 10 seconds upon receiving a query, and suppress duplicate reports if they overhear another host's report for the same group.[14] Leaving a group occurs silently without an explicit message; hosts simply cease reporting, and routers infer departure from the absence of responses to subsequent queries.[14] A key limitation of IGMPv1 is the lack of group-specific queries, restricting routers to broadcasting general queries that solicit reports for all groups, which increases network traffic and delays detection of membership changes.[3] Without an explicit leave mechanism, leave detection relies on query timeouts, potentially delaying the pruning of forwarding state by up to 3 minutes as routers wait for non-responses over multiple query cycles.[3] This inefficiency, combined with no support for source-specific multicast, makes IGMPv1 unsuitable for modern bandwidth-sensitive applications.[15] For backward compatibility in mixed networks, subsequent versions like IGMPv2 and IGMPv3 default to IGMPv1 behavior when version 1 routers are detected, ensuring interoperability with legacy systems.[3] IGMPv1 is rarely used standalone today, though it is emulated in newer implementations for supporting legacy hosts.[16]

IGMPv2

IGMPv2, defined in RFC 2236 in November 1997, builds upon IGMPv1 by introducing mechanisms to optimize multicast group membership reporting and router processing in IPv4 networks. A primary enhancement is the addition of the Leave Group message (type 0x17), which permits hosts to promptly inform adjacent routers of their exit from a multicast group, thereby shortening the leave latency from up to three minutes in IGMPv1 to mere seconds. This immediate notification prevents unnecessary traffic forwarding to vacated hosts. IGMPv2 also supports group-specific queries, enabling routers to target inquiries to individual groups for more precise membership verification.[3] The protocol employs three core message types to manage group dynamics: Membership Query (type 0x11), which incorporates a Maximum Response Time field in hundredths of a second to stagger host responses and mitigate traffic bursts, along with the querier's IP address derived from the packet source; Version 2 Membership Report (type 0x16), used by hosts to affirm ongoing group interest; and Leave Group (type 0x17). Messages follow a variable-length format starting with an 8-octet header, and the protocol includes a configurable robustness variable—defaulting to 2—to retransmit queries in lossy environments, enhancing reliability without excessive overhead.[3] Operational efficiency is further improved through a deterministic querier election process, where the router with the lowest IP address on the subnet assumes the querier role upon detecting competing queries. For backward compatibility, IGMPv2 routers detect IGMPv1 hosts by parsing the distinct report format lacking the Maximum Response Time field and can revert to v1 behavior if needed. RFC 2236 formally obsoletes RFC 1112, the specification for IGMPv1, while preserving interoperability.[3] Despite these advances, IGMPv2 operates exclusively in an any-source multicast model, forwarding all sources to interested groups without provisions for source-specific filtering—a capability deferred to IGMPv3.[3]

IGMPv3

IGMPv3 introduces support for source-specific multicast (SSM), enabling hosts to report interest in multicast traffic from specific sources rather than all sources for a group. This is achieved through two filter modes in membership reports: INCLUDE, where hosts specify the desired sources from which they want to receive traffic for a group, and EXCLUDE, where hosts indicate sources to block while receiving from all others. These modes allow for more precise control over multicast reception, facilitating applications that require selective source filtering.[1] The protocol defines two primary message types: the Membership Query (type 0x11), which routers use to poll hosts and can include a source list to query specific source-group combinations, and the Membership Report (type 0x22), sent by hosts to convey their current state with records specifying the filter mode (INCLUDE or EXCLUDE) along with associated source addresses. These reports support multiple group records in a single message, enhancing efficiency in state reporting.[17][1] Key improvements in IGMPv3 include an extended default Query Interval of 125 seconds between general queries, reducing network overhead compared to prior versions. The protocol also incorporates updates from RFC 4604, which refine state diagrams, timers, and behaviors for SSM-aware routers and hosts to ensure consistent handling of source-specific joins and compatibility in mixed environments.[15][6] For backward compatibility, IGMPv3 routers maintain per-interface modes that negotiate down to IGMPv1 or v2 when older reports are detected, ensuring seamless operation in heterogeneous networks. All IGMPv3 membership reports are sent to the all-IGMPv3-routers address 224.0.0.22, which all version-capable devices monitor.[1][1] Adoption of IGMPv3 has been driven by its ability to enable bandwidth savings in multicast applications, such as video-on-demand, by allowing hosts to filter out unwanted sources and receive only relevant streams, thereby optimizing network resource utilization in scenarios with multiple content providers.[6]

Message Types and Formats

Common Message Structure

IGMP messages are encapsulated as payloads within IPv4 datagrams, using IP protocol number 2 to indicate the protocol.[18][9][19] The IPv4 header for these datagrams specifies a time-to-live (TTL) value of 1, ensuring the messages are processed only by the local network.[9][19] For query messages, the destination IP address is set to 224.0.0.1 (the all-hosts multicast address), while report messages use the multicast group address as the destination.[9][19] The core IGMP header, applicable to versions 1 and 2, consists of 8 octets with the following fixed fields: a 1-octet Type field indicating the message type; a 1-octet Max Resp Time (or Code in version 3) field specifying the maximum response time for queries; a 2-octet Checksum field for integrity verification; and a 4-octet Group Address field containing the multicast group address (set to 0.0.0.0 for general queries).[18][9]
FieldSize (octets)Description
Type1Identifies the IGMP message type (e.g., query or report).
Max Resp Time/Code1Maximum response time in 1/10-second units for queries; used for version detection.
Checksum216-bit one's complement checksum of the IGMP message.
Group Address4IPv4 multicast address of the group; zero for general queries.
The IGMP version is inferred from the Max Resp Time field in 8-octet messages: a value of 0 indicates version 1, while a non-zero value signifies version 2 or later.[9] For version 3 messages, the total length exceeds 8 octets, distinguishing it from prior versions.[19] The checksum is computed using the standard IP-style one's complement algorithm over the entire IGMP message, with the checksum field itself set to zero during calculation, as defined in RFC 1071.[18][9][19] In IGMP version 3, the message structure extends beyond the fixed 8-octet header to include variable-length fields, such as the number of sources (2 octets) followed by a list of source IP addresses (4 octets each) for source-specific operations, and in reports, a number of group records followed by per-group details including record type, auxiliary data length, source count, group address, source list, and optional auxiliary data.[19]

Query Messages

Query messages in the Internet Group Management Protocol (IGMP) are initiated by multicast routers, known as queriers, to poll hosts for their multicast group memberships on a local network. These messages enable routers to maintain accurate records of group subscriptions, ensuring efficient multicast traffic forwarding. In all versions of IGMP, queries are sent with an IP destination address of 224.0.0.1 (the all-systems multicast address) for general queries, and an IP time-to-live (TTL) value of 1 to limit scope to the local subnet.[2][3][1] In IGMPv1, the only query type is the General Query, which solicits reports from all groups on the subnet. Its structure consists of an 8-octet message with Type field set to 1, an Unused field (zeroed on transmission), a 16-bit Checksum, and a Group Address field (zeroed on transmission and ignored on reception). General Queries in IGMPv1 are sent periodically, no more frequently than once per minute, or in rapid succession during router startup to quickly ascertain memberships. Hosts receiving a valid General Query start a random delay timer between 0 and 10 seconds before responding, suppressing responses if another host reports first.[2] IGMPv2 introduces both General and Group-Specific Queries, expanding querier capabilities. The General Query, with Type 0x11 and Group Address 0, discovers all active groups, sent periodically at the Query Interval (default 125 seconds). The Group-Specific Query, with Type 0x11 and the target Group Address set, confirms lingering memberships after a host sends a Leave Group message, transmitted up to the Last Member Query Count (default equal to the Robustness Variable, typically 2) times at 1-second intervals. Both query types include a Max Resp Time field (default 10 seconds for General Queries), specifying the maximum host response delay in tenths of a second. The Querier's Robustness Variable (QRV, default 2) and Querier's Query Interval Code (QQIC, encoding the 125-second default) are conveyed in the unused octet of IGMPv1 queries but repurposed in IGMPv2 for robustness against packet loss and interval tuning. Response suppression occurs if a host hears a report for the queried group within the Max Resp Time, preventing redundant transmissions.[3] IGMPv3 builds on prior versions with three query variants: General, Group-Specific, and Group-and-Source-Specific, all using Type 0x11, as specified in RFC 9776 (2025), which obsoletes RFC 3376. The General Query (Group Address 0, Number of Sources (S) 0) polls for all group memberships, sent periodically at the Query Interval derived from QQIC (default 125 seconds). The Group-Specific Query (Group Address set, S=0) verifies members for a single group, typically after leave detection, with a shorter Max Resp Code (default 1 second). The Group-and-Source-Specific Query (Group Address set, S>0, followed by a Source Address list) checks reception from particular sources in INCLUDE mode filter states, used to confirm source-specific subscriptions. Unique to IGMPv3 queries, the Suppress Router Processing (S) flag, located in the octet following the Group Address, when set to 1 instructs receiving multicast routers to suppress their timer updates in response to the query, aiding compatibility in mixed-version environments. The QRV field (default 2 if zero) and QQIC field (default 125 seconds if zero) are explicitly included, with the Max Resp Code using linear scaling below 128 (in tenths of a second) and exponential above for longer delays up to about 53 minutes. Queries include an S field indicating the number of source addresses (0 for non-source-specific types), followed by the unicast Source Address list when S>0. Timing follows the querier's interval, with elected queriers (lowest IP address) sending queries; lower-IP queriers override others upon detection.[1]

Report and Leave Messages

In IGMP versions 1 and 2, hosts send Membership Report messages to inform routers of their interest in receiving traffic for specific multicast groups. The IGMPv1 Membership Report has a message type of 0x12 and consists of the type field, an unused field set to zero, a checksum, and the multicast group address.[2] These reports are sent either unicast to a specific router or multicast to the group address itself, with an IP TTL of 1.[2] Similarly, the IGMPv2 Membership Report uses type 0x16, includes the same fields plus a Max Response Time set to zero, and follows the same transmission rules.[3] Both versions limit the report to a single group address, without source-specific details.[3] IGMPv3 introduces a more flexible Membership Report structure with type 0x22, allowing multiple group records in a single message to support source-specific filtering.[1] Each group record includes a record type—such as MODE_IS_INCLUDE (value 1) for receiving traffic only from specified sources or MODE_IS_EXCLUDE (value 2) for receiving from all sources except those listed—an auxiliary data length (typically zero in standard IGMPv3), the number of sources (N), the multicast group address, and a source list of N unicast IP addresses.[1] These reports are sent multicast to the all-IGMPv3-routers address 224.0.0.22, enabling efficient batch reporting of include or exclude modes for multiple groups and sources.[1] IGMPv3 group records use the following record types:
  • MODE_IS_INCLUDE (1): Current state is INCLUDE mode; the interface receives traffic only from the listed sources.
  • MODE_IS_EXCLUDE (2): Current state is EXCLUDE mode; the interface receives traffic from all sources except those listed.
  • CHANGE_TO_INCLUDE_MODE (3, TO_IN): The filter mode has changed to INCLUDE; the source list specifies the new desired sources. Commonly used when switching to source-specific multicast (SSM) or signaling a leave by using an empty list (TO_IN {}).
  • CHANGE_TO_EXCLUDE_MODE (4, TO_EX): The filter mode has changed to EXCLUDE; the source list specifies sources to exclude. Often used for standard group joins in any-source multicast (ASM) with an empty source list (TO_EX {}), equivalent to a general join.
  • ALLOW_NEW_SOURCES (5): Adds new sources to the existing include list (sent in state-change reports).
  • BLOCK_OLD_SOURCES (6): Removes sources from the include list or adds to exclude (sent in state-change reports).
The key difference between TO_IN and TO_EX lies in the target filter mode: TO_IN transitions to INCLUDE mode (receive only from listed sources), while TO_EX transitions to EXCLUDE mode (receive from all except listed). In practice, TO_EX with empty list is the common "join" for any-source groups, while TO_IN is used for precise source selection or explicit leaves.[15] Leave Group messages, introduced in IGMPv2 and later, allow hosts to explicitly notify routers when ceasing interest in a group, reducing leave latency compared to implicit timeouts. The message type is 0x17, with fields mirroring the v2 report: type, Max Response Time (zero), checksum, and group address.[3] It is sent multicast to the all-routers address 224.0.0.2, prompting the querier to issue a group-specific query to confirm if other hosts remain interested.[3] IGMPv3 does not use a separate Leave Group message; instead, hosts signal departure by sending a Membership Report with a TO_IN record (type 3) containing an empty source list for the group, effectively transitioning to no membership.[1] IGMPv1 lacks any leave mechanism, relying solely on query timeouts for implicit group expiration.[2] To prevent network congestion from duplicate reports, IGMP implements suppression mechanisms across versions. In response to a query, hosts schedule reports with a random delay between 0 and the query's Max Response Time; if a report for the same group is overheard during this period, the host cancels its transmission.[3] This applies to both v1/v2 simple reports and v3 records, though v3 extends suppression to source-specific states for finer control.[1]

Operational Mechanisms

Group Membership Management

In IGMP, hosts manage their multicast group memberships through a series of processes that allow them to join, maintain, and leave groups dynamically. When a host wishes to join a multicast group, it immediately sends an unsolicited Membership Report message to the group address, notifying the local multicast router of its interest. To prevent network congestion from multiple hosts sending simultaneous reports, the host implements a suppression mechanism: upon receiving a report from another host for the same group, it cancels its own transmission if the timer has not yet expired. This process applies across IGMP versions, with variations in report repetition; for instance, in IGMPv1, reports are sent 1 to 3 times with random delays of 0 to 10 seconds, while in IGMPv2 and IGMPv3, they are retransmitted up to 1 or 2 times at intervals of 10 seconds or 1 second, respectively.[2][3][1] Maintaining group membership involves periodic reporting in response to router queries, ensuring the router's knowledge of active listeners remains current. Hosts track their memberships internally in a host group table, which maintains an entry per interface for each group, including associated source lists and expiry timers. Upon receiving a query, the host schedules a response report after a random delay (typically 0 to 10 seconds) and suppresses it if another host's report for the same group is heard first. The membership state expires after the Group Membership Interval (GMI), a timer set to 260 seconds in IGMPv3, during which no reports are sent for the group; this timeout mechanism confirms the host's continued interest.[2][3][1] Leaving a group differs by version to balance efficiency and confirmation. In IGMPv1, departure is timeout-based: the host simply stops sending reports, and the router detects inactivity after the GMI duration without further reports for the group. IGMPv2 introduces an explicit Leave Group message sent by the host to the all-routers multicast address (224.0.0.2) if it was the last reporter, prompting the router to issue group-specific queries for confirmation over a short interval (default 1 second, repeated up to 2 times). In IGMPv3, leaving involves sending a state-change report with a Filter-Mode-Change record, such as transitioning to an INCLUDE mode with an empty source list, allowing precise adjustments without full group removal.[2][3][1] IGMPv3 enhances membership management with source-specific filtering through two modes: INCLUDE, where the host receives traffic only from explicitly listed sources, and EXCLUDE, where it receives traffic from all sources except those listed. These modes are maintained in the host group table alongside timers for source records, which expire if not refreshed. State transitions between modes or source list changes follow defined rules; for example, switching from INCLUDE({A}) to EXCLUDE({B}) generates a TO_EX record for the new excluded sources and an ALLOW_NEW record for previously included ones, ensuring minimal disruption. The host reports these changes immediately via unsolicited reports to update the router promptly.[1]

Query and Response Processes

The query and response processes in the Internet Group Management Protocol (IGMP) form the core mechanism by which multicast routers discover and maintain host memberships in IP multicast groups on attached local networks, ensuring efficient traffic forwarding only to interested receivers. A designated querier router initiates this cycle by periodically transmitting general query messages to the all-systems multicast address (224.0.0.1), prompting hosts to report their active group subscriptions within a specified response window; this periodic solicitation, typically occurring every 125 seconds in IGMPv2 and IGMPv3, allows routers to refresh their state tables and prune inactive groups. Hosts respond with membership reports, which routers use to update forwarding decisions, starting traffic delivery upon receiving reports and ceasing it after timeouts if no further interest is indicated.[3][1] In IGMPv1, the process is rudimentary, with the querier sending general queries no more frequently than once per minute to solicit reports from hosts, which delay responses randomly between 0 and 10 seconds per group to minimize collisions; upon hearing a report for a group from another host, a host cancels its own pending transmission for that group. This version lacks explicit querier election or leave signaling, relying solely on the absence of reports to infer group inactivity.[14] IGMPv2 refines the cycle by standardizing the query interval at 125 seconds (Query Interval, or QI) and the maximum response delay at 10 seconds (Query Response Interval, or QRI), during which hosts schedule reports for each joined group with uniform random delays; if a host detects a report for the same group before its timer expires, it suppresses its own to reduce network load. For group departures, the querier issues group-specific queries at 1-second intervals (Last Member Query Interval, or LMQI, defaulting to 1 second for up to 2 queries) upon receiving a leave message, confirming no remaining members before pruning; querier election on multi-router networks favors the router with the lowest IP address, with others monitoring via an Other Querier Present timer (approximately 255 seconds) and assuming the role if queries cease. No responses to general queries within the group membership interval (GMI, default 260 seconds) trigger group state expiration, halting forwarding.[20][21] IGMPv3 extends these mechanisms to support source-specific multicast (SSM) by introducing source-list queries, where the querier sends group-and-source-specific queries to validate host interest in particular sources for a group, enabling precise filtering in SSM deployments; general queries retain the 125-second QI and 10-second QRI defaults, but responses may include INCLUDE or EXCLUDE filter modes with associated source lists. In EXCLUDE mode, the block state for unwanted sources times out after the GMI (260 seconds), transitioning to INCLUDE if no confirming reports arrive, while robustness retries (governed by a default robustness variable of 2) multiply timer values to tolerate packet loss in reports. Querier election mirrors IGMPv2, using the lowest IP address, with non-queriers taking over after the Other-Querier-Present timer (approximately 250 seconds) expires.[22][23]

Security Considerations

Vulnerabilities and Attacks

The Internet Group Management Protocol (IGMP) is inherently vulnerable to various attacks due to its lack of built-in authentication and reliance on unverified IP-level protections, allowing unauthorized manipulation of multicast group memberships.[24] This absence of cryptographic mechanisms means that any device on a local network can send forged messages, potentially disrupting multicast operations across IGMP versions 2 and 3.[25] Such weaknesses expose networks to risks particularly in unsecured environments like wireless or shared media, where message interception and injection are feasible.[26] Denial-of-service (DoS) attacks represent a primary threat, where attackers flood routers with fake IGMP reports or leave messages to overload state tables and force excessive processing. For instance, spoofed membership reports can mislead routers into maintaining unnecessary group states, consuming memory and CPU resources on the device.[27] In IGMPv3, forged group-and-source-specific queries with large source lists and short response times can overwhelm hosts, triggering massive report generation that clogs network bandwidth.[28] Similarly, in IGMPv2, repeated forged leave messages provoke group-specific queries, amplifying traffic without altering core protocol behavior.[25] A specific implementation vulnerability in Cisco IOS Software's IGMPv3 handling has been noted to cause device crashes under sustained message floods, highlighting real-world DoS impacts.[29] Spoofing attacks enable malicious hosts to impersonate legitimate queriers or members by forging source IP addresses in IGMP messages, thereby hijacking control of multicast sessions. An attacker can send a query with a lower IP address than the current querier, assuming the querier role and potentially directing traffic to non-existent groups for up to the group membership interval.[28] This allows injection of false membership reports, tricking routers into forwarding multicast traffic to unauthorized recipients and enabling traffic interception in unsecured networks.[25] Group hijacking occurs when spoofed reports lead to unauthorized joins, diverting sensitive multicast streams to attacker-controlled interfaces, especially in environments without source verification.[26] Amplification risks arise from IGMP's query-response mechanism, where a small query can elicit disproportionately large responses from multiple hosts, magnifying attack traffic toward a spoofed victim. Studies have identified networks with up to 305,000 responders capable of 2.4x median amplification, with extreme cases reaching over 40,000x, allowing low-bandwidth attackers to saturate gigabit links.[26] For example, spoofing a victim's address in an Ask Neighbors query (a legacy DVMRP message type, such as type 5, encapsulated in IGMP) directs amplified neighbor reports back to the victim, evading detection.[26] Historical incidents involving IGMP exploits are rare but have been documented in multicast deployments, often as sustained DoS streams from anomalous query floods in shared media networks. Anecdotal reports from early 2010s deployments note attackers leveraging IGMP loops via repeated spoofed queries between misconfigured routers, consuming resources indefinitely.[26] These events underscore exacerbated risks in wireless setups, where signal range facilitates easier message injection without physical access controls.[26]

Mitigation Strategies

To mitigate vulnerabilities in IGMP deployments, such as unauthorized group joins or query spoofing, network administrators can implement access controls using Access Control Lists (ACLs) on routers to validate multicast group membership requests. For instance, extended ACLs can filter IGMPv3 reports by permitting or denying specific source-group (S,G) pairs, ensuring only authorized joins are processed and preventing illicit traffic forwarding.[30] Additionally, limiting querier sources to trusted interfaces via ACLs restricts the election of malicious queriers, reducing the risk of traffic redirection or denial-of-service from forged queries.[31] Rate limiting serves as an effective defense against IGMP floods, where excessive messages could overwhelm network resources. Throttling IGMP messages per host or port, such as configuring limits on the number of joins or reports processed within a time interval, prevents amplification attacks while maintaining legitimate multicast operations.[32] Implementing query and response caps on routers further caps the volume of periodic queries, mitigating potential denial-of-service by ensuring bounded processing loads.[33] Enabling IGMP snooping on Layer 2 switches enhances security by authenticating and filtering multicast traffic, forwarding reports only to designated router ports and discarding packets with invalid checksums to block forged messages. When combined with authentication mechanisms, such as validating report sources against known hosts, snooping prevents unauthorized access to groups. IGMP proxying at network edges provides further filtering by aggregating and validating reports before upstream propagation, reducing exposure to external threats.[34] IPsec can be used to authenticate IGMP messages, providing protection against forgery and spoofing. The Authentication Header (AH) protocol in IPsec mode allows verification of message origin and integrity, though it requires key management and may disable replay protection in symmetric key setups on local networks.[24][35] For environments transitioning to IPv6, shifting to Multicast Listener Discovery (MLD) is recommended over IGMP, as MLD integrates with ICMPv6's built-in security features like neighbor discovery protections, offering better resistance to spoofing and denial-of-service compared to IGMP's standalone operation.[36] Deploying monitoring tools is essential for detecting anomalies in IGMP traffic, such as unusual report volumes indicating spoofing attempts. Logging anomalous reports on routers and integrating with Intrusion Detection Systems (IDS) enables real-time spoof detection by analyzing packet patterns against baseline behaviors.[37] Adhering to standards like RFC 4604 for IGMPv3 provides foundational guidance, including errata recommendations to ignore non-source-specific requests on SSM addresses to avoid compatibility mode reversions that could enable denial-of-service. Vendor hardening practices, such as disabling IGMP on unneeded interfaces to minimize attack surfaces, further bolster security.[6][38]

Implementations and Deployment

Operating System Support

Linux provides full support for IGMP version 3 (v3) since the kernel 2.6 series, released in 2003, enabling advanced source-specific multicast features for hosts and routers.[39] Tools such as smcroute facilitate static multicast routing by manipulating the kernel's multicast forwarding cache, integrating seamlessly with IGMP for IPv4 multicast traffic management.[40] Configuration options, including IGMP timers and version preferences, are accessible through the /proc/sys/net/ipv4/conf interface, allowing administrators to tune parameters like query response intervals via sysctl commands.[41] Windows operating systems offer native IGMPv3 support starting with Windows XP and Windows Server 2003, with subsequent versions like Windows Vista and later maintaining full compatibility for multicast group management.[42] Management is performed using netsh interface ipv4 commands, such as netsh interface ipv4 set interface "Local Area Connection" igmpversion=3, to configure version settings and join/leave groups.[43] Older versions, including Windows 2000, are limited to IGMPv2, lacking source filtering capabilities.[42] BSD-derived systems like FreeBSD support IGMPv3 since version 7.0 in 2007, while macOS added kernel support starting with OS X Lion (10.7) in 2011, building on its Darwin kernel foundation and providing robust host-side multicast operations.[44][45] In FreeBSD, integration with the ipfw firewall allows fine-grained control over IGMP messages, such as filtering queries or reports via rules like "add 10000 allow igmp from any to any".[46] macOS similarly leverages these BSD roots for seamless IGMP handling in applications requiring multicast, though configuration remains primarily kernel-level. Mobile operating systems exhibit partial IGMP support focused on application-level multicast joining. Android and iOS enable developers to join multicast groups using socket options like IP_ADD_MEMBERSHIP via setsockopt, as defined in POSIX standards, allowing apps to receive IGMP-managed traffic without kernel-level querier functionality.[47] These platforms do not implement full querier roles, relying on network routers for query generation, which suits their host-oriented design. Configuration in these systems often involves socket APIs for dynamic group membership; for example, code snippets using setsockopt with level IPPROTO_IP and option IP_ADD_MEMBERSHIP permit hosts to report interest in multicast addresses, triggering IGMP reports to routers.[43] Kernel parameters, such as those under net.inet.igmp in BSD-derived systems or sysctl equivalents in Linux, adjust timers like the querier interval (default 125 seconds in IGMPv3) to optimize network efficiency.[48] As of 2025, IGMPv3 serves as the universal default across modern kernels in Linux, Windows, and BSD systems, with IGMPv1 fully deprecated due to its lack of leave messages and source filtering, ensuring compatibility with contemporary multicast deployments.[41]

Network Device Integration

In routers, Protocol Independent Multicast (PIM)-enabled devices, such as those running Cisco IOS, function as IGMP queriers to periodically poll hosts for multicast group memberships, ensuring efficient traffic distribution.[49] These routers support IGMP version 3 (IGMPv3) Source-Specific Multicast (SSM) features, utilizing multicast routing (mroute) tables to track source-group pairs and forward traffic selectively.[50] Configuration typically involves enabling IGMPv3 on interfaces with commands like "ip igmp version 3" to align with SSM requirements.[51] Layer 2 switches implement IGMP snooping to optimize multicast forwarding by eavesdropping on IGMP messages and constructing port-to-group mapping tables, thereby preventing unnecessary flooding across all ports.[52] In devices like the Juniper EX series, this feature builds and maintains these maps dynamically, supporting both IGMPv2 and IGMPv3.[53] Fast-leave options, available for IGMPv2 and later, enable immediate removal of a port from a group upon receiving a leave message, which is particularly useful in single-host scenarios to reduce latency in group changes.[54] Network appliances such as firewalls and load balancers often proxy IGMP messages to facilitate secure multicast traversal across zones or segments without exposing internal hosts directly.[55] For instance, Cisco Secure Firewall Threat Defense (FTD) operates in stub multicast routing mode as an IGMP proxy, forwarding membership reports between upstream and downstream interfaces while adhering to RFC 4605.[55] These appliances also perform VLAN-aware processing, inspecting IGMP packets within specific VLAN contexts to enforce policies and maintain isolation. Scalability challenges arise in large subnets supporting thousands of multicast groups, where extensive state tracking for IGMP memberships can strain device resources.[56] This tracking imposes notable CPU overhead, as routers and switches must process frequent queries and updates, potentially leading to performance degradation in high-density environments without optimizations like snooping or hierarchical routing.[57] As of 2025, vendor trends emphasize embedding IGMPv3 support directly into Software-Defined Networking (SDN) controllers for centralized management of multicast policies.[58] Additionally, integration with Ethernet VPN (EVPN) fabrics in data centers enables efficient IGMP snooping and proxying over VXLAN overlays, supporting optimized inter-subnet multicast (OISM) for scalable IPv4 traffic.[59][60] Testing IGMP implementations in network devices often involves tools like mrouted, which simulates multicast routing and IGMP interactions in controlled environments to validate querier behavior and group joins.[61] Compliance testing focuses on standards such as RFC 4604, ensuring SSM-aware handling of IGMPv3 messages without modifications to core protocol mechanics.[6]

References

  1. RFC 9776 - Internet Group Management Protocol, Version 3
  2. RFC 1112: Host extensions for IP multicasting
  3. RFC 2236 - Internet Group Management Protocol, Version 2
  4. What is IGMP? | Internet Group Management Protocol - Cloudflare
  5. Internet Group Management Protocol (IGMP) - HPE Aruba Networking
  6. RFC 4604 - Using Internet Group Management Protocol Version 3 ...
  7. RFC 2710 - Multicast Listener Discovery (MLD) for IPv6
  8. RFC 3973 - Protocol Independent Multicast - Dense Mode (PIM-DM)
  9. RFC 2236: Internet Group Management Protocol, Version 2
  10. RFC 1075: Distance Vector Multicast Routing Protocol
  11. RFC 4541 - Considerations for Internet Group Management Protocol ...
  12. RFC 2710: Multicast Listener Discovery (MLD) for IPv6
  13. https://datatracker.ietf.org/doc/html/rfc9777
  14. RFC 1112 Host Extensions for IP Multicasting August 1989
  15. RFC 3376: Internet Group Management Protocol, Version 3
  16. Host Extensions for IP Multicasting and "Any Source Multicasting" (ASM) IP service
  17. Internet Group Management Protocol (IGMP) Type Numbers
  18. RFC 1112: Host extensions for IP multicasting
  19. https://www.rfc-editor.org/rfc/rfc9776.html
  20. https://datatracker.ietf.org/doc/html/rfc2236#section-3
  21. https://datatracker.ietf.org/doc/html/rfc2236#section-8
  22. https://datatracker.ietf.org/doc/html/rfc9776#section-6
  23. https://datatracker.ietf.org/doc/html/rfc9776#section-8
  24. https://datatracker.ietf.org/doc/html/rfc9776#section-9
  25. https://datatracker.ietf.org/doc/html/rfc2236#section-10
  26. On the Potential Abuse of IGMP - ACM Digital Library
  27. https://datatracker.ietf.org/doc/html/rfc9776#section-9.2
  28. https://datatracker.ietf.org/doc/html/rfc9776#section-9.1
  29. Cisco IOS Software Internet Group Management Protocol Denial of ...
  30. IP Multicast: IGMP Configuration Guide, Cisco IOS Release 15SY
  31. Secure IP Multicast Deployments - Cisco
  32. Multicast Design Best Practices | OrhanErgun.net Blog
  33. [PDF] IP Multicast Optimization: IGMP State Limit - Cisco
  34. RFC 4605 - Multicast Listener Discovery (MLD) - IETF Datatracker
  35. https://datatracker.ietf.org/doc/html/rfc4302
  36. Understanding MLD Snooping | Junos OS - Juniper Networks
  37. Monitoring IGMP Snooping | Junos OS - Juniper Networks
  38. IGMP - Palo Alto Networks
  39. https://sourceware.org/bugzilla/show_bug.cgi?id=5
  40. troglobit/smcroute: Static multicast routing for UNIX - GitHub
  41. IP Sysctl - The Linux Kernel documentation
  42. Microsoft Windows IGMPv3 and MLDv2 processing vulnerability
  43. MLD and IGMP Using Windows Sockets - Win32 apps
  44. sourcefilter(3) - FreeBSD Manual Pages
  45. https://trac.videolan.org/vlc/ticket/6524
  46. https://man.freebsd.org/cgi/man.cgi?query=ipfw
  47. Is android support IGMP url to play video - Stack Overflow
  48. igmp - FreeBSD Manual Pages
  49. IP Multicast: IGMP Configuration Guide - Cisco
  50. IP Multicast Routing Configuration Guide, Cisco IOS XE Cupertino ...
  51. [PDF] IGMP Configuration Guide, Cisco IOS XE Amsterdam 17.1.x
  52. IGMP Snooping Overview | Junos OS - Juniper Networks
  53. Example: Configuring IGMP Snooping on EX Series Switches
  54. immediate-leave - Junos CLI Reference - Juniper Networks
  55. Cisco Secure Firewall Management Center Device Configuration ...
  56. [PDF] Scaling IP Multicast on Datacenter Topologies - Princeton SNS Group
  57. IP Multicast Technology Overview - Cisco
  58. Cloud Networking Webinars - Arista
  59. Overview of Multicast Forwarding with IGMP Snooping or MLD ...
  60. https://apps.juniper.net/feature-explorer/feature/8365?fn=OISM%20with%20IGMPv2%2C%20IGMPv3%2C%20and%20IGMP%20snooping%20for%20IPv4%20multicast%20traffic%20in%20EVPNVXLAN%20fabrics
  61. troglobit/mrouted: The original DVMRP (dynamic multicast routing ...
User Avatar
No comments yet.