OSI 7-Layer Model — What Each Layer Does and Why the Split Exists

Concrete Example

Layering is easiest to believe when you look at the bytes it produces. A single HTTPS request leaving a laptop is not one object — it is four nested ones, each wrapped by the layer below in strict order. This is encapsulation made literal:

bytes on the wire ─────────────────────────────────────────────────────────▶

┌──────────────┬───────────┬────────────┬──────────────────────────┬─────┐
│ Ethernet hdr │  IP hdr   │  TCP hdr   │ TLS record + HTTP request│ FCS │
│ src/dst MAC  │ src/dst IP│ src/dst port│  GET /index.html ...    │     │
└──────────────┴───────────┴────────────┴──────────────────────────┴─────┘
 └─ L2 FRAME ─────────────────────────────────────────────────────────────┘
                └─ L3 PACKET ────────────────────────────────────────┘
                            └─ L4 SEGMENT ───────────────────────────┘
                                          └─ L7 DATA ────────────────┘

Read the brackets bottom-up and you have the send path: the application produces data, the transport layer prepends a port header to make a segment, the network layer prepends an IP header to make a packet, and the data link layer wraps the whole thing in a MAC header and trailer to make a frame. The physical layer then emits it as voltage, light or radio. On receipt the destination unwraps in the reverse order. Note that no layer inspects the payload it was handed — the IP header is written without ever parsing the HTTP request inside it.

The second thing worth tracing is what each intermediate device actually touches. Take a laptop at 192.168.1.10 fetching a page from a server at 93.184.215.14, across this topology:

[Laptop] ── [Switch] ── [Router R1] ═══ internet ═══ [Router R2] ── [Server]
 192.168.1.10            gateway                                    93.184.215.14
                       192.168.1.1

One sentence captures the whole table: the IP addresses are fixed end-to-end; the MAC addresses are rewritten at every router. That is precisely the L3-vs-L2 distinction — global and unchanging versus local and per-hop — and it is the most useful thing the OSI model gives you. A useful thought experiment: delete the switch and routing still works (plug the laptop straight into R1); delete the routers and nothing ever leaves the LAN. Routers are what make it “the internet.”

Visual Model

Think about posting a letter overseas. You write it, hand it to a courier, who hands it to an airline, which hands it to a plane’s crew. Each party only talks to the one next to it and only cares about its own job — the airline never reads your letter, and you never fly the plane. If the airline swaps a 737 for an A320, your letter is unaffected, because the interface between courier and airline never changed. That division of labour is OSI, and it is why Wi-Fi versus Ethernet is invisible to HTTP.

The stack below is the whole model in one view. Step through it top-down — the order a click travels as it leaves your machine — or click any layer directly. Each row carries the layer’s job, its PDU name, the address it uses, and which devices act at that layer.

Two beliefs about that L3/L2 boundary trip up almost everyone learning this material. Both are worth correcting explicitly, because getting them backwards makes every later topic — ARP, VLANs, subnetting, load balancing — harder than it needs to be.