How IGMP snooping works
IGMP snooping is a feature of managed Ethernet switches that limits where multicast traffic goes. A plain switch treats a multicast frame much like a broadcast and sends it out of every port in the VLAN. With snooping enabled, the switch reads the IGMP messages passing through it, builds a table of which ports have a receiver for each multicast group, and forwards each stream only to those ports plus the port towards the multicast router or querier.
The name describes the trick. IGMP is a Layer 3 protocol between hosts and routers, and a Layer 2 switch would normally pass it along without looking. A snooping switch inspects those packets anyway, which is a layer violation by design. The IETF documented how switches should do it in RFC 4541.
The result is that a camera stream, a clock signal or a process data feed reaches the devices that asked for it and nothing else. Links to devices that never joined the group stay free, and small devices such as PLCs and remote I/O are not forced to receive and discard traffic they cannot use.
What is IGMP?
IGMP, the Internet Group Management Protocol, is how an IPv4 host tells the network which multicast groups it wants to receive. Multicast addresses run from 224.0.0.0 to 239.255.255.255, and a group is simply one of those addresses. One sender transmits a single stream to the group address, and the network copies it to every member, which uses far less bandwidth than sending a separate unicast stream to each receiver.
Hosts send a membership report to join a group. A router or switch acting as the querier sends a general query at regular intervals, by default every 125 seconds, and hosts that still want the group answer. If nobody answers for around 260 seconds, the membership times out. IPv6 does the same job with Multicast Listener Discovery (MLD), so the IPv6 version of this feature is MLD snooping.
| Version | Defined in | What it added | Typical use today |
|---|---|---|---|
| IGMPv1 | RFC 1112 (1989) | Queries and membership reports; leaving is by timeout only | Legacy devices |
| IGMPv2 | RFC 2236 (1997) | Leave message, querier election, group-specific queries | Most industrial and video devices |
| IGMPv3 | RFC 3376 (2002) | Source filtering, so a host can ask for a group from named senders only | Source-specific multicast, newer IP video |
| MLDv1 / MLDv2 | RFC 2710 / RFC 3810 | IPv6 equivalents of IGMPv2 and IGMPv3 | IPv6 networks |
Why a network needs an IGMP querier
Snooping only works while the switch keeps hearing IGMP traffic. Hosts often send a report only when they first join, so without regular queries the switch’s table ages out. Depending on the switch, the stream then either floods every port again or stops reaching receivers that still want it. Either way the symptom looks like an intermittent fault.
On a routed network the multicast router is the querier. On an isolated plant or camera network with no router, enable the IGMP querier function on one managed switch in each VLAN. If several switches are set as queriers, IGMPv2 and IGMPv3 elect the one with the lowest IP address, so the result is predictable. Our explainer on Layer 3 switches vs routers covers which device usually takes the router role.
Where IGMP snooping matters in industrial systems
Multicast is common on plant and security networks, often without anyone choosing it. These are the usual sources.
-
//
IP cameras and video walls. Cameras can send one multicast stream that a recorder, an analytics server and a video wall all join. Without snooping, every stream reaches every port, and a few HD cameras can fill a 100 Mb/s link to a device that never asked for video. Whether a recorder joins a multicast stream or pulls its own unicast copy depends on the camera and recording software, so check both before choosing industrial NVRs and switches.
-
//
EtherNet/IP implicit I/O. Producer and consumer connections in EtherNet/IP often use multicast UDP. Guidance for EtherNet/IP networks generally recommends IGMP snooping with a querier, so scanners and adapters are not flooded with I/O data meant for other devices.
-
//
Precision time. IEEE 1588 PTP sends its timing messages to multicast addresses, so snooping and querier settings must let them through. Our white paper on synchronizing machine vision with IEEE 1588 PTP explains why that timing matters.
-
//
Broadcast audio and media over IP. Paging, public address and studio video over IP rely on multicast and assume snooping is on.
Setting up IGMP snooping
Most of our industrial PoE switches with management list IGMP snooping, and some state the number of multicast groups supported, for example 1,024, or add MLD snooping for IPv6. A few settings decide whether it behaves well:
-
//
Enable it on every switch in the path. One unmanaged or non-snooping switch in the middle floods every stream it receives.
-
//
Set one querier per VLAN. Use the router if there is one, or a core managed switch if there is not.
-
//
Decide what happens to unknown multicast. Many switches can drop multicast for groups nobody has joined instead of flooding it, which protects small devices.
-
//
Use fast leave on single-host ports. Immediate leave stops a stream as soon as a camera viewer or HMI leaves, rather than after a query cycle.
Quick answers on IGMP snooping
IGMP snooping: common questions
Should IGMP snooping be on or off?
On, wherever multicast is used. It is safe to enable on managed switches and stops multicast flooding. Make sure the VLAN has a querier, or streams can stop when the table ages out.
What happens if IGMP snooping is not enabled?
Multicast is flooded. Every port in the VLAN receives every multicast stream, which wastes bandwidth and can overload small devices such as PLCs, I/O modules and thin clients.
What is an IGMP querier?
The device that keeps group membership up to date. It sends periodic queries so hosts re-confirm their groups. It is usually a router or a Layer 3 switch, or a managed switch with the querier function enabled.
What is IGMP proxying?
A router feature, not a switch feature. An IGMP proxy forwards joins from a downstream network to an upstream one, common on broadband routers for IPTV. Snooping happens inside one switched network.
Does IGMP snooping work with IPv6?
No, IPv6 uses MLD snooping. Multicast Listener Discovery replaces IGMP in IPv6, and many managed switches support IGMP and MLD snooping side by side.
We supply managed switches with our camera, vision and control systems, and as standard we set up IGMP snooping, the querier and VLANs to match the multicast traffic before the system ships.