Don't Panic — Protocols and Addressing

Network protocols are the rules that let machines exchange data without holding a committee meeting inside every packet. Addressing is the set of labels that tells the data where to go. Together, they turn a collection of cables, radios, and disagreeable boxes into a network that can move a request from one application to another.

The useful trick is that no address is the address. A MAC address handles the next physical hop on a local segment. An IP address names the destination across networks. A port number identifies the application on the destination host. Three labels, three jobs. Mixing them up is how a packet capture becomes an abstract painting.

Data also travels in layers. The application creates the message. TCP or UDP adds transport information. IP adds the source and destination for the route. Ethernet wraps that packet in a frame for the next hop. At the other end, the wrapping comes off again. This is encapsulation, which sounds as if the packet has been sent to finishing school, but it is only headers being added and removed.

The surprising part is the journey to a remote server. Your host does not put the server's MAC address in its outbound frame. It uses ARP to find the MAC address of the default gateway, then gives the router a frame containing the remote IP destination. Each router repeats the local delivery step for the next hop. The IP destination guides the trip; the frame destination changes along the way.

TCP and UDP make another trade. TCP sets up a connection and uses acknowledgments and sequence numbers to deliver an ordered byte stream. UDP sends datagrams without that machinery. Neither is a personality type. They fit different application needs, and ports make it possible for many conversations to share one IP address without each arriving at the wrong desk.

Read the Intro when the four layers need a full explanation. Use the Slides for the map from application data to frame. Keep the Cheatsheet nearby when prefixes, address scopes, and TCP states start blending together. Then use the Practice Reference and exercise to inspect one flow until MAC, IP, and port each look like the answer to their own very specific question.