Tracing a Packet Through the Stack

To make the layers concrete, lets trace a single message from one computer to another. We will watch the data travel down the sender stack, across the network, and up the receiver stack. Seeing the full journey ties together encapsulation, addressing, and routing into one clear story and shows how every layer plays its part.

It begins at the application layer on the sending computer. Say a browser builds a request for a web page. This raw request is the original data, with no networking headers yet. The application hands it down to the transport layer to start its trip. From here, each layer will wrap the data as it descends toward the network.

The transport layer adds a header with port numbers so the data reaches the right service, and with TCP it adds sequence numbers for reliability. The data is now a segment. The transport layer also splits large data into multiple segments if needed. Each segment is then passed down to the internet layer for addressing.

The internet layer wraps the segment with an IP header holding the source and destination IP addresses, forming a packet. These IP addresses stay the same from end to end, identifying the original sender and final receiver. The packet now knows which device it must ultimately reach, no matter how many networks lie between them.

The link layer wraps the packet in a frame with the MAC address of the next device on the local network, plus an error-check trailer. The frame is converted to signals and sent across the medium. Note the destination MAC is only the next hop, not the final device, which is a key detail in the journey.

If the destination is on another network, the frame goes first to the router (the default gateway). The router receives the frame, strips it, reads the IP address in the packet, and decides where to forward it next. The router then builds a new frame with a new destination MAC for the next hop. The packet survives; the frame is rebuilt.

This pattern repeats at each router along the path. At every hop, the frame is rebuilt with new MAC addresses for that local link, while the packet and its IP addresses stay unchanged. So the link-layer wrapper changes constantly, but the network-layer addressing is end to end. The packet travels router to router until it reaches the destination network.

When the packet reaches the final network, the last device delivers the frame to the destination computer. Now decapsulation begins. The receiver moves the data up its stack, with each layer reading and removing its own header. The journey down on the sender is mirrored by the journey up on the receiver.

The link layer checks the frame for errors and strips it to reveal the packet. The internet layer confirms the destination IP and removes the IP header. The transport layer reads the port, reorders and reassembles segments if needed, and hands the clean data up. Each layer undoes exactly what its peer on the sender did.

Finally the application layer on the receiver gets the original data, the web request, exactly as the sender created it. The receiving service processes it and will send a response that makes the same trip in reverse. The message has crossed the network, and to the applications it simply appears as if they spoke directly.

A message goes down the sender stack, gaining a transport header (segment), an IP header (packet), and a link header (frame). It crosses routers where the frame is rebuilt each hop but the packet stays the same, then goes up the receiver stack as each header is stripped. This down-across-up path is how every networked conversation truly happens.

As a packet crosses routers, what stays the same and what changes at each hop?

Tracing a packet: on the sender, data descends, becoming a segment (ports), a packet (end-to-end IP addresses), and a frame (next-hop MAC). At each router, the frame is rebuilt with new MACs while the packet and IP addresses stay constant. At the destination, data ascends as each layer strips its header, delivering the original message to the application. Down, across, up.