8.5 Module Quiz – Build A Small Network: Can You Pass The Challenge Before It Expire?

Ever tried to set up a tiny network just to see how the pieces fit together?
Maybe you’ve watched a video where a handful of switches, a router, and a couple of PCs magically talk to each other. Or perhaps the lab you’re staring at in the 17.8.5 module quiz looks like a puzzle you’d rather not solve.

Either way, you’re about to build a small network from scratch, and the good news is you don’t need a data‑center to do it. A few cables, a couple of devices, and a bit of curiosity are enough. Let’s walk through the whole thing—what it is, why you should care, how to actually pull it off, and the pitfalls that trip most beginners Surprisingly effective..

What Is the 17.8.5 Module Quiz – Build a Small Network?

In plain English, the 17.8.Plus, 5 module quiz asks you to design, configure, and verify a miniature LAN that demonstrates core networking concepts. Think of it as a hands‑on checkpoint in a Cisco‑style curriculum: you’ll be wiring devices, assigning IP addresses, setting up a basic routing protocol, and proving that traffic can flow between subnets.

The Core Pieces

• Two or three end devices (PCs or laptops) that act as hosts.
• A switch to create a local Ethernet segment.
• A router to connect two different subnets.
• Optional: a server for DNS or DHCP, if the lab calls for it.

That’s it. The “module” part just means the lab is packaged with a set of objectives and a quiz that checks whether you’ve met them Most people skip this — try not to..

The Learning Goal

You’re not just plugging cables for the sake of it. The exercise forces you to think about:

• IP addressing schemes (subnetting, default gateways)
• Layer‑2 vs. Layer‑3 functions
• Basic routing (static or RIP)
• Verification tools (ping, traceroute, show commands)

If you can get this small network humming, you’ve got the foundation for anything bigger The details matter here..

Why It Matters / Why People Care

Real‑world networks start small. That's why a coffee shop’s Wi‑Fi, a home office, or a boutique retail POS system all begin as a handful of devices. Mastering the 17.Because of that, 8. 5 lab gives you a sandbox where you can make mistakes without breaking a production environment.

The Practical Payoff

• Job interviews: “Tell me about a time you built a network from scratch.” You’ll have a concrete story.
• Certification prep: Most CCNA‑style exams include a hands‑on lab that mirrors this exact scenario.
• Confidence boost: Nothing feels better than typing show ip route and actually seeing your routes appear.

What Goes Wrong Without It?

Skip the fundamentals and you’ll end up with “it works on my machine” syndrome. Plus, the result? Which means you might assign overlapping subnets, forget a default gateway, or mis‑configure a switch port as a trunk when it should be access. No connectivity, endless ping timeouts, and a lot of frustration The details matter here..

How It Works (or How to Do It)

Below is a step‑by‑step walk‑through that covers everything from the physical layout to the final verification. Feel free to adapt the IP scheme to your own lab, but keep the logic the same Took long enough..

1. Gather Your Gear

• Two PCs (or virtual machines) – call them PC‑A and PC‑B.
• One switch – any unmanaged 5‑port switch will do.
• One router – a Cisco 1841, a virtual router (GNS3/Packet Tracer), or even a cheap home router in “router mode”.
• Cables – straight‑through Ethernet (Cat5e or better).

2. Physical Connections

1. Connect PC‑A to port 1 on the switch.
2. Connect PC‑B to port 2 on the switch.
3. Connect the switch’s uplink (port 5, for example) to the router’s Gig0/0 interface.

If you’re using a virtual lab, just drag the links in the topology view.

3. Define the IP Scheme

We’ll use two subnets so the router has something to route between Simple, but easy to overlook..

4. Configure the Router

On a Cisco‑style CLI:

Router> enable
Router# configure terminal
Router(config)# interface Gig0/0
Router(config-if)# ip address 192.168.10.1 255.255.255.0
Router(config-if)# no shutdown
Router(config-if)# exit

Router(config)# interface Gig0/1
Router(config-if)# ip address 192.1 255.In practice, 255. In practice, 20. Think about it: 168. 255.

If you prefer static routing (the simplest for this lab), you actually don’t need to add anything else—each directly‑connected network is automatically in the routing table.

### 5. Set Up the PCs

On Windows:

