So You Want to Set Up a Home Router? Let's Do It Step by Step

 

When Your Router Turns Out to Be a Server: My WTNP Home Network Adventure

Blog #8 - Net with Hiru

I walked into this WTNP practical thinking "how hard can building a home network be?" Turns out - pretty entertaining, actually. Here's the full story of designing a wired + wireless home network in Cisco Packet Tracer, including the moment I accidentally tried to run Wi-Fi off a device that has never broadcast a single radio wave in its life.



The Brief

Design a home network with both wired and wireless devices, configure the home router properly (not just drag-and-drop-and-hope), secure it, and understand why each setting exists - not just click through it.

Simple on paper. Chaotic in practice. Let's go.

Step 1: Placing the Devices ( My First Mistake 😏)

I placed a router, a switch, 3 PCs, a laptop, a smartphone and 2 tablets. Nothing connected wirelessly. No SSID. No radio waves. Nothing.

Turns out - I'd grabbed a Cisco 2901 ISR router from the Routers category, not a Home Wireless Router from Wireless Devices. Rookie move, but an instructive one: enterprise routers route packets, they don't broadcast Wi-Fi. Lesson learned the slightly embarrassing way - swapped it for the actual Home Wireless Router and suddenly the smartphone had something to talk to.

Takeaway: Not everything labeled "router" does the same job. Know your device category before you cable anything.

Step 2: Logging Into the Router - Two Ways In

Once the right router was in place, it was time to log in. My lecturer showed us the "real world" way first:

  1. Open Command Prompt on a connected PC
  2. Type ipconfig
  3. Read the Default Gateway - that's the router's LAN IP
  4. Punch that IP into a browser
  5. Log in with admin / admin

 router login, PC3 accessing router interface



Then  the Packet-Tracer-only shortcut: click the router itself and open its GUI tab directly, no PC or IP needed. Same admin panel, zero cabling required - a nice reminder that this shortcut exists purely because we're in a simulator. In real life, you only ever get option one.

Step 3: Wired Side - Enter the Switch

Two PCs and a laptop, but only 4 LAN ports (and I wanted them free for other things). Enter the switch  connected via its Gigabit port straight into the router's regular LAN port.

Interesting mismatch I didn't expect: the switch's Gig port auto-negotiated down to 100 Mbps because the router's LAN side only supports FastEthernet. No errors, no drama - the link just quietly settled to whatever speed both ends could agree on.

 PC3 ping test



Static IP 192.168.0.2 on one PC, ping to the router's gateway - and there it was, a clean reply. Small moment, oddly satisfying😉.

Step 4: The Wireless Module Plot Twist

