In a typical network, most traffic follows a simple pattern: one source sends a packet to one destination. This is called unicast traffic.
Unicast works perfectly for web browsing, SSH sessions, or file transfers. Each conversation involves exactly two devices.But what happens when one source needs to send the same data to many receivers at the same time?
The Duplication Problem
Imagine a server streaming a live video feed to three receivers on the network.
With unicast, your server must create one separate copy for each receiver. Three receivers means three individual streams, each carrying the exact same data.
Figure 1 – Unicast sends multiple copies
Each copy carries the same payload. Yet every packet travels independently through the network, consuming bandwidth on every link it crosses.
Now scale this to hundreds of receivers. If each stream is 5 Mbps, your server pushes 1.5 Gbps of identical data out of a single interface for just 300 viewers.
This approach does not scale.
The more receivers you add, the more bandwidth you waste.Answer the question below
What type of traffic model sends one individual copy per receiver?
Why Not Use Broadcast?
You might think broadcast solves the duplication problem.
Instead of creating separate copies, the source sends a single frame that reaches every device on the segment.But broadcast has two serious limitations.
First, broadcast is limited to a single Layer 2 domain. Routers do not forward broadcast traffic. If your receivers span multiple subnets, broadcast cannot reach them.

Figure 2 – Broadcast reaches all hosts
Second, broadcast forces every device on the segment to process the frame, even devices that have no interest in the stream. This wastes CPU cycles on every host and creates unnecessary interrupts.
Unicast wastes bandwidth. Broadcast wastes bandwidth and processing power, and cannot cross routers.
Your network needs a third model.Answer the question below
In a unicast model, how many copies of a stream does the server send if there are 100 receivers?
IP Multicast, defined in RFC 1112, introduces a delivery model built specifically for one-to-many and many-to-many communication.
With multicast, your source sends a single copy of each packet. The network itself takes responsibility for replicating that packet only where receivers exist.

Figure 3 – Multicast targets interested receivers
Your server now sends a single stream regardless of how many receivers are watching.
Routers along the path duplicate the packets only at branching points where receivers are present.
Hosts that did not join the group receive nothing.This is the core advantage of multicast: the source’s load stays constant, and network links carry only one copy of the traffic until a fork is needed.
The Multicast Group Model
Multicast traffic is not addressed to a single host.
Instead, it is sent to a multicast group address.A multicast group is identified by a Class D IPv4 address in the range 224.0.0.0 to 239.255.255.255.
Any host that wants to receive the stream joins the group. Any host that is not interested simply ignores it.
Figure 4 – Multicast group membership
The source does not need to know who the receivers are or how many exist. It simply sends traffic to the group address. The network handles the rest.
Answer the question below
Does a multicast source need to know the identity of each receiver?
Unicast, Broadcast, and Multicast Compared
Now that you understand the multicast model, let’s compare all three delivery models side by side.

Figure 5 – Traffic models compared
With unicast, the source creates N copies for N receivers.
With broadcast, the source sends one copy but every host on the segment processes it.
With multicast, the source sends one copy and only group members receive it.
Characteristic
Unicast
Broadcast
Multicast
Delivery model
One-to-one
One-to-all
One-to-many
Source load
Grows with each receiver
One copy
One copy
Crosses routers
Yes
No
Yes
Receiver filtering
Exact (by IP)
None (all hosts process)
Group-based (only members)
Bandwidth efficiency
Poor for groups
Wastes CPU on non-members
Optimal for groups
Table 1 – Unicast, Broadcast, and Multicast Comparison
Multicast combines the best of both worlds.
Like broadcast, the source sends only one copy.
Like unicast, traffic can cross routers and only reaches devices that actually need it.This is why multicast is the standard for applications like IPTV, video surveillance, financial market feeds, and operating system deployment. Any scenario where one source serves many receivers benefits from multicast.
Answer the question below
Which delivery model sends one copy but forces all hosts to process it?
The Class D space is divided into several well-known ranges.
You should know the most important ones.Range
Name
Purpose
224.0.0.0/24
Link-Local
Routing protocols (OSPF, EIGRP, HSRP). TTL = 1, never routed.
224.0.1.0 – 238.255.255.255
Globally Scoped
Routable multicast. Used for IPTV and video conferencing.
239.0.0.0/8
Administratively Scoped
Private multicast, similar to RFC 1918 for unicast. Confined to your organization.
Table 2 – Key IPv4 Multicast Address Ranges
You already use multicast without realizing it.
OSPF sends Hellos to 224.0.0.5 and 224.0.0.6.
EIGRP uses 224.0.0.10.
HSRP uses 224.0.0.2.
These are all link-local multicast groups.
Multicast IPv4 Address Structure
Every multicast IPv4 address is 32 bits long.
The first four bits are always set to 1110, which is the binary signature of Class D. The remaining 28 bits identify the specific multicast group.
Figure 6 – Multicast IPv4 address structure
This fixed prefix is why the multicast range starts at 224.0.0.0. In binary, 224 is 11100000, which matches the 1110 pattern exactly.
Unlike unicast addresses, multicast addresses have no subnet mask and no network/host portion. The entire 28-bit field simply identifies a group.
Multicast MAC Address Format
At Layer 2, multicast IPv4 addresses are mapped to a special MAC address range: 01:00:5E:xx:xx:xx.
The first 25 bits of this MAC address are fixed.They always begin with 01:00:5E, followed by a 0 bit.
This leaves only 23 bits available to represent the multicast group.

