Broadcast, multicast, and why only UDP can do this
Step 1 of 2 — understand the idea. Read this first and the packet trace will confirm what you already expect, instead of teaching you two things at once.
What you'll be able to do
▸Explain why a connection-oriented protocol cannot broadcast
▸Distinguish broadcast from multicast by who receives and who decides
▸Say where the broadcast stops and why that boundary matters
Every protocol so far has needed a destination address. That works right up until the moment you do not have one — a machine that has just been plugged in and needs a DHCP server, a device looking for a printer, a router looking for other routers.
Broadcast is the answer to that: address the packet to everybody on the segment and let whoever is interested respond. It only works with a stateless transport, because there is no coherent way to have a connection with an unknown number of machines at once.
That is why this is a UDP lesson rather than a general networking one.
Watch these fields in the lab: ipv4.destIp
Unicast is speaking to one person by name. You need to know who they are.
Broadcast is shouting in a room. Everybody stops what they are doing, listens long enough to decide it was not for them, and goes back to work. Cheap for you, and a small tax on everybody else.
Multicast is a mailing list. You send once; the people who subscribed receive it; nobody else is interrupted. The sender's effort is the same as the shout and the cost to bystanders is nothing.
The walls of the room are the broadcast domain, and a router is a wall.
Shouting in an office, versus a mailing list
shouting across the room
→ broadcast to the subnet
the walls of the room
→ the broadcast domain, ending at a router
a mailing list you subscribed to
→ a multicast group you joined
Where it breaks down:A person who hears a shout that was not for them has genuinely lost nothing. A machine has done real work — received the frame, walked up the stack to the port number — before discarding it, which is why a chatty broadcast protocol on a large segment is a measurable cost.
✓ Concept check — before you open the packets
These test the idea, not the trace. You should be able to answer them from the explanation above.
Now that you understand the concept, observe how it appears in the packet exchange.
The lab runs a real simulated capture — pause, step, click any packet, and inspect every byte.