3.3 Making It Work: Connecting, Configuring, and Verifying Access

Setting up a network sounds complicated, but it really comes down to a few core skills: reading IP addresses, cabling devices together, and configuring the settings that let everything talk. This topic walks through how to tell if two devices live on the same network, how to physically build and configure a LAN, and how to set up a wireless access point that serves both your internal users and guests safely.

Reading IPv4 Addresses and Subnet Masks

Every device on an IP network needs an address so other devices know where to send data. In IPv4, that address is 32 bits long. Writing out 32 ones and zeros gets old fast, so we use dotted decimal format instead.

Octets and Dotted Decimal

The 32 bits get split into four chunks of 8 bits each. Each 8-bit chunk is called an octet. Since 8 bits can represent values from 0 to 255, every octet shows up as a decimal number in that range, separated by dots.

So an address like 192.168.1.10 is really:

</>Code
11000000.10101000.00000001.00001010

Four octets, 32 bits total, just written in a way humans can read.

Network Bits vs. Host Bits

Here's the key idea: those 32 bits are split into two parts.

• Network bits identify which network the device is on
• Host bits identify the specific device within that network

Think of it like a street address. The network bits are the street name (which neighborhood you're in) and the host bits are the house number (which specific house on that street).

But how do you know which bits are network bits and which are host bits? That's the job of the subnet mask.

How Subnet Masks Work

A subnet mask is also 32 bits long, but it follows a strict pattern: a run of 1s followed by a run of 0s. No mixing.

• The 1s in the mask mark the network bits
• The 0s (trailing zeros) mark the host bits

For example, the mask 255.255.255.0 in binary is:

</>Code
11111111.11111111.11111111.00000000

That's 24 ones followed by 8 zeros. So the first three octets of any address using this mask are network bits, and the last octet is the host bits.

CIDR Notation

Writing out 255.255.255.0 every time gets tedious, so there's a shortcut called Classless Inter-Domain Routing (CIDR) notation. You just write a slash followed by the number of 1 bits in the mask.

So 192.168.1.10/24 means the address 192.168.1.10 with a mask of 24 ones (which is 255.255.255.0).

Checking If Two Devices Share a Network

Two IPv4 devices are on the same network when their network bits match and they're using the same subnet mask. To check, you apply the mask to each address and compare the network portions.

Walking Through an Example

Suppose you have three devices, all using the mask 255.255.255.0 (/24):

• Device A: 192.168.1.10
• Device B: 192.168.1.20
• Device C: 192.168.2.30

Since the mask is /24, the first three octets are network bits. So compare those:

• A's network portion: 192.168.1
• B's network portion: 192.168.1
• C's network portion: 192.168.2

A and B match, so they share a network and can talk to each other directly. C has a different network portion (192.168.2 instead of 192.168.1), so it's on a different network. For C to reach A or B, traffic would have to go through a router.

The quick trick: look at how many bits the mask covers, then compare that portion of each address. If it matches, same network. If not, different networks.

Configuring a Local Area Network

Building a LAN is part planning, part physical work, and part configuration. You want to finish the network design before you start plugging anything in, so you know what cables, devices, and settings you need.

Tools and Hardware You'll Need

Setting up a LAN calls for a variety of equipment:

• Appropriate cabling to join devices (Ethernet cable like Cat6 is common)
• A cable stripper (or wire stripper) to peel off the insulation
• Connectors like RJ45 for attaching Ethernet cables to devices
• A crimping tool to lock the connectors onto the cables
• Cable management and labeling supplies to keep runs organized
• The endpoints (computers, printers, phones) and network devices (switches, routers)
• Personal protective gear like gloves and safety glasses

Configuring a Switch

A network switch connects devices within the LAN. To configure its settings (password, IP address, subnet mask), you've got two options:

1. Command Line Interface (CLI): typing commands directly
2. Graphical User Interface (GUI): clicking through the switch's management console in a browser

To reach the management console in the first place, you usually attach a console cable from your computer to the switch.

Adding a Router or Gateway

A switch alone keeps traffic inside the LAN. To reach external networks (including the internet), you need a router or gateway. For the router to act as the default gateway for devices on the local network, you have to assign it an IP address and subnet mask that fit the network.

Devices on the LAN then send any traffic destined for outside networks to that gateway, and the router figures out where to forward it.

Adding Wireless

Want Wi-Fi on your LAN? Two ways to do it:

• Install a dedicated wireless access point (WAP)
• Turn on the wireless features built into a wireless router

The WAP needs to be configured with:

• An SSID (the network name)
• An IP address and subnet mask
• Wireless security settings (encryption, password)

Configuring the Endpoints

Every endpoint on the network (laptops, desktops, printers) must have an IP address and subnet mask that fit the network. You can assign addresses two ways:

• Static addressing: you assign a specific IP address manually, one device at a time
• DHCP (Dynamic Host Configuration Protocol): a DHCP server hands out addresses automatically as devices connect

Static is useful for devices that need a predictable address (like a printer or server). DHCP is easier for everything else because it just works when a device joins.

Verifying Connections with ping

Once everything's connected, you need to check that devices can actually reach each other. The ping command does this by sending Internet Control Message Protocol (ICMP) packets to a specific IP address. If the target device is connected and reachable, it answers the ICMP request.

For example:

</>Code
ping 192.168.1.127

This sends ICMP packets to whatever device holds the address 192.168.1.127. If you get replies back, the connection works. If it times out, something's wrong (wrong IP, cable issue, device off, firewall blocking it, etc.).

Setting Up Guest and Internal Wireless Networks

Most WAPs can run two wireless networks at once: an internal network for your own devices and a guest network for visitors. Keeping guests separated this way adds protection, because guests can get online but can't poke around your internal resources.

Configure the Internal Network First

Always set up the internal network first. That way you can confirm the settings are right and that your internal devices and resources can actually talk to each other before you add guest access on top.

To configure the internal network:

1. Give it an SSID protected by a strong password
2. Turn on WPA2 or WPA3 encryption
3. Turn off WPS (Wi-Fi Protected Setup has known vulnerabilities)

Turning On the Guest Network

The guest network gets switched on from the router or WAP's settings. To reach those settings, you typically type the device's IP address into a web browser and sign in with administrator credentials.

Once you enable the guest network feature, the guest configuration options show up. Filling them in looks a lot like configuring any wireless network. The guest network must have:

• Its own separate SSID (different from the internal one)
• A strong password
• WPA2 or WPA3 encryption turned on

Extra Protections for Guests

Beyond the basics, there are additional measures you can apply to a guest network:

• Cap the number of devices that can join at once
• Block guest users from reaching internal network resources (this is the big one for security)
• Restrict access hours or session length so guests can't camp on the network forever
• Turn on a captive portal where users have to sign in and accept terms of use before connecting

Verifying It Works

The test is simple: join a device to the guest network and try two things.

1. Can you reach the internet? (You should be able to.)
2. Can you reach internal resources, like a shared printer or file server? (You should not be able to.)

If both check out the right way, your guest network is configured correctly. If guests can somehow still reach internal devices, something in the isolation settings isn't right and needs to be fixed before you let anyone use it.