A shared language

Networking involves many technologies working together: cables, radio signals, addresses, protocols and applications. To talk about them clearly, engineers use layered models. A layer is a group of functions that solves one part of the problem and hands its result to the next layer.

The OSI model

The OSI model has seven layers. Engineers still use it daily to describe where a problem sits.

A common memory aid from Layer 1 upward is “Please Do Not Throw Sausage Pizza Away.”

The TCP/IP model

The TCP/IP model is what the internet actually uses. It groups the OSI layers into four: Link, Internet, Transport and Application. In practice, people mix both: “it’s a Layer 2 problem” (switching) or “the app layer is fine.”

Encapsulation

When you send data, each layer wraps it with its own header, like putting a letter in an envelope, then into a box, then onto a truck:

1. The application creates data (for example, an HTTP request).
2. Transport adds a TCP header with port numbers, creating a segment.
3. Network adds an IP header with source and destination IP addresses, creating a packet.
4. Data Link adds an Ethernet header with MAC addresses, creating a frame.
5. Physical sends the bits as electrical, light or radio signals.

The receiving side removes each layer in reverse order.

Why it helps troubleshooting

If a link light is off, it is a Layer 1 problem. If a PC has no IP address, think Layers 2–3 and DHCP. If ping works but a website does not, look higher: DNS, ports or the application. Layers turn a confusing problem into a checklist.