← Computer Networks Flagship protocol trace

Packet Journey

Follow one URL from browser cache to rendered bytes. Inspect what changes at every layer—and what does not.

Full network path 18 deterministic events · no live traffic · ⚡ 0 XP
Scenario controls

Choose a bounded journey

Every run is generated locally from fixed teaching data.

Reserved example URL https://learn.example/packet-journey
Event timeline

URL → render

6% replayed
1 / 18

Keyboard: ← previous · → next · Space play/pause

Where the event happens

Illustrated topology

Browser cache
Browser cache + navigation
Client stack 192.0.2.10
LAN one switched hop
Gateway 192.0.2.1
Routed path collapsed hops
Web origin 203.0.113.x
DNS resolver198.51.100.53 · routed branch
Rendererlocal browser handoff

Active at step 1: browser.

Event 1 of 18
browser cache

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.

What this step compresses We model one top-level document cache. A real page can have different cache states per resource.
Layer lens

Where it fits

TCP/IP model
Application · browser
OSI teaching map
7 · Application
Browser cache
Frame / packet / segment

Current envelopes

local

No network envelope yet

Internet · IP packet No IP packet
Transport · segment / datagram No transport unit
Application data Cache key: GET https://learn.example/packet-journey
Added here none
Removed here none
Address inspection

Source → destination

MAC = this hop only

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.