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.
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
- Cisco Packet Tracer (free) — it includes a Wireless Router (for example the WRT300N or a newer dual-band model) with the same web GUI you would use on real hardware. Download from netacad.com/courses/packet-tracer.
- Or physical gear: a SOHO wireless router, two PCs (or laptops), and at least one phone/tablet-class client (in the lab a laptop can stand in for a phone).
- Ethernet cables for the wired clients and for the WAN/uplink to the modem.
- Wireless clients need a wireless NIC. In Packet Tracer, delete the wired NIC and add a WPC300N-class wireless module, or use the built-in wireless of laptops and smartphones.
- No console cable is required for this lab — a SOHO router is configured through its web GUI, reachable at its factory default gateway address on a LAN port.
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.
The plan
| Item | Value | Why |
|---|---|---|
| Primary SSID | Net-SOHO | Clear, non-identifying network name. Avoid names that reveal the owner or address. |
| Band / radio | 2.4 GHz and 5 GHz | 2.4 GHz has longer range; 5 GHz has more channels and less interference. Offer both. |
| Channel (2.4 GHz) | 6 | Channels 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 MHz | 20 MHz is more forgiving in a crowded 2.4 GHz band; 40 MHz increases interference risk. |
| Security mode | WPA2-Personal (AES) or WPA3-Personal | Strong, current encryption. Never leave a network Open or on WEP. |
| Pre-shared key (PSK) | CCNA-Lab-Pass | A passphrase of at least 12 characters mixing cases, digits, and symbols. Real deployments should be longer and unique. |
| LAN / gateway address | 192.168.0.1 | The router is the default gateway and DHCP server for the internal network. |
| Subnet mask | 255.255.255.0 (/24) | A single class-C-sized LAN, ample for a SOHO. |
| DHCP scope (LAN) | 192.168.0.100 – 192.168.0.199 | 100 addresses for clients, leaving the lower range free for static devices. |
| DNS handed to clients | 192.168.0.1 | The router forwards DNS to the ISP. (A public resolver such as 8.8.8.8 is an alternative.) |
| Guest SSID | Net-Guest | Separate name so the guest key is never the main key. |
| Guest security / key | WPA2-Personal / Guest-Pass-2026 | Guests are still protected, but on their own credentials. |
| Guest isolation | Enabled | Guests reach the Internet but cannot reach Net-SOHO clients. |
| Guest scope | 192.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.
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.
Step 2 — Build the topology
- Open Packet Tracer. Drag a Wireless Router onto the workspace and name it Net-SOHO-R1.
- 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.
- 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.
- Add PC-A and PC-B and connect each to a LAN port on the router with a straight-through cable.
- Add a Laptop, a Smartphone, and a Tablet (or a second and third laptop). These use their built-in wireless adapter — no cable.
- Power everything on. The router boots with its factory default WLAN (often an open SSID like
Defaultorlinksys).
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.
- Set Network Mode to a mixed mode that serves current clients, for example
Mixed 802.11n/ac/ax(availability depends on the model). - For the 2.4 GHz radio, set SSID to
Net-SOHO, select Channel 6, and set Channel Width to20 MHz. - If the router has a 5 GHz radio, set its SSID to
Net-SOHO-5G(or the sameNet-SOHOif you want a single name) and let it auto-select a clean 5 GHz channel (for example36). - 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.
- 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.
- Security Mode: choose
WPA2-Personal(called WPA2/WPA Mixed Personal on some models). If the model supports WPA3-Personal, preferWPA3-Personalor aWPA2/WPA3 Mixedmode so old clients still connect. - Encryption:
AES(do not select TKIP; it is obsolete). - Passphrase / Pre-shared Key:
CCNA-Lab-Pass. Match the case exactly; WPA-Personal passphrases are case-sensitive. - Repeat for the 5 GHz radio if it is configured separately (the same or a different PSK).
- Click Save Settings. Any client that was connected on the open SSID is dropped until it re-authenticates with the key.
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).
- Enable the guest network.
- Set the guest SSID to
Net-Guest. - Choose the band — 2.4 GHz is fine for guests and reaches further.
- Set guest Security to
WPA2-Personalwith the keyGuest-Pass-2026. - Enable Guest Isolation / AP Isolation so guest clients cannot reach
Net-SOHOdevices or each other. - If the router supports a guest DHCP scope, confirm it uses a separate subnet, here
192.168.1.0/24with gateway192.168.1.1. - Save settings.
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.
- On the laptop, open Desktop → PC Wireless (or the wireless icon), click Connect, select the SSID
Net-SOHO, and enter the PSKCCNA-Lab-Pass. - Confirm the client shows Associated / Connected. If it does not, the PSK or security mode is mismatched (see Troubleshooting).
- 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.
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.
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.
| Check | Command | What you should see |
|---|---|---|
| SSID is visible | Wireless client scan | Net-SOHO (and Net-SOHO-5G, Net-Guest if your model supports them). |
| Clients associate | Client status | Connected / Associated after the key is entered. |
| DHCP works | ipconfig | An address in 192.168.0.100-199, mask 255.255.255.0, gateway and DNS 192.168.0.1. |
| Gateway reachable | ping 192.168.0.1 | Four replies, 0% loss. |
| Internet reachable | ping 8.8.8.8 | Four replies, 0% loss. |
| Name resolution works | ping www.cisco.com | The name resolves to an address and replies come back. |
| Guest is isolated | Guest device pings a LAN client | The ping fails while Internet access still works. |
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 | Fix |
|---|---|---|
| No SSID visible | Wrong band or channel width; radio disabled; SSID hidden; client too far away | Confirm 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 / drops | Placement (walls, metal, distance); interference on the channel | Move 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 key | PSK mismatch (case-sensitive); security mode mismatch (WPA2 vs WPA3); encryption set to TKIP | Re-enter CCNA-Lab-Pass exactly; set both ends to WPA2/WPA3-Personal with AES; avoid TKIP. |
| Associated but no IPv4 / 169.254.x.x | DHCP scope disabled or exhausted; wrong subnet/gateway; client set to a static address | Enable DHCP and widen the scope; verify the gateway is 192.168.0.1; set the client back to DHCP. |
| Has IPv4 but no Internet | WAN/uplink down; missing default route; DNS not set | Check 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 join | MAC filtering; band-only client; saved wrong profile | Remove the MAC filter; ensure the client supports the SSID’s band and mode; delete and reconnect the wireless profile. |
Review
Check what you have learned with these review questions.
Sources & references
- Cisco. CCNA (200-301) Exam Topics, Domain 2.0 (Network Access: wireless) and 4.0 (IP Services: DHCP, NAT). cisco.com.
- IEEE. IEEE 802.11 (Wireless LAN MAC and PHY specifications), including the 2.4 GHz and 5 GHz channel plans. standards.ieee.org.
- Wi-Fi Alliance. Discover Wi-Fi: Security (WPA2 and WPA3, SAE). wi-fi.org.
- 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.