Topic 1 of 5

OSI / TCP-IP Layers

Networking is organized into layers so each piece of software only has to worry about its own job: the code that renders a web page never has to know how bits move across a fiber-optic cable, and the code pushing those bits never has to know what a URL is. Each layer only talks to the layer directly above and below it, through a well-defined interface — and has no idea what happens further up or down the stack.

Two numbering schemes are common: the theoretical 7-layer OSI model and the practical 4-layer TCP/IP model. Below, explore what each of the 7 OSI layers does, then watch a message get wrapped in headers as it travels down one stack and unwrapped as it climbs back up the other.

Why split networking into layers?

Interoperability — a Linux server and a Windows laptop can talk to each other because both implement the same layer interfaces, even though almost everything above and below those interfaces differs.
Swappability — you can switch your laptop from Wi-Fi to a wired Ethernet connection mid-session without changing a single line of browser code, because only L1/L2 changed.
Independent evolution — HTTP went from version 1.1 to 2 to 3 without any change to how IP routes packets underneath it.
A shared troubleshooting vocabulary — saying "it's a Layer 3 problem" instantly tells another engineer to look at routing and IP addressing, not cabling or application code.

Explore the layers

Watch encapsulation happen

Step through what happens when your browser sends a request: the data picks up a header at each layer on the way out, travels across the wire, then gets unwrapped one layer at a time on the other end.

Sender

Receiver

Presentation and Session (L5–L6) don't add their own header in this simplified view — they hand data straight to Transport. Also, in reality, if the finished frame is bigger than the link's MTU, it has to be split into multiple packets before it can be sent — a process called fragmentation.

OSI vs. TCP/IP: two models, one idea

The Internet was actually built on the 4-layer TCP/IP model. The 7-layer OSI model came from a separate, mostly unimplemented standardization effort — but its terminology stuck because it's more granular and easier to teach layer-by-layer.

OSI (7 layers)	TCP/IP (4 layers)
7. Application	Application
6. Presentation
5. Session
4. Transport	Transport
3. Network	Internet
2. Data Link	Network Access
1. Physical	Network Access

Common gotchas

NAT breaks layering purity. NAT devices rewrite Layer 3/4 information on the fly, which is why protocols that embed IP addresses inside their Layer 7 payload (like older FTP) can break behind NAT.
Firewalls deliberately look inside layers they "shouldn't." A Layer 3/4 firewall can also peek into Layer 7 payloads to block specific applications — a intentional layer violation done for security.
MTU mismatches cause silent slowdowns. If a packet is too big for a link and the Don't Fragment flag is set, routers drop the oversized packet instead of splitting it, leading to hard-to-diagnose connection hangs.
Not every layer is meaningfully involved in every conversation. A ping between two hosts on the same switch barely touches Layer 3 routing logic — it's mostly a Layer 2 conversation.