Week 8 · Lab

LAB: Wireless Configuration

In this hands-on lab you configure a SOHO wireless router so that two wired PCs and three wireless clients share one secure network, and a guest device gets Internet access on an isolated guest SSID. You will set the SSID, band, channel, and a WPA2/WPA3 pre-shared key, enable DHCP, and prove the whole path works — then break it on purpose to see how it fails.

CCNA 200-301 Domain 2.0 & 4.0 Wireless Verified 2026-10-11
Part 1

Objective and requirements

The goal: two wired PCs and three wireless clients share one secure network, and one guest device reaches the Internet on an isolated guest SSID. Every value — SSID, band, channel, security mode, pre-shared key, DHCP scope — is decided on paper before the GUI is touched.

Plan

SSID, band, channel, security mode, PSK, and DHCP scope — all written down first.

Build

Add the router and clients; cable the WAN and LAN sides.

Prove

Check DHCP with ipconfig, then the path with ping.

Requirements

Model note Consumer routers differ. Packet Tracer’s classic WRT300N is 2.4 GHz only; newer emulated routers expose both 2.4 GHz and 5 GHz radios and may offer WPA3. If your model lacks 5 GHz or WPA3, configure the options it does have and note it — the procedure is identical.
Part 2

Topology and addressing plan

Build this in Packet Tracer (or your simulator) before you type a single setting. Wired clients connect to the router’s LAN switch ports; wireless clients associate over 802.11 to the SSID. The guest device joins a separate, isolated SSID that reaches the Internet but not the internal LAN.

Internet / ISP Cable modem Wireless router SSID: Net-SOHO PC-A wired PC-B wired Laptop-1 wireless Phone-2 wireless Tablet-3 wireless Guest phone SSID: Net-Guest LAN cable LAN cable 802.11 isolated

The plan

ItemValueWhy
Primary SSIDNet-SOHOClear, non-identifying network name. Avoid names that reveal the owner or address.
Band / radio2.4 GHz and 5 GHz2.4 GHz has longer range; 5 GHz has more channels and less interference. Offer both.
Channel (2.4 GHz)6Channels 1, 6, and 11 are the only non-overlapping choices in 2.4 GHz. Pick the one with least interference.
Channel width (2.4 GHz)20 MHz20 MHz is more forgiving in a crowded 2.4 GHz band; 40 MHz increases interference risk.
Security modeWPA2-Personal (AES) or WPA3-PersonalStrong, current encryption. Never leave a network Open or on WEP.
Pre-shared key (PSK)CCNA-Lab-PassA passphrase of at least 12 characters mixing cases, digits, and symbols. Real deployments should be longer and unique.
LAN / gateway address192.168.0.1The router is the default gateway and DHCP server for the internal network.
Subnet mask255.255.255.0 (/24)A single class-C-sized LAN, ample for a SOHO.
DHCP scope (LAN)192.168.0.100 – 192.168.0.199100 addresses for clients, leaving the lower range free for static devices.
DNS handed to clients192.168.0.1The router forwards DNS to the ISP. (A public resolver such as 8.8.8.8 is an alternative.)
Guest SSIDNet-GuestSeparate name so the guest key is never the main key.
Guest security / keyWPA2-Personal / Guest-Pass-2026Guests are still protected, but on their own credentials.
Guest isolationEnabledGuests reach the Internet but cannot reach Net-SOHO clients.
Guest scope192.168.1.100 – 192.168.1.199 (gateway 192.168.1.1)A separate subnet keeps guest traffic apart from the LAN.

Why only channels 1, 6 and 11?

In the 2.4 GHz band each channel is 22 MHz wide but the channels are spaced only 5 MHz apart, so neighbours overlap almost completely. Channels 1, 6 and 11 are the only three that do not overlap each other. Select one below to see the overlap.

2.4 GHz channel plan · select the channel
1 Channel

Part 3

Tasks: step by step

Work through the steps in order. The stepper gives you the purpose of each one; the full command listings follow it.

Task stepper · step through the lab

Step 2 — Build the topology

  1. Open Packet Tracer. Drag a Wireless Router onto the workspace and name it Net-SOHO-R1.
  2. Add a Cable modem (or a Device → Cloud acting as the ISP). On the router, the WAN/Internet port is usually coloured differently from the four LAN ports.
  3. Connect the modem to the router’s Internet/WAN port with a straight-through cable, and the modem’s other side to the ISP/Internet cloud.
  4. Add PC-A and PC-B and connect each to a LAN port on the router with a straight-through cable.
  5. Add a Laptop, a Smartphone, and a Tablet (or a second and third laptop). These use their built-in wireless adapter — no cable.
  6. Power everything on. The router boots with its factory default WLAN (often an open SSID like Default or linksys).
