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

Four numbers make a device part of a network: an IP address, a subnet mask, a default gateway, and a DNS server. This guide shows how to set them by hand or by DHCP, how the mask decides whether two devices can talk directly, and how to prove every configuration with ipconfig and ping.

After Topics 3.1 and 3.2, the tournament network exists on paper. Topic 3.3 is build weekend: every console, switch, and access point needs a correct address, and one wrong octet takes a device off the air while every cable stays plugged in. The skill tested here is verification: a configuration is done when ping says so, not when the settings screen closes.

• Static or DHCP: two ways a device gets its address
• The four numbers every device needs
• Are two devices on the same network? The mask decides
• Step-by-step: building the tournament LAN
• Verifying access with ipconfig and ping
• Practice: Config Clinic
• One access point, two networks: internal and guest
• Using AI to draft configurations, safely
• Key terms
• Frequently asked questions

Static or DHCP: two ways a device gets its address

A static IP address is typed in by hand: open the device's network settings and enter the IP address, subnet mask, and default gateway yourself. A dynamic address is leased by a DHCP server, usually built into the router, which manages a pool of available addresses and hands one to each device that asks.

Use static addresses for devices everything else must find at a fixed spot: the streaming rig, the scoreboard server, the switch itself. Use DHCP for the crowd: eighty player consoles need a pool, not hand-typed addresses. Configuring the pool happens on the server side: open the router's web interface or CLI, define the pool's address range, set the subnet mask, default gateway, and network address, and choose a lease time. On each host, DHCP is one setting: obtain an IP address automatically.

The four numbers every device needs

Setting	What it does	Tournament example
IP address	Identifies the device; unique on the LAN, inside the range	Streaming rig: 192.168.20.10
Subnet mask	Splits the address into network bits and host bits	255.255.255.0 (/24)
Default gateway	The router; the door to other segments and the internet	192.168.20.1
DNS server	Turns names into addresses	192.168.20.1

After setting them, verify. On Windows, ipconfig prints the address, mask, and gateway the device actually holds; on Mac and Linux use ifconfig or the network settings screen. The MAC address appears as Physical Address, Hardware Address, or Ether Address depending on the system. What the screen accepted and what the device holds are two different facts, and only the second counts.

Are two devices on the same network? The mask decides

An IPv4 address is 32 bits written as four octets, each 0 to 255. The subnet mask is a run of ones followed by zeros: the ones mark the network bits, the zeros the host bits. CIDR notation is shorthand for the same thing, a slash plus the count of one-bits: /24 is 255.255.255.0, /16 is 255.255.0.0, /26 is 255.255.255.192.

Two devices share a network when their network bits match under matching masks. Apply the mask, compare the network portions, done. With mask 255.255.255.0, the first three octets are the network:

Device	Address	Network portion (/24)	Same as the caster desk?
Caster desk	192.168.20.31	192.168.20	-
Scoreboard server	192.168.20.25	192.168.20	Yes: direct delivery through the switch
Player console	192.168.10.31	192.168.10	No: traffic goes through the gateway

Notice the trap: the console's last octet matches the caster desk exactly, yet it is a different network. The only test is the mask.

The /26 surprise

Masks other than /24 break networks in unexpected places. Under 255.255.255.192 (/26), the last octet splits into four blocks: 0-63, 64-127, 128-191, 192-255. A laptop at 192.168.10.140 with a /26 mask computes its network as 192.168.10.128-191, so a gateway at 192.168.10.1 looks off-network and everything beyond a few neighbors fails. This exact case appears in the practice clinic below.

Step-by-step: building the tournament LAN

1. Finish the design first. Devices, cabling, and network needs decide the topology and settings. Nothing gets plugged in before the plan from 3.1 and 3.2 is settled.
2. Gather real tools. Cabling, a wire stripper, RJ45 connectors, a crimping tool, labels and cable management, the devices themselves, and safety glasses and gloves. Label as you go.
3. Configure the switch. Connect over the console cable and set the password, IP address, and subnet mask through the CLI or the GUI of the management console.
4. Configure the router. It needs an IP address and subnet mask, and it becomes the default gateway every device on the segment points at. No router, no path off the segment.
5. Add wireless. The access point gets an SSID, wireless security settings, an IP address, and a subnet mask.
6. Address the endpoints. Statics for the fixed servers, DHCP for the crowd, every address unique and in range. Then verify, device by device.

Verifying access with ipconfig and ping

Verification has two layers. ipconfig answers "what does this device believe?": its address, mask, and gateway. ping answers "what does the network actually deliver?" by sending ICMP packets to a target address; a connected target answers them. ping 192.168.1.127 tests one thing: can this device reach the device holding 192.168.1.127.

