OSI Series Part 3: Layer 3 – The Network Layer

We’ve handles the wires (Layer 1) and the local hardware addresses (Layer 2). But what happens when you want to send data to a server in a different city, or even just a different building on campus?

Welcome to Layer 3: The network Layer. This is the layer of Routing and Logical Addressing.

1. The Mission: Path Determination

The primary job of the Network Layer is to move data between different networks. It handles Routing which is the process of looking at a destination address and deciding the best path across the “web” of the internet to get there.

While Layer 2 uses a MAC address (your social security number), Layer 3 uses an IP Address (your mailing address). One is a permanent to the hardware; the other changes based on where you are “plugged in.”

2. The PDU: Packets

At Layer 3, we take the “Frames” from Layer 2 and look inside them at the Packets. A Packet contains:

• The IP Header: This includes the Source IP, the Destination IP, and the TTL (Time to Live).
• TTL Tip: TTL is a counter that prevents a packet from wandering the internet forever. Every time it hits a router (a “hop”), the number drops by one. If it hits zero, the packet is discarded.

3. The Hardware: The Router

The “King” of the Layer 3 is the Router. Routers maintain Routing Tables. They don’t care about MAC addresses; they only care about IP ranges. When a packet arrives, the router checks its table, finds the “Next Hop,” and sends it on its way.

4. Logical Addressing: IPv4 vs. IPv6

From my understand in the Network+ studies, we are going to delve deep into a massive amount of time here (there will be a whole section on this)

• IPv4: The “Old Guard.” 32-bit addresses (e.g., 192.168.1.1). Because we ran out of these, we have to use tricks like NAT (Network Address Translation).
• IPv6: The “Future.” 128-bit hexadecimal addresses (e.g., 2001:0db8:85a3….). It provides trillions of addresses, meaning every grain of sand on earth could have its own IP.

5. Real-World Troubleshooting: “The Gateway Check”

When you’re at your desk at your office and a user says they can’t get to Google:

• Ping the Loopback: ping 127.0.0.1. Does their own NIC work?
• Ping the Gateway: Can they talk to the router? if not, there’s a local break.
• Traceroute: Use tracert (windows) to see exactly which router is dropping the packet on the way to the destination.

🧪The “Exam Tip” for Network+

From my studies, CompTIA seems to ask a lot about ICMP (Internet Control Message Protocol). Even though we use it for troubleshooting (Ping/Traceroute), It technically lives here at Layer 3. Remember: ICMP doesn’t carry user data; it carries “status and error” messages for the network itself.

Next Up: Layer 4

Tomorrow, I will dive into the “reliability” layer. We’ll talk about Layer 4: The Transport Layer, the “Three-Way Handshake,” and the eternal battle between TCP and UDP.