Packet Journey
Follow one URL from browser cache to rendered bytes. Inspect what changes at every layer—and what does not.
URL → render
Keyboard: ← previous · → next · Space play/pause
Illustrated topology
Active at step 1: browser.
The browser checks its response cache
Look for a reusable response keyed by https://learn.example/packet-journey.
The browser checks whether a complete response can be reused before asking the network stack for anything.
Where it fits
- TCP/IP model
- Application · browser
- OSI teaching map
- 7 · Application
Current envelopes
No network envelope yet
No link frame at this local stepNo IP packetNo transport unitCache key: GET https://learn.example/packet-journeySource → destination
Link hop · MAC
- Source
not used — local step- Destination
not used — local step
Inside the browser; no frame exists
Network · IPv4
- Source
not used — local step- Destination
not used — local step
IP identifies the illustrated end hosts; routers forward between links.
Transport · port
- Source
not used — local step- Destination
not used — local step
Ports select the endpoint service or client socket when transport is in use.
Simulation assumptions and learning boundaries
- IPv4 is used so the IP-to-MAC handoff can be traced with ARP.
- The HTTPS origin is remote, so the client sends Ethernet frames to a default gateway.
- DNS uses one UDP exchange and succeeds.
- TCP and TLS complete without loss, retry, resumption, or interception.
- MAC addresses describe only the illustrated local link and change at routers.
Address safety: .example names are reserved for examples; 192.0.2.0/24, 198.51.100.0/24, and 203.0.113.0/24 are documentation networks. MACs
beginning with 02: are illustrative locally administered values.