Here's where things got genuinely fun. PCs and laptops in Packet Tracer come with wired NICs by default - there's no Wi-Fi built in. To go wireless, you have to:

  1. Power off the device (Packet Tracer won't let you swap hardware on a live machine - very true to real life)
  2. Physically drag the wired module out
  3. Drag a wireless module in
  4. Power back on

 PC and laptop module swap







It felt oddly satisfying - like actually opening up a computer and swapping a card, except nobody's going to complain about static electricity😇.

Step 5: Securing the Network (and Breaking Everything Repeatedly)

This is where the real chaos began.💥

Changing the admin password - straightforward. Set a new password in the Administration tab, save.

Changing the SSID and enabling WPA2-Personal (AES) - also straightforward on the router's side.

[Insert screenshot: SSID change, WPA2 security config]

What wasn't straightforward: every single time I changed something on the router - SSID, password, security mode, even disabling the 5GHz band - every wireless device dropped instantly. Smartphone, tablet, PC, laptop - gone. Every time.💔

At first I thought I'd broken something. Turns out, this is completely expected behavior: any change to the wireless radio config forces the router to reset that service, which invalidates every existing session. It's not a Packet Tracer bug - it's exactly what happens on your actual home router when you change the Wi-Fi password. Everyone in the house loses connection for a second and has to rejoin.

The fix that actually got my smartphone back online:
The SSID and password on the device have to match the router exactly - same SSID spelling, Authentication set to WPA2-PSK (not left on Disabled), Encryption Type set to AES, and the passphrase typed in correctly. Miss any one field, and the device just sits there with a self-assigned 169.254.x.x address, silently failing.



Once I matched every field, it connected instantly. Small config mismatch, big frustration 😓 very on-brand for networking.

Step 6: DHCP — Watching Addresses Change Live

Next, I played with the DHCP scope: changed the starting IP from .100 to .10 and watched what happened to my smartphone.

 before and after IP of smartphone






Here's the subtlety I almost missed: changing the range on the router doesn't instantly update devices that already hold a lease. You have to force a renew , toggle the device to Static and back to DHCP, or disconnect/reconnect - before it actually picks up an address from the new range.

Checked the DHCP Client Table before and after to confirm - a genuinely satisfying way to see DHCP doing its job instead of just trusting it blindly.





Step 7: MAC Filtering - The Final Boss 👿

Last piece: locking down access by hardware address, not just password.

  1. Pulled the smartphone's MAC address straight from the DHCP Client Table
  2. Enabled Wireless MAC Filter on the router
  3. Added the MAC to the block list
  4. Saved, then tried renewing the smartphone's IP

 wireless MAC filter



The smartphone couldn't get an address anymore, even with the correct SSID and password. Its entry vanished from the DHCP Client Table entirely. It was a good reminder that Wi-Fi security isn't just "one password fits all" - you can layer authentication (WPA2) with hardware-level filtering (MAC) for defense in depth. Also a good reminder that MAC addresses can be spoofed in the real world, so this layer alone isn't bulletproof , but combined with a strong password, it raises the bar.

What I'd Tell Past-Me

  • Check your device category before placing it - a router isn't a router isn't a router.
  • Any wireless setting change = mass disconnect. Don't panic, just reconnect everyone with matching credentials.
  • DHCP changes need a renew to actually show up on existing clients.
  • Security is layered - WPA2/AES handles encryption and authentication, MAC filtering adds a hardware-level checkpoint on top.

This lab turned "how does my home Wi-Fi actually work" from a black box into something I can now trace end to end - SSID, encryption, DHCP leases, MAC filtering, all the way down to a ping reply on a terminal. Genuinely one of the more hands-on, "oh THAT'S why that happens" modules so far.

Next up: probably diving deeper into wireless troubleshooting or moving toward enterprise-grade AP configuration. Stay tuned.

Comments

Post a Comment

Popular posts from this blog

Nervous, Excited, and Proud — My pfSense Configuration Journey

Image
  My pf Sense Configuration Journey    .🖉 When my lecturer told us we would be setting up a firewall using pfSense, I honestly had no idea what I was getting into. This is the story of how I went from zero experience to successfully logging into a pfSense dashboard and everything that went wrong (and right) along the wa y. Starting Fresh: VMware for the First Time The first thing I had to do was set up a virtual machine environment. I had heard about VMware before, but I had never actually used it. My go-to had always been VirtualBox so even before I touched pfSense, I was already stepping into unfamiliar territory. Installing VMware was a new experience on its own. The interface looked different from what I was used to, and I had to take some time to get comfortable with how it worked. It was a small hurdle, but it reminded me that in this module, almost everything would be new. Installing pfSense: More Steps Than I Expected Once VMware was ready, it was time to...
Read more

NetWithHiru-Blog-Series-01

Image
  My First Networking Project: Connecting Accounts and Delivery Departments Introduction This project focuses on the design and implementation of an inter-departmental network using Cisco Packet Tracer. The network connects two departments, Accounts and Delivery, ensuring efficient communication through proper IP addressing and routing configurations. The project demonstrates fundamental networking concepts such as subnetting, device configuration, and connectivity testing in a simulated environment. Objectives To design a simple network connecting the Accounts and Delivery departments To configure IP addresses, subnet masks, and default gateways using the 192.168.40.0 network To implement routing between two different networks using a router To connect all devices using appropriate network cables To verify network connectivity between departments using the ping command To gain practical experience in using Cisco Packet Tracer for network s...
Read more

Ethical Hacking Journey

Image
Blog #3 - I Installed Kali Linux Before My Lecturer Even Mentioned It One big reason I got into this path is Wenura Mendis sir and his streaming channel Vibernet Sreaming . Watching his content opened my eyes to the world of ethical hacking and cybersecurity in a way that felt real and practical not just theory. It inspired me to stop watching and start doing. So when I enrolled in the Cisco Networking Academy Ethical Hacking course, I didn't want to just follow along in class. I wanted to get my hands dirty before anyone told me to. That's where this whole Kali Linux journey began. "I didn't wait to be taught. I broke things, fixed them, broke them again - and learned more than any classroom could have given me in a single week." If you've been following my blog series, you already know I don't wait around. The moment I enrolled in the Cisco Networking Academy Ethical Hacking course, I knew I needed Kali Linux on my machine. Not next week. Not when ...
Read more