Finding the web GUI On a real SOHO router, connect a PC by cable and browse to the factory default gateway (often 192.168.0.1 or 192.168.1.1). In Packet Tracer, click the wireless router and open the GUI tab; it is the same configuration, just embedded. The default login is printed on the device label (commonly admin/admin) — and changing it is itself a required hardening step.

Step 3 — Create the SSID on 2.4 GHz and 5 GHz

Open the router’s web GUI and go to the Wireless (or Wireless → Basic Wireless Settings) page.

  1. Set Network Mode to a mixed mode that serves current clients, for example Mixed 802.11n/ac/ax (availability depends on the model).
  2. For the 2.4 GHz radio, set SSID to Net-SOHO, select Channel 6, and set Channel Width to 20 MHz.
  3. If the router has a 5 GHz radio, set its SSID to Net-SOHO-5G (or the same Net-SOHO if you want a single name) and let it auto-select a clean 5 GHz channel (for example 36).
  4. Leave SSID Broadcast (SSID Broadcast Enabled) on for the lab. Hiding the SSID is not a security control — clients still transmit it — but it can be a small lab exercise later.
  5. Click Save Settings. The radio restarts and the new SSID appears.
! Values set on the Wireless page
Network Mode      : Mixed 802.11n / ac / ax
SSID (2.4 GHz)    : Net-SOHO
Channel           : 6
Channel Width     : 20 MHz
SSID (5 GHz)      : Net-SOHO-5G
SSID Broadcast    : Enabled

Step 4 — Set security mode and the PSK

Go to Wireless → Wireless Security. This is the step that turns an open network into a protected one.

  1. Security Mode: choose WPA2-Personal (called WPA2/WPA Mixed Personal on some models). If the model supports WPA3-Personal, prefer WPA3-Personal or a WPA2/WPA3 Mixed mode so old clients still connect.
  2. Encryption: AES (do not select TKIP; it is obsolete).
  3. Passphrase / Pre-shared Key: CCNA-Lab-Pass. Match the case exactly; WPA-Personal passphrases are case-sensitive.
  4. Repeat for the 5 GHz radio if it is configured separately (the same or a different PSK).
  5. Click Save Settings. Any client that was connected on the open SSID is dropped until it re-authenticates with the key.
Wireless client Net-SOHO router association + PSK (CCNA-Lab-Pass) accept + 4-way handshake (derives pairwise key) Traffic is encrypted with the derived key. A wrong PSK fails the handshake.
Exam tip — WPA2 vs WPA3 WPA2-Personal uses a pre-shared key with AES-CCMP. WPA3-Personal replaces the pre-shared-key exchange with SAE (Simultaneous Authentication of Equals), which resists offline dictionary attacks. If a question asks for the strongest personal/PSK option, the answer is WPA3.

Step 5 — Add the guest network

A guest network gives visitors Internet access without exposing the internal LAN. Look for a Guest Network page (sometimes under Wireless or Administration).

  1. Enable the guest network.
  2. Set the guest SSID to Net-Guest.
  3. Choose the band — 2.4 GHz is fine for guests and reaches further.
  4. Set guest Security to WPA2-Personal with the key Guest-Pass-2026.
  5. Enable Guest Isolation / AP Isolation so guest clients cannot reach Net-SOHO devices or each other.
  6. If the router supports a guest DHCP scope, confirm it uses a separate subnet, here 192.168.1.0/24 with gateway 192.168.1.1.
  7. Save settings.
Security reason for isolation Without isolation, a compromised guest device becomes a launch pad into your internal network. Guest isolation is a segmentation control: the guest VLAN/subnet can reach the Internet but not the trusted LAN.

Step 6 — Verify wireless clients obtain DHCP

Now join each wireless client to Net-SOHO with the key and confirm it receives an address from the scope.

  1. On the laptop, open Desktop → PC Wireless (or the wireless icon), click Connect, select the SSID Net-SOHO, and enter the PSK CCNA-Lab-Pass.
  2. Confirm the client shows Associated / Connected. If it does not, the PSK or security mode is mismatched (see Troubleshooting).
  3. Open Desktop → Command Prompt and run ipconfig.
C:\> ipconfig

Wireless LAN adapter Wireless Network Connection:
   Connection-specific DNS Suffix  . :
   IPv4 Address. . . . . . . . . . . : 192.168.0.102
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1

C:\> ipconfig /all
Wireless LAN adapter Wireless Network Connection:
   Physical Address. . . . . . . . . : 00:11:22:33:44:55
   DHCP Enabled. . . . . . . . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.0.102
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DNS Servers . . . . . . . . . . . : 192.168.0.1

