Plug a new router into a cable modem, and within a minute a laptop across the room is browsing the web. That convenience hides a stack of decisions the router makes for you: which addresses to hand out, how devices find each other, and how outside traffic gets in or stays out. A technician needs to understand those decisions well enough to change them on purpose.
This maps to CompTIA A+ Core 1 (220-1201), Domain 2 (Networking), and the objectives covering IP addressing and configuring a small office/home office (SOHO) network. The exam expects you to know how IPv4 and IPv6 addresses are structured, the difference between static and dynamic addressing, and the settings you configure on a SOHO router for both wired and wireless clients. In practice, that's the difference between a network that "just works" and one you can actually troubleshoot when it doesn't.
We'll work through addressing first, because every SOHO setting sits on top of it, then move to the router, the wireless side, and the security and service settings you touch on real jobs.
An IP address identifies a device, and the mask says where it lives
Every device on an IP network needs a unique address for that network. In IPv4, that address is 32 bits, written as four decimal numbers separated by dots, such as 192.168.1.20. Each of those four numbers (called an octet) represents 8 bits and ranges from 0 to 255. That gives a theoretical space of about 4.3 billion addresses, which sounds like a lot until you remember how many devices exist worldwide.
An IP address by itself isn't enough. It always travels with a subnet mask, which tells the device which part of the address identifies the network and which part identifies the host. A common home mask is 255.255.255.0. Where the mask shows 255, that portion of the address is the network; where it shows 0, that portion is the host. So on 192.168.1.20 with a 255.255.255.0 mask, the network is 192.168.1 and the host is 20. Devices with the same network portion can talk directly. Devices on different networks need help.
That help is the default gateway. The gateway is the address of the router that forwards traffic off the local network toward other networks, including the internet. On a home network the gateway is usually the router's own LAN address, like 192.168.1.1. If a device has no gateway or the wrong one, it can reach neighbors on its subnet but nothing beyond it. That's a classic symptom to recognize on the exam: local resources work, the internet doesn't.
You'll also see the mask written in CIDR notation, where /24 means the same thing as 255.255.255.0 (24 bits of network). You don't need to subnet by hand for Core 1, but you should recognize that /24 and 255.255.255.0 describe the same boundary.
Private addresses stay inside, public addresses face the internet
Not every IPv4 address is meant to appear on the public internet. Specific ranges are reserved as private addresses for use inside local networks. Your SOHO router uses these on the LAN side, and they never route across the internet directly. This is why the same 192.168.1.x range shows up in millions of homes without conflict.
| Private range | Mask | Common use |
|---|---|---|
| 10.0.0.0 – 10.255.255.255 | 255.0.0.0 (/8) | Large private networks |
| 172.16.0.0 – 172.31.255.255 | 255.240.0.0 (/12) | Medium networks |
| 192.168.0.0 – 192.168.255.255 | 255.255.0.0 (/16) | SOHO and home networks |
A public address, by contrast, is globally unique and assigned by your ISP. Your router usually gets one public address on its WAN (internet) interface. Every device behind the router shares that single public address through Network Address Translation (NAT). NAT rewrites the private source address on outbound traffic to the router's public address, tracks the connection, and translates the replies back to the right internal device. For the exam, remember that NAT is what lets many private hosts share one public IP.
You should also recognize the loopback address, 127.0.0.1, which always refers to the local device itself. Pinging it tests whether the local TCP/IP stack is working, independent of any network hardware.
DHCP hands out addresses automatically, static addressing sets them by hand
There are two ways a device gets its IP configuration: dynamically or statically.
Dynamic Host Configuration Protocol (DHCP) is the automatic method, and it's the default on nearly every SOHO router. The router runs a DHCP server that leases addresses from a defined pool (for example, 192.168.1.100 through 192.168.1.200). When a device joins, it requests a lease and receives an address, subnet mask, default gateway, and DNS server addresses all at once. The lease has a time limit, after which the device renews it. DHCP is why you can hand a guest the Wi-Fi password and they're online without typing a single number.
Static addressing means you type the configuration into the device by hand: address, mask, gateway, and DNS. You use it for devices that must always be reachable at a known address, such as network printers, servers, IP cameras, and the router itself. The trade-off is maintenance. A statically assigned address must fall inside the correct subnet, must not collide with the DHCP pool, and must be unique. Two devices sharing an address causes an IP conflict, which knocks both off the network intermittently.
A practical middle ground is a DHCP reservation, sometimes called address reservation. You tie a specific IP to a device's MAC address on the router, so DHCP always hands that device the same address. You get the stability of a static address with the central management of DHCP. On the job this is the cleaner way to give a printer a fixed address, because you configure it once on the router instead of on each device.
APIPA tells you DHCP failed, not that the network is fine
When a device is set to obtain an address automatically but can't reach a DHCP server, Windows assigns itself an address from the Automatic Private IP Addressing (APIPA) range: 169.254.0.1 through 169.254.255.254, with a 255.255.0.0 mask. This is a link-local address, meaning it works only for communication with other devices on the same physical segment that also fell back to APIPA. There's no gateway and no DNS.
For a technician, an APIPA address is a diagnostic clue, not a working configuration. If you run ipconfig and see 169.254.x.x, the device tried DHCP and got no answer. Check the cable, the switch port, and whether the DHCP server (usually the router) is up and reachable.