Figure 7 – Multicast MAC address format
The mapping takes the lower 23 bits of the multicast IP address and places them into the last 23 bits of the MAC address. Because a multicast IP has 28 variable bits but only 23 map to the MAC, 32 different group addresses can map to the same MAC. This is a known limitation called address ambiguity.
Answer the question below
How many bits from the multicast IP address are copied into the MAC address?
The 23-Bit Mapping Process
Your device takes the multicast IPv4 address and extracts the lower 23 bits.
It copies those 23 bits directly into the last 23 bits of the MAC address 01:00:5E.
The upper 5 bits of the IP’s 28-bit group field are simply discarded.
Figure 8 – IP to MAC address mapping process
This means that groups 239.1.1.1 and 239.129.1.1 both produce the same destination MAC: 01:00:5E:01:01:01. The 5 discarded bits create this overlap.
Your switch uses this destination MAC to forward the frame only to ports that have interested receivers, provided IGMP snooping is enabled.Answer the question below
Which traffic model can cross routers AND only deliver to interested receivers?
Answer the question below
Which destination MAC address does a frame sent to group 239.200.5.10 use?
Multicast sounds simple in theory: the source sends once, the network delivers to all group members. But making this work across a routed network requires several cooperating protocols.
Before you study each protocol in depth, you need the full picture of how they fit together.

Figure 9 – Multicast architecture overview
The multicast control plane is split into two layers.
At the network edge, between hosts and their first-hop router, IGMP manages group membership. In the core, between routers, PIM builds distribution trees toward the source.IGMP — Host-to-Router Signaling
The first question the network must answer is: which hosts want to receive a specific group?

Figure 10 – IGMP at the edge, PIM in the core
IGMP (Internet Group Management Protocol) operates between hosts and their directly connected router. A host uses IGMP to join or leave a multicast group. Your router uses IGMP to track which groups have active members on each interface.
Without IGMP, your router would have no way to know whether any local host is interested in a given multicast stream.
PIM — Router-to-Router Signaling
Once your router knows a local host wants a stream, it needs to pull that stream from the source through the network.

Figure 11 – IGMP joins, PIM builds the path
PIM (Protocol Independent Multicast) is the multicast routing protocol. It builds distribution trees that define the path multicast traffic follows from source to receivers.
PIM does not maintain its own routing table. Instead, it relies on your existing unicast routing protocol (OSPF, EIGRP, BGP) to determine the best path toward the source.This is why it is called "Protocol Independent": PIM works with any unicast routing protocol.
Putting It All Together
Here is how the pieces connect in a typical multicast flow:
A host sends an IGMP Join to its local router, requesting group 239.1.1.1.
Your router uses PIM to signal upstream routers and build a distribution tree toward the source.
The source sends a single stream. Routers replicate packets only at branching points. The host receives the stream.
Each of these protocols will be covered in its own dedicated lesson, starting with IGMP.
Answer the question below
Which protocol do hosts use to join or leave a multicast group?