```powershell
netsh interface ip set address "Ethernet" static 192.168.10.2 255.255.255.0 192.168.10.1

On Linux/macOS:

sudo ifconfig eth0 192.168.10.2 netmask 255.255.255.0
sudo route add default gw 192.168.10.1

Do the analogous steps for PC‑B, swapping the 10‑subnet for the 20‑subnet That's the part that actually makes a difference..

6. Verify Layer‑2 Connectivity

First, make sure the switch is passing frames.

• On PC‑A, run ping 192.168.10.1.
• On PC‑B, run ping 192.168.20.1.

Both should reply. If not, double‑check cable placement and that the switch ports aren’t disabled.

7. Verify Layer‑3 Routing

Now test cross‑subnet traffic.

• From PC‑A, ping 192.168.20.2.
• From PC‑B, ping 192.168.10.2.

If the pings succeed, the router is correctly forwarding packets.

8. Optional: Add a Simple Routing Protocol

If the quiz expects you to demonstrate a dynamic protocol, enable RIP (very easy).

Router(config)# router rip
Router(config-router)# version 2
Router(config-router)# network 192.168.10.0
Router(config-router)# network 192.168.20.0
Router(config-router)# no auto-summary
Router(config-router)# exit

Now run show ip route on the router. You should see the two networks listed as RIP‑learned routes No workaround needed..

9. Test with Traceroute

From PC‑A:

tracert 192.168.20.2   # Windows
traceroute 192.168.20.2  # Linux/macOS

You should see two hops: the router’s 10‑subnet address, then the destination PC. If you see a “* * * Request timed out” after the first hop, something’s still blocking traffic—maybe an ACL you forgot to clear.

10. Clean Up

When the quiz is over, shut down the interfaces you used (good habit):

Router(config)# interface Gig0/0
Router(config-if)# shutdown
Router(config-if)# exit
Router(config)# interface Gig0/1
Router(config-if)# shutdown

Common Mistakes / What Most People Get Wrong

1. Using a crossover cable between PC and switch – modern switches are auto‑MDIX, but many older models still need straight‑through. The result? No link lights.
2. Overlapping subnets – putting both PCs in 192.168.10.0/24 looks fine until the router can’t differentiate them.
3. Forgetting the “no shutdown” command – the interface stays administratively down, and the router never learns the network.
4. Mixing up default gateways – pointing PC‑A to 192.168.20.1 will send its traffic straight to the wrong subnet, causing immediate ping failures.
5. Skipping verification – it’s tempting to assume everything works after you type the commands. A quick show ip interface brief saves a lot of head‑scratching later.

Practical Tips / What Actually Works

• Label your cables before you plug anything in. A simple “A‑to‑Switch” tag prevents the classic “I swapped ports” panic.
• Use the show running-config command after each major change. It’s a quick sanity check that the IP address you typed actually stuck.
• Keep a notebook of the IP scheme you choose. When you’re juggling multiple labs, it’s easy to reuse an address by accident.
• put to work the router’s console LED – a solid green usually means the interface is up; amber can indicate a problem.
• If you’re in a virtual lab, snapshot the topology after you get the basic connectivity right. That way you can roll back if a dynamic routing experiment goes sideways.
• Don’t ignore the ARP table. On a PC, arp -a shows which MAC address the router resolved to. If you see “ff‑ff‑ff‑ff‑ff‑ff”, the ARP request never got answered—often a sign of a mis‑cabled link.

FAQ

Q1: Do I really need a router for a “small network”?
A: If all devices share the same subnet, a switch alone suffices. The router is required here to demonstrate inter‑subnet routing, which is a core CCNA objective Not complicated — just consistent. Nothing fancy..

Q2: Can I replace the router with a Layer‑3 switch?
A: Yes, a L3 switch can perform the same routing functions. Just configure SVIs (Switched Virtual Interfaces) for each VLAN/subnet and enable routing.

Q3: What if my switch is managed and I accidentally set a port to trunk?
A: Trunk ports expect VLAN tags. If you connect an untagged PC to a trunk, the switch will drop the frames. Change the port back to “access” mode for that VLAN Worth keeping that in mind..

Q4: How do I verify that RIP is actually advertising routes?
A: On the router, run show ip protocols – you’ll see the networks listed under “Routing for Protocols”. show ip rip database shows the RIP routing table entries.

Q5: Is DHCP required for this lab?
A: Not for the basic 17.8.5 quiz. Static IPs keep things transparent. If the exam asks for DHCP, configure a pool on the router (ip dhcp pool LAN10 etc.) and set the PCs to obtain an address automatically.

Building a tiny network might feel like a lot of steps at first, but once the cables click and the pings start flowing, the “aha!Keep the lab saved, tweak the IP ranges, maybe add a second router, and you’ll have a reusable sandbox for all the future networking puzzles you’ll face. You’ve just taken a concept that lives in textbooks and turned it into something you can see, touch, and troubleshoot. ” moment is worth every minute. Happy wiring!

Going Beyond the Basics

Now that the core of the lab is stable, you can extend it in several fun ways:

1. Add a second router
   • Create a second subnet (192.168.2.0/24).
   • Connect the two routers with a serial or Ethernet link.
   • Enable RIP on both routers and add the new network to the RIP process.
   • Verify reachability from a PC in the new subnet to the original subnet.

2. Introduce a firewall or ACL
   • On the first router, configure a simple access‑list that denies traffic from the 192.168.1.0/24 subnet to the 192.168.2.0/24 subnet.
   • Observe how pings now fail and how the ACL is logged (if you enable logging).

3. Use a Layer‑3 switch
   • If you have one, replace the router with an L3 switch and configure VLAN interfaces (SVIs).
   • Enable inter‑VLAN routing and compare the performance and configuration simplicity with the router.

4. Simulate a WAN link
   • Use a serial interface or a DMVPN‑like setup in the emulator to connect to a remote lab.
   • Practice configuring OSPF or EIGRP for dynamic routing over the WAN.

Common Pitfalls and How to Avoid Them

Checklist Before You Submit

• [ ] All PCs have the correct IP, subnet mask, and default gateway.
• [ ] Each router’s interfaces are up (show ip interface brief).
• [ ] RIP is enabled on both routers, and the correct networks are advertised (show ip protocols).
• [ ] All pings between PCs succeed.
• [ ] The show ip route table contains entries for both subnets on each router.
• [ ] You’ve documented every step in a lab notebook or digital log.

Final Thoughts

Building this miniature network from scratch forces you to confront every foundational concept that will appear on the CCNA exam: IP addressing, subnetting, interface configuration, static and dynamic routing, and basic troubleshooting. By walking through each command and verifying the results, you convert abstract theory into tangible, observable behavior Simple, but easy to overlook..

Not obvious, but once you see it — you'll see it everywhere.

The moment a ping finally succeeds after a misconfiguration is fixed is more rewarding than any textbook diagram—because you know the problem existed and you solved it yourself. Keep experimenting: swap the RIP version, try EIGRP, or even add network security features. Each variation deepens your understanding and prepares you for the unpredictable scenarios you’ll face in the real world.

So grab those cables, fire up your emulator, and let the packets flow. Now, your CCNA journey is just beginning, and every successful lab is a step closer to mastery. Happy networking!

Adding Redundancy with a Backup Link

Once you’ve confirmed basic connectivity, it’s a good idea to simulate a fail‑over scenario. Redundant paths are a staple of real‑world networks, and the CCNA exam often tests your ability to configure them.

1. Create a second serial link between the two routers (or, if you’re using a DMVPN hub‑spoke topology, add an extra spoke) But it adds up..

2. Assign a different subnet to the new link, e.g., 10.0.0.0/30.

3. Enable RIP on the new interfaces just as you did for the primary link.

4. Verify that both routes appear in the routing tables:

   R1#show ip route rip
   R2#show ip route rip
   

   You should see two entries for the remote network—one via the primary link and one via the backup link, each with the same administrative distance (120) but different metric values.

5. Test fail‑over by shutting down the primary serial interface on one router:

   R1(config)#interface Serial0/0/0
   R1(config-if)#shutdown
   

   After a few seconds, the routing protocol will recalculate, and the backup path will become active. Ping from PC‑A to PC‑B again; the traffic should still flow, confirming that redundancy works.

6. Bring the primary link back up and watch the metric‑based convergence return the traffic to the preferred path.

Introducing a Simple ACL for Security

Even in a tiny lab, you can demonstrate how access‑control lists (ACLs) restrict traffic—an essential skill for the CCNA Security objectives.

Goal: Block all HTTP (port 80) traffic from the 192.168.1.0/24 network to the 192.168.2.0/24 network while allowing everything else.

1. Create a standard numbered ACL on R1 (the edge router for the 192.168.1.0 network):

   R1(config)#access-list 101 deny tcp 192.So naturally, 168. 1.That said, 0 0. 0.So naturally, 0. Also, 255 192. So naturally, 168. 2.Plus, 0 0. 0.0.
   
   

2. Apply the ACL inbound on the interface that faces the internal LAN:

   R1(config)#interface GigabitEthernet0/0
   R1(config-if)#ip access-group 101 in
   

3. Validate the rule:

   • From PC‑A, attempt to browse to a web server on PC‑B (or use telnet 192.168.2.x 80). The connection should be refused.
   • Ping and SSH (port 22) should still succeed, proving that only HTTP is blocked.

4. Document the ACL in your lab notes, noting the ACL number, the exact statements, and the interface to which it is applied. This habit mirrors real‑world change‑control procedures It's one of those things that adds up..

Scaling Up: Adding a Third LAN Segment

To practice inter‑VLAN routing and more complex routing tables, extend the topology with a third LAN (192.Because of that, 3. So 168. 0/24) attached to R2.

1. Add a new switch (Switch‑C) and two PCs (PC‑C1, PC‑C2) Not complicated — just consistent..

2. Connect the switch to R2’s unused gigabit interface (e.g., Gig0/2).

3. Configure the new interface on R2:

   R2(config)#interface GigabitEthernet0/2
   R2(config-if)#ip address 192.Also, 168. Practically speaking, 3. 1 255.255.255.
   
   

4. Assign IP addresses to the new PCs:

   • PC‑C1: 192.168.3.10 /24, GW 192.168.3.1
   • PC‑C2: 192.168.3.20 /24, GW 192.168.3.1

5. Advertise the new network with RIP on R2:

   R2(config)#router rip
   R2(config-router)#network 192.168.3.0
   

6. Verify end‑to‑end connectivity:

   • Ping from PC‑A (192.168.1.x) to PC‑C1 (192.168.3.10).
   • Ping from PC‑C2 to PC‑B.

   All should succeed, confirming that RIP now carries three distinct networks across the WAN Took long enough..

Lab‑Report Template (Optional)

If you’re preparing a formal submission for an instructor or a certification practice log, use this concise template:

Conclusion

By walking through the steps above—starting with a single‑link, two‑router design, then layering redundancy, security, and a third LAN—you’ve built a miniature yet fully functional WAN that mirrors many real‑world deployments. Each command you typed reinforced a core CCNA concept:

• IP addressing & subnetting gave each device a unique identity.
• Interface activation and verification ensured the physical layer was sound.
• RIP (or any dynamic routing protocol) demonstrated how routers exchange reachability information without manual routes.
• ACLs introduced the principle of “least privilege” at the router edge.
• Redundant links illustrated convergence and metric‑based path selection.

The most valuable takeaway is the habit of verify‑then‑document. After every configuration change, run a show command, test connectivity, and log the outcome. This disciplined approach not only prepares you for the CCNA exam’s lab‑simulation questions but also cultivates the troubleshooting mindset that network engineers rely on daily Not complicated — just consistent..

Now that you have a solid, extensible foundation, you can experiment further—swap RIP for OSPF, enable IPv6, add VLANs, or integrate a firewall appliance. Each addition will deepen your understanding and bring you one step closer to mastering the CCNA curriculum. Happy packet‑crafting, and may your routes always converge quickly!

Advanced Tweaks You Can Try Next

Once the base lab is stable, push the environment a little further. The following optional exercises let you explore features that frequently appear on the CCNA exam and in real‑world networks.

Tip: When you add a new feature, always revert to the baseline verification steps (ping, show ip route, show ip protocols). If anything looks off, the debug commands (used sparingly) will quickly point you to the culprit But it adds up..

Troubleshooting Checklist – A Quick Reference

Having this sheet at hand during lab sessions saves valuable minutes and reinforces the systematic approach expected on the exam.

Wrapping Up the Lab Experience

You have now:

1. Built a functional dual‑router WAN with a third LAN.
2. Implemented RIP, verified route propagation, and confirmed that each router holds three distinct networks in its routing table.
3. Added redundancy, basic security, and a simple management plane (SSH).
4. Documented every step using the Lab‑Report Template, ensuring reproducibility and clear communication—skills that are just as important as the technical ones.

The CCNA exam tests not only your ability to type commands but also your capacity to plan, validate, and troubleshoot a network end‑to‑end. By completing this lab and the optional extensions, you have exercised all three pillars:

• Knowledge – understanding of protocols, addressing, and security.
• Skill – hands‑on configuration and verification.
• Attitude – disciplined documentation and methodical problem solving.

Take a moment to review the lab report you generated. If you can explain each command and the reason behind every verification output, you’re ready to tackle the simulation questions that will appear on the real CCNA test Nothing fancy..

Final Thoughts

Networking is a discipline of layers—physical, data‑link, network, and beyond. Because of that, the lab you just completed stitches those layers together, showing how a single mis‑configured interface can break an entire WAN, while a well‑placed ACL can protect it without sacrificing connectivity. Keep experimenting, keep documenting, and, most importantly, keep thinking like a network engineer: anticipate failure, design for resilience, and secure the path for every packet Simple, but easy to overlook. Took long enough..

Good luck on your CCNA journey, and may every route you configure converge on success!

Extending the Lab – Optional Challenges

While the core lab covers the essentials, you can stretch your skills by adding a few more layers of complexity. These extensions are optional but highly recommended if you want to mimic a production‑grade environment.

Tip: Keep your lab router’s uptime high and your CLI history clean. A well‑maintained environment reduces the risk of stale configurations interfering with new experiments.

Troubleshooting Checklist – Quick Refresher

Keep this table handy during the exam; a few keystrokes can save you minutes of frustration.

Final Thoughts

You’ve walked through the entire lifecycle of a small WAN: from design, to implementation, to verification, and finally to documentation. By practicing the steps outlined above, you’ve not only memorized a handful of commands but also internalized a systematic approach that Cisco values in the CCNA exam:

1. Plan – Understand the topology and the requirements before typing a single command.
2. Execute – Apply the configuration consistently across all devices.
3. Validate – Use the appropriate show commands to confirm the network behaves as intended.
4. Document – Record every change in a clear, reproducible format.

When you sit for the CCNA exam, the test will present you with scenarios that require rapid reasoning and precise configuration. The knowledge you’ve gained here—how to slice a network into subnets, how to let RIP do its job, how to protect with ACLs, and how to document everything—will be the foundation of your success The details matter here..

Take a final look at your lab report. If you can explain why you chose each command and what you expect to see in the output, you’re not just ready for the exam—you’re ready for the field.

Good luck, and may every packet you route find its destination with speed and security!

Going Beyond – Optional Enhancements

While the core lab covers all the mandatory CCNA material, a few extra features can give you a competitive edge and deepen your understanding of modern routing stacks.

1. OSPF Area Border Router (ABR) Basics

If you extend the lab to a second core router, you’ll see how OSPF can be segmented into multiple areas Easy to understand, harder to ignore..

• Configure an ABR

  interface Gig0/1
   ip address 10.10.10.1 255.255.255.0
   ip ospf 1 area 0
  interface Gig0/2
   ip address 10.20.20.1 255.255.255.0
   ip ospf 1 area 1
  

• Summarize routes

  router ospf 1
   area 0 range 10.0.0.0 255.255.0.0
  

Summarization reduces routing table size and limits OSPF convergence time And that's really what it comes down to..

2. EIGRP for IPv6

If you want to keep your lab modern, enable EIGRP for IPv6 on a single router.

interface Gig0/0
   ipv6 address 2001:db8:1::1/64
   ipv6 enable
router eigrp 1
   no auto-summary
   eigrp router-id 1.1.1.1
   network 2001:db8:1:: 0x0

Validate with show ipv6 eigrp neighbors Surprisingly effective..

3. NTP Synchronization

All routers should agree on time for accurate logs and SNMP timestamps.

ntp server 192.168.100.10

Verify with show ntp associations.

4. Dynamic ARP (Proxy ARP) for Transparent Bridging

If you need to forward traffic between non‑co‑located subnets without a router, enable Proxy ARP on the router interface.

interface Gig0/1
   ip proxy-arp

Test by pinging a host on the other subnet; the router will reply on behalf of the remote host.

Documentation – The Final Piece of the Puzzle

A lab report is more than a list of commands; it’s a narrative that explains why each step was taken. A well‑crafted report should include:

Not obvious, but once you see it — you'll see it everywhere.

Use Markdown or a PDF format for consistency. When you present this to a supervisor or study group, the clarity of your documentation will often be as impressive as the technical accuracy.

Putting It All Together – A Quick Recap

1. Design – Map out the WAN, decide on routing protocols, and plan IP schemes.
2. Configure – Apply interfaces, routing, ACLs, and SNMP, one device at a time.
3. Validate – Use show commands to confirm connectivity, routing tables, and security policies.
4. Document – Record every step, with reasoning and verification evidence.
5. Review – Spot-check for typos, missing ACL entries, or inconsistent subnetting.

This workflow mirrors the CCNA exam’s “scenario‑based” questions. When the exam asks you to “add a new site” or “block a rogue host,” you’ll be ready to translate the requirement into a concise, error‑free configuration.

Final Words

You’ve now traversed the full spectrum of a WAN laboratory: from the initial design to the final line‑by‑line verification, and from basic RIP to optional OSPF and EIGRP enhancements. Each command you typed is a building block; each verification step is proof that the block fits correctly.

Most guides skip this. Don't Worth keeping that in mind..

When the CCNA exam arrives, remember that the exam is not just a test of memorization—it’s a test of process. Apply the four‑step cycle, keep your documentation tight, and trust that the configurations you practiced today will translate into real‑world deployments Easy to understand, harder to ignore..

Good luck on the exam—and on every network you’ll design in the future. Your packets will travel faster, your systems will stay secure, and your career will keep moving forward Simple, but easy to overlook..