Networking Fundamentals
The TCP/IP Model Explained
The OSI model is the textbook; the TCP/IP model is what the internet actually uses. It describes the same journey in four practical layers.
Four layers instead of seven
The TCP/IP model — also called the internet protocol suite — organizes networking into four layers rather than OSI's seven. It was designed alongside the protocols it describes, so it maps cleanly onto how real internet traffic behaves.
- Application — the protocols programs use directly: HTTP for the Web, SMTP for email, DNS for name lookups.
- Transport — TCP (reliable) and UDP (fast) manage end-to-end delivery using port numbers.
- Internet — IP handles addressing and routing packets across networks.
- Link — the local network hardware and protocols, like Ethernet and Wi-Fi.
How it maps to OSI
The TCP/IP application layer rolls together OSI's application, presentation, and session layers. The transport and internet layers line up closely with OSI's layers 4 and 3. The link layer combines OSI's data link and physical layers. Same journey, fewer boxes.
Encapsulation: boxes inside boxes
As data moves down the layers, each one wraps it in its own header — like putting a letter in an envelope, then a mailbag, then a truck. Your application data gets a transport header (with ports), then an internet header (with IP addresses), then a link header (with MAC addresses). At the destination, each layer unwraps its envelope in turn.
Why this model won
TCP/IP became the internet's foundation because it was open, freely implementable, and pragmatic — it prioritized working code over theoretical completeness. Every device you own that goes online speaks this suite. When IP Ducky reports your IP address, it is reading a value from the internet layer; when it fetches data, it is using the transport and application layers on top.