A good sweep pings in widening circles: a neighbor on the segment, the gateway, a device on another segment, an internet address. Where the replies stop tells you where the problem lives. Neighbors answering while the gateway stays silent points at the gateway setting or the mask; raw internet addresses answering while names fail points at DNS.

Practice: Config Clinic

Warm up with three sample questions, then work the clinic. Each case gives three artifacts: segment documentation, the device's address table, and ping or ipconfig evidence. Find the one misconfiguration behind the symptom, then pick the verification that proves the fix.

Three free sample questions

1. Staff segment 192.168.20.0/24, gateway 192.168.20.1, DHCP pool .50-.200. Is 192.168.20.1 a valid static address for the scoreboard server?

Show answer

No. It is in range but not unique: the gateway already holds it. Every LAN address must be unique (EK 3.3.A.2).

2. Both masks are 255.255.255.0. Are 192.168.1.10 and 192.168.2.30 on the same network?

Show answer

No. Under /24, 192.168.1 does not match 192.168.2, so traffic between them goes through the gateway (EK 3.3.B.4).

3. A PC reaches 203.0.113.8 by ping but no website loads by name. Which of the four numbers is the suspect?

Show answer

The DNS server. Connectivity is proven by the raw-address reply; only name resolution is failing (EK 3.3.A.5, 3.3.C.7).

Now the full clinic, shuffled every run: read the evidence, not the order.

One access point, two networks: internal and guest

Most access points can host a guest network beside the internal one: internet access with no path to internal resources. Spectators get connectivity; the scoreboard server stays out of reach. Build it in this order:

1. Internal network first. Create the SSID with a strong password, enable WPA2 or WPA3, disable WPS, and confirm internal devices communicate before touching the guest side.
2. Enable the guest network. Browse to the access point's IP address, log in with the administrator credentials, and turn the guest feature on.
3. Configure the guest side like a real network. A separate SSID, its own strong password, WPA2 or WPA3. Then tighten it: limit the device count, disable access to the internal network, set access hours or session limits, and add a captive portal if guests should accept terms.
4. Verify with a test device. Join the guest SSID: the internet should load and internal resources should not. A guest network that reaches the scoreboard admin page fails verification even though the internet works.

Using AI to draft configurations, safely

Drafting forty static addresses is exactly the tedium an AI assistant is good at, so use one: hand it the segment plan and ask for an address table. Then audit the draft before anything gets typed into a device. Check three things against the documentation: every address unique, every address inside its segment's range, and the plan clear of the gateway address and the DHCP pool. One duplicated gateway address in a confident-looking table takes the caster desk down on game day. AI drafts; the technician verifies with ipconfig and proves it with ping.

Key terms

Static IP address

An address entered manually; must be unique and inside the network range.

DHCP

The service, usually on the router, that leases addresses automatically from a configured pool.

Subnet mask

A run of ones then zeros that splits an address into network bits and host bits.

CIDR notation

Slash shorthand for the mask: /24 = 255.255.255.0, /26 = 255.255.255.192.

Default gateway

The router's address on the segment; the path to other networks and the internet.

ipconfig / ifconfig

Commands that display the device's actual IP configuration, including the MAC address.

ping

Sends ICMP packets to an address to verify the target is reachable and answering.

Guest network

A wireless network granting internet access without access to internal resources.

Frequently asked questions

What is the difference between a static and a dynamic IP address?

A static address is typed in by hand in the device's network settings. A dynamic address is leased automatically by a DHCP server that manages a pool of available addresses.

How do I check my IP address, subnet mask, and gateway?

On Windows, run ipconfig in a terminal. On Mac or Linux, use ifconfig or the network settings screen. The MAC address may be labeled Physical Address, Hardware Address, or Ether Address.

What does a subnet mask actually do?

It marks which bits of the address name the network and which name the host. Ones cover the network bits, zeros cover the host bits. Two devices share a network only when their network bits match under the mask.

What does /24 mean in an address like 192.168.10.0/24?

It is CIDR notation: 24 one-bits in the mask, which is 255.255.255.0. The first three octets are network bits and the last octet is for hosts.

How can I tell if two devices are on the same network?

Apply each device's subnet mask to its address and compare the network portions. Same portion under matching masks means same network and direct delivery; different portions mean traffic goes through the default gateway.

What does the ping command do?

It sends ICMP packets to a specific IP address. If the target is connected and reachable, it answers. A reply proves connectivity to that address; a timeout tells you where to look next.

Websites will not load by name but ping works by address. What is wrong?

The DNS server setting. Raw-address replies prove connectivity, so only name resolution is failing. Point DNS at the documented server and open a site by name to verify.

How do I verify a guest network is set up correctly?

Join it with a test device. The internet should load and internal resources should not. If an internal server answers, isolation failed even though the internet works.

AP is a trademark of the College Board, which was not involved in the production of, and does not endorse, this resource.