Check the four things the exam always asks for: a valid IPv4 address inside the scope (192.168.0.x), the correct subnet mask, a default gateway (192.168.0.1), and a DNS server. An address in the 169.254.x.x range means DHCP failed — that is an APIPA self-assigned address.

Exam tip — APIPA 169.254.0.0/16 is the link-local range Windows uses when a DHCP request gets no reply. Seeing it on a client is the fastest clue that the client has no working DHCP path (no SSID yet, wrong subnet, or an exhausted scope).

Step 7 — Verify the Internet path with ping

Association and an address only prove the wireless link is healthy. To prove the full path, test the gateway, then a public address, then a name.

! 1. The gateway (the router itself)
C:\> ping 192.168.0.1
Reply from 192.168.0.1: bytes=32 time=2ms TTL=255

! 2. A public IP beyond the ISP - tests routing and NAT
C:\> ping 8.8.8.8
Reply from 8.8.8.8: bytes=32 time=20ms TTL=128
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)

! 3. A name - tests DNS as well as connectivity
C:\> ping www.cisco.com
Pinging www.cisco.com [192.0.2.10] with 32 bytes of data:
Reply from 192.0.2.10: bytes=32 time=24ms TTL=128
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)

Read the three tests as a ladder: gateway success means Layer 2/3 to the router works; public-IP success means the WAN link, default route, and NAT work; name success means DNS works. If step 1 works but step 2 fails, the fault is on the WAN side; if step 2 works but step 3 fails, DNS is misconfigured.

Part 4

Verify: what good looks like

When the lab is complete you should see all of the following. Use the checklist as your own pass sheet.

Lab checklist · tick each item as you confirm it

CheckCommandWhat you should see
SSID is visibleWireless client scanNet-SOHO (and Net-SOHO-5G, Net-Guest if your model supports them).
Clients associateClient statusConnected / Associated after the key is entered.
DHCP worksipconfigAn address in 192.168.0.100-199, mask 255.255.255.0, gateway and DNS 192.168.0.1.
Gateway reachableping 192.168.0.1Four replies, 0% loss.
Internet reachableping 8.8.8.8Four replies, 0% loss.
Name resolution worksping www.cisco.comThe name resolves to an address and replies come back.
Guest is isolatedGuest device pings a LAN clientThe ping fails while Internet access still works.
Part 5

Troubleshooting guide

Wireless faults cluster around four themes: the SSID is not visible, the signal is weak, the passphrase is wrong, or DHCP fails. Work up the ladder — the first step that fails is where the fault lives.

Symptom → likely cause · select the symptom

SymptomLikely causeFix
No SSID visibleWrong band or channel width; radio disabled; SSID hidden; client too far awayConfirm the radio is enabled and broadcasting; match the client’s band (2.4 vs 5 GHz); temporarily set 20 MHz and channel 6; move closer.
SSID visible but weak / dropsPlacement (walls, metal, distance); interference on the channelMove the router to a central, elevated position; change to a less crowded channel (1, 6, or 11); prefer 5 GHz at close range.
Association fails / wrong keyPSK mismatch (case-sensitive); security mode mismatch (WPA2 vs WPA3); encryption set to TKIPRe-enter CCNA-Lab-Pass exactly; set both ends to WPA2/WPA3-Personal with AES; avoid TKIP.
Associated but no IPv4 / 169.254.x.xDHCP scope disabled or exhausted; wrong subnet/gateway; client set to a static addressEnable DHCP and widen the scope; verify the gateway is 192.168.0.1; set the client back to DHCP.
Has IPv4 but no InternetWAN/uplink down; missing default route; DNS not setCheck the modem link; confirm the router WAN obtained an address; verify DNS is handed out (or ping 8.8.8.8 to isolate DNS).
One client cannot joinMAC filtering; band-only client; saved wrong profileRemove the MAC filter; ensure the client supports the SSID’s band and mode; delete and reconnect the wireless profile.
Debugging order for wireless Go up the ladder: (1) is the SSID visible? (2) does association succeed? (3) does the client get a DHCP address? (4) can it ping the gateway? (5) can it ping 8.8.8.8? (6) does DNS resolve a name? The first step that fails is where the fault lives.
Part 6 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Sources

Sources & references

  1. Cisco. CCNA (200-301) Exam Topics, Domain 2.0 (Network Access: wireless) and 4.0 (IP Services: DHCP, NAT). cisco.com.
  2. IEEE. IEEE 802.11 (Wireless LAN MAC and PHY specifications), including the 2.4 GHz and 5 GHz channel plans. standards.ieee.org.
  3. Wi-Fi Alliance. Discover Wi-Fi: Security (WPA2 and WPA3, SAE). wi-fi.org.
  4. Cisco Networking Academy. Packet Tracer (simulator download). netacad.com/courses/packet-tracer.

Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.