On this page
1. Introduction: Beyond Unicast and Broadcast
As a network engineer, you live by a creed of efficiency. So, imagine being asked to stream a live All-Hands meeting to 500 employees.
Using unicast, your source server must generate and manage 500 separate IP streams. The server load would be immense, and your network links would groan under the weight of redundant traffic.
What about broadcast? You'd flood the entire network segment, interrupting every device, whether it's an employee's laptop or a server in the data center. It's the equivalent of using a bullhorn for a private conversation.
This is the problem domain where IP Multicast becomes indispensable. Multicast is an elegant one-to-many communication model built on the concept of a subscription. Think of it like a radio broadcast: the station transmits a single signal, and only the radios tuned to that specific frequency will play the audio. The broadcast tower doesn't care if 10 people or 10 million are listening.
This guide will deconstruct IP multicast from theory to terminal, covering the foundational addressing, host-to-router signaling with IGMP, the core routing logic of PIM, and the practical commands you'll use to build and debug it.
2. The Foundations: Addressing and the IGMP Subscription Model
Before we can route multicast traffic, we need to understand how groups are identified and how hosts subscribe to them on the local network.
Multicast Addressing: Layer 3 and Layer 2
At Layer 3, multicast uses the Class D IPv4 address range: 224.0.0.0 to 239.255.255.255. This range is further subdivided into well-defined blocks:
- Link-Local Addresses (
224.0.0.0/24): This block is reserved for network protocols operating on a local segment and is never forwarded by routers. You'll see these used by routing protocols like OSPF (224.0.0.5) and for the "all-hosts" address (224.0.0.1). - Source-Specific Multicast (SSM) Range (
232.0.0.0/8): This large block is specifically designated for SSM applications, where the receiver specifies both the multicast group and the source address to join. - Administratively Scoped Addresses (
239.0.0.0/8): Think of this as the RFC 1918 equivalent for multicast. This address space is intended for private use within an organization and should not be routed on the public internet.
At Layer 2, an IP multicast address is mapped to a specific Ethernet MAC address. The IANA-reserved prefix 01:00:5E is combined with the last 23 bits of the multicast IP address. For example, 239.1.1.1 becomes 01:00:5E:01:01:01.
⚠️ Key Detail: Because the first four bits of a Class D address are 1110 and the mapping only uses the last 23 bits, 5 bits of the IP address are ignored. This creates a 32:1 ambiguity where 32 different IP multicast groups can map to the exact same MAC address. While not typically an issue, in very dense multicast environments, this can cause hosts to process traffic for groups they didn't subscribe to.
