2.2 Identification Needed: Documenting My Network

Every device on a network needs some kind of ID so traffic knows where to go, kind of like how every house needs an address for mail delivery. This topic is all about the different flavors of IPv4 addresses you'll run into and how to map out a network so you (or someone else) can actually understand what's connected to what. Once you can read an IP address and sketch a clear diagram, troubleshooting and expanding a network gets way easier.

Types of IPv4 Addresses

IPv4 addresses are the 32-bit numbers (like 192.168.1.5) that identify devices on a network. Not all of them work the same way. Some are meant for the open internet, some only work inside your house, and some exist just for special situations like testing or fallback.

Public IP Addresses

A public IP address is the one your network shows to the rest of the internet. Think of it as your network's "street address" that the outside world can actually find.

Key things to know:

• It's unique. No two devices on the internet share the same public IP at the same time.
• Your ISP (internet service provider) hands it out to your router.
• It's directly reachable from the internet, which is why servers (like the ones hosting websites) use public IPs.
• Organizations get public addresses for anything outward-facing, like web servers, email servers, or VPN endpoints.

So when you load a website, your traffic travels across the internet using public IP addresses on both ends.

Private IP Addresses

A private IP address only works inside a LAN (local area network). These addresses are reserved for internal use, and routers on the internet will discard any traffic aimed at a private IP. That's actually a feature, not a bug. It gives you an extra layer of security, because outside sources can't directly reach devices that only have private addresses.

There are three ranges you need to memorize, one from each "class":

The Class C range is the one you've probably seen most. Home routers love handing out addresses like 192.168.1.100.

A quick way to keep the Class B range straight: it's only 172.16 through 172.31, not the whole 172.x.x.x block. That one trips people up.

APIPA Addresses

Normally, a DHCP (Dynamic Host Configuration Protocol) server handles assigning IP addresses automatically. When you plug in a laptop, DHCP gives it an IP, a subnet mask, a gateway, and so on. No manual setup needed.

But what happens if the DHCP server is down or misconfigured? That's where APIPA (Automatic Private IP Addressing) steps in. The host gives itself an address automatically from this range:

169.254.0.0 to 169.254.255.255

If you ever see a device with an IP starting with 169.254, that's your clue that DHCP failed. The device can still talk to other APIPA devices on the same LAN, but it won't reach the internet. It's basically a "I couldn't get a real address, so here's a placeholder" situation.

Loopback Addresses

A loopback address is used by a device to send data to itself, mostly for testing. If you want to check whether the networking stack on your own machine is working, you can ping the loopback address and see if it responds.

The most common loopback address is:

127.0.0.1

This always refers to the local machine, no matter what device you're on. Developers use it constantly when testing web servers locally (you might've seen http://127.0.0.1:3000 before, or its nickname localhost).

Quick Comparison

Documenting an Existing Network

Once a network is built, you need a way to keep track of what's in it. That's where network diagrams come in. They give you a visual picture of every device and how they're all connected. Diagrams are useful both before setup (for planning) and after setup (for recording the final layout).

A good diagram should show:

• Every device: endpoints, servers, routers, switches, access points, firewalls
• The MAC address and IP address of each device
• How devices connect to each other

Having the MAC and IP addresses on the diagram is huge for troubleshooting. If something breaks, you know exactly which device to check. It also makes it easier to expand the network later, since you can see what IPs are already in use.

Wired vs. Wireless Links

There's a simple convention for showing connections:

• Solid lines = wired connections
• Dashed lines = wireless connections

That way, anyone glancing at the diagram can immediately see how each device is linked without needing a long explanation.

SOHO Networks

Most of the networks you'll document at this level are SOHO (Small Office/Home Office) networks. A SOHO network supports a small number of users on a single LAN, usually in a home or small business. If you have Wi-Fi at home with a few phones, a laptop, and a smart TV connected, congrats, you've been using a SOHO network this whole time.

Devices You'll See in a SOHO Network

Here's the typical cast of characters:

Router

• Moves data between the outside network (the internet) and the local network
• Often comes combined with a modem in a single box, which connects you to your ISP for internet access

Switch

• Links wired devices together and handles traffic inside the LAN
• Think of it as a traffic cop for internal wired communication

Wireless Access Point (WAP)

• Provides Wi-Fi by attaching to a switch or router
• This is what lets your phone connect without a cable

Wireless Gateway

• A single device that combines a modem, router, switch, and WAP into one box
• Many SOHO networks use these because it's simpler than buying four separate devices. That all-in-one box from your ISP is almost certainly a wireless gateway.

Firewall

• Filters traffic to protect the network (covered in more detail elsewhere in the course)

Endpoints

• Any device that joins the network to send and receive data
• Examples: mobile phones, laptops, PCs, servers, IoT devices (smart thermostats, smart bulbs), printers, 3D printers, NAS (network attached storage), and VoIP (voice over IP) phones

Basically, if it connects to the network and uses data, it's an endpoint.

Cabling in SOHO Networks

Three cable types show up most often:

• Twisted pair (Ethernet): The most common cable for internal wired connections. Those blue cables with the RJ45 clip on the end? Twisted pair.
• Coaxial: Often used by ISPs for the external connection into the SOHO router. If you have cable internet, coax is probably running into your house.
• Fiber optic: Also used by ISPs for the external link, especially with newer, faster internet service.

The pattern to remember: twisted pair handles the inside of the network, while coax and fiber usually handle the outside connection from the ISP to your router.

Putting It All Together

Imagine you're documenting a home network. You'd sketch a diagram showing:

• A wireless gateway connected to the ISP via a coaxial cable coming in from outside
• A desktop PC connected to the gateway with a twisted pair Ethernet cable (solid line), labeled with its MAC address and a private IP like 192.168.1.10
• A laptop and a phone connected wirelessly (dashed lines), each with their own MAC and IP (192.168.1.11, 192.168.1.12)
• A smart printer (IoT endpoint) connected wirelessly with IP 192.168.1.13
• The gateway itself holding the public IP assigned by the ISP on its outside-facing interface, and a private IP (192.168.1.1) on its inside-facing interface

If one day the laptop suddenly shows an IP like 169.254.12.45, you'd know right away that DHCP on the gateway isn't handing out addresses properly, because APIPA has kicked in. If you wanted to test whether the laptop's network stack even works, you'd ping 127.0.0.1 first. That's how knowing your IPv4 address types and keeping a solid diagram turn confusing problems into quick fixes.