IGMP (Internet Group Management Protocol) is the IPv4 protocol that devices use to signal which multicast groups they want to receive. Without IGMP, a router delivering multicast traffic would have no way to know which hosts on a subnet are interested in a given stream — it would have to flood multicast everywhere or drop it entirely.
Where IGMP fits
Multicast is one-to-many traffic. Instead of the source sending a separate copy to every recipient (unicast) or to every device on the network (broadcast), it transmits once to a multicast group address. Devices that want the stream join that group via IGMP. Routers use IGMP membership reports to decide which multicast streams to forward onto each subnet.
| Term | Meaning | Example |
|---|---|---|
| Multicast group | Shared destination address (224.0.0.0–239.255.255.255) | IPTV channel stream |
| IGMP report | Host announces it wants a group | Set-top box tunes to a channel |
| IGMP leave | Host announces it no longer wants a group | Viewer changes channel |
| IGMP query | Router asks which groups hosts want | Periodic membership refresh |
| IGMP snooping | Switch learns per-port group membership | Stops flooding every port |
IGMP versions
IGMPv1 (1989) introduced the basic join mechanism. There was no explicit leave — the router had to wait for a membership query timeout to detect that a host had left, causing streams to linger for up to three minutes after the last member departed. IGMPv2 (1997) added an explicit Leave Group message, reducing leave latency to seconds. It also introduced the concept of a designated querier on each subnet. IGMPv3 (2002) added source-specific multicast (SSM) — a host can now specify not just which group it wants but which source it wants the traffic from (INCLUDE or EXCLUDE source filters). This is important for IPTV deployments where multiple providers might use the same group addresses with different source IPs. Most home routers support IGMPv2 and v3; IGMPv3 is required for full SSM support.
IPTV and IGMP in practice
IPTV is the most common reason home users encounter IGMP. An ISP delivers dozens or hundreds of TV channels as multicast streams into its access network. Each channel has a unique multicast group address. When a set-top box tunes to a channel, it sends an IGMPv2 or v3 membership report for that group. The home router (or ISP gateway) passes this upstream, and the ISP's multicast routing infrastructure adds that stream to the customer's access port. When the viewer changes channel, the set-top box sends an IGMP Leave for the old group and a membership report for the new one — the channel change speed depends in part on how quickly IGMP processes this handoff.
IGMP snooping
By default, a Layer 2 switch treats multicast traffic like broadcast — it floods every frame to every port. On a busy IPTV network with many HD streams, this can consume significant bandwidth on ports that have no interested devices. IGMP snooping solves this: the switch inspects IGMP messages passing through it and builds a multicast forwarding table mapping group addresses to specific ports. Multicast is then delivered only to ports that sent a membership report for that group. IGMP snooping must be enabled globally and on the relevant VLAN to take effect. Disabling it — or using an unmanaged switch that cannot snoop — causes all multicast to flood all ports, which can saturate Wi-Fi and degrade performance for other devices.
IGMP querier
On each subnet, one device acts as the IGMP querier — it periodically sends General Membership Query messages to 224.0.0.1 (all-hosts multicast), prompting all hosts to report their current group memberships. This keeps the router's multicast forwarding state current. In a home network with a single router, the router is always the querier. In more complex setups with multiple routers, IGMPv2 and v3 include an election process where the router with the lowest IP address becomes the querier.
IGMP vs MLD (IPv6)
IGMP only operates with IPv4. IPv6 replaces it with MLD (Multicast Listener Discovery), which is part of ICMPv6. MLD v1 corresponds roughly to IGMPv2; MLDv2 adds source-specific multicast equivalent to IGMPv3. The concepts are identical — hosts signal group membership to routers — but the packet format and addresses differ. On dual-stack networks, IGMP and MLD run in parallel for their respective address families.
Common IGMP problems
The most frequent issue is multicast flooding when IGMP snooping is disabled or unsupported on a switch in the path. Symptoms include all wired ports receiving the full IPTV multicast load even when no device on that port is watching TV, degrading LAN performance. A second common issue is IGMP proxy misconfiguration on the home router — the router must pass membership reports from the LAN toward the ISP and forward the resulting multicast streams back into the LAN. If the proxy is disabled or pointing at the wrong interface, IPTV streams arrive at the router but are never forwarded to the set-top box. Managed switches also require IGMP snooping to be enabled per-VLAN, not just globally — a common oversight in VLAN-segmented home networks.
Frequently Asked Questions
What does IGMP stand for?
IGMP stands for Internet Group Management Protocol.
What is IGMP used for?
It lets IPv4 devices join and leave multicast groups, especially for IPTV and local one-to-many traffic.
Should I enable IGMP snooping?
Usually yes on managed switches when multicast traffic exists. It keeps multicast from flooding ports that did not request it.