When you open a website, send a message, or connect to a remote device, the data does not travel as one unexplained block. Multiple protocols cooperate, each device performs a limited role, and the information is wrapped for each part of the journey.
What you will be able to do
- Distinguish end devices from intermediary devices.
- Explain unicast, broadcast, and multicast delivery.
- Describe encapsulation and de-encapsulation.
- Identify what changes at each routed hop.
01
End devices and intermediary devices
End devices are where communication begins or ends. Laptops, phones, servers, cameras, and printers run applications that create or consume data. Their network interfaces turn application data into signals that can enter a network.
Intermediary devices move or control that traffic. A switch forwards Ethernet frames inside a local network. A router forwards IP packets between networks. A firewall applies policy to decide which traffic may cross a boundary. One physical product can perform several roles, but the distinction helps you reason about a packet's path.
When troubleshooting, first ask whether the fault is at an endpoint, on the local link, or at an intermediary device. This prevents random configuration changes.
02
Protocols make communication predictable
A protocol is a set of communication rules. It can define how a message is formatted, how devices identify one another, when a sender may transmit, and how an error is reported. Ethernet, IP, TCP, UDP, DNS, and HTTP solve different parts of the same delivery problem.
Layers let each protocol focus on a narrower responsibility. An application can request reliable transport without needing to know which switch port forwards the next Ethernet frame.
03
Unicast, broadcast, and multicast
Unicast is one-to-one delivery. Most interactive traffic is unicast. Broadcast targets every host in an IPv4 broadcast domain and is kept local by routers. Multicast targets members of a selected group, avoiding a separate copy for every receiver.
IPv6 does not use broadcast. It relies on multicast and other mechanisms for functions that IPv4 may perform with a broadcast.
04
Encapsulation and de-encapsulation
As data moves down a protocol stack, each layer adds control information. Transport information identifies applications and may provide reliability. An IP header identifies source and destination networks. An Ethernet header identifies the next local-hop interfaces. The final frame is converted to signals on the medium.
At the receiver, the process is reversed. Each layer interprets and removes the information intended for it, then passes the remaining payload upward. This is de-encapsulation.
Application data -> Segment -> Packet -> Frame -> Bits05
What changes at a router
A router receives a Layer 2 frame, verifies it, removes the frame header and trailer, and examines the IP packet. It selects a route and then builds a new frame for the outgoing link.
The source and destination IP addresses normally remain the endpoints of the communication. The Layer 2 source and destination addresses change because every local link has a different sender and next hop. Understanding this distinction is central to packet analysis.
06
A short delivery walkthrough
- The application creates data for a remote server.
- The host adds transport and IP information.
- Because the destination is remote, the host frames the packet for its default gateway.
- The switch learns the source MAC address and forwards the frame.
- The router removes the incoming frame, selects a route, and creates a new frame.
- The destination receives the data and de-encapsulates it for the application.
The first frame does not use the remote server's MAC address. MAC addresses provide local-hop delivery; the first destination MAC belongs to the default gateway.