Build a Home Lab That Actually Gets You Hired
A managed switch, a real router, a Raspberry Pi, and free virtualization software. Here's the lab that teaches real skills — without the loud, power-hungry mistakes everyone warns about.
The flight-simulator analogy
Pilots don't learn in a classroom and then fly a 747 full of people. They log hundreds of hours in a simulator: engines fail, weather turns, alarms scream — and nobody dies. A home lab is the same deal for networking:
- The simulator cockpit = your desk gear. Real devices, real command lines, real blinking lights.
- Engine failures = you unplugging cables, mismatching VLANs, and creating loops on purpose — then fixing them.
- The logbook = the five projects below. Each one is a story you tell in an interview: "here's what broke, here's the packet capture, here's how I fixed it."
Interviewers have a tell for candidates who only watched videos: they describe protocols but freeze on "walk me through a packet that leaves your VLAN and arrives somewhere else." A lab builds the muscle that answers that fluently.
Why a lab beats another course
Courses teach you what commands exist. A lab teaches you what happens when you type them — including the 9 PM version where nothing works and the console cable becomes your best friend. And you do not need a rack, a closet, or a second mortgage: a small desk's worth of gear plus free virtualization covers the entire CCNA and most of CCNP.
The blueprint: wire it like this
This is the whole lab on one blueprint. Three physical boxes, one trunk carrying four VLANs, and a dotted path where the chaos lives (the lab VLAN). IPs follow the plan in the table further down.
The hardware core
Three physical pieces and one cable. Everything else, virtualize.
| Role | Pick | Why |
|---|---|---|
| Router | MikroTik hEX (RB750Gr3) | Runs RouterOS: real OSPF, BGP, NAT, firewall. Quiet, cheap to run, and the whole protocol stack is unlocked. |
| Managed switch | TP-Link TL-SG108E or Ubiquiti Switch Flex Mini | VLANs, trunks, port mirroring — the entire switching fundamentals set. Go Cisco CBS350 if your career is Cisco-shaped. |
| Server | Raspberry Pi 5 | Silent, sips power, and runs Pi-hole DNS, a DHCP server, syslog, and Docker containers for weeks without complaint. |
| Cable | USB-to-serial console cable | The day anything stops pinging, the console port is how adults reach the CLI. |
Decoding that table: a managed switch is one you can actually configure (VLANs, trunks, port mirroring); RouterOS is the MikroTik operating system that speaks real OSPF, BGP, and NAT; Pi-hole is ad-blocking DNS software that doubles as your DNS learning lab.
Full details and links are on the gear page. Start with the switch and Pi if budget is tight; add the router when you reach real routing protocols.
Follow one packet through the lab
This is the interview question the lab answers: "Walk me through a packet that leaves your VLAN and arrives somewhere else." Watch a packet leave the laptop on VLAN 20, ride the trunk, get routed and NATed, and disappear into an encrypted tunnel:
The four jobs, in plain words: the switch works at Layer 2 — it stamps the 802.1Q tag (the VLAN label) and forwards up the trunk. The router works at Layer 3 — it strips the tag, rewrites the source address (NAT), and routes toward the internet. WireGuard (a modern, fast VPN protocol) encrypts it for the tunnel to your VPS. One packet, four jobs: switch → router → NAT → crypto. Say this out loud in the interview.
Want to watch this exact journey on the wire? Mirror the trunk port to your laptop and build the capture filter with the Wireshark filter builder.
Virtualize the rest — mostly free
- GNS3 — open source, runs real device images for Cisco, Juniper, MikroTik, and Linux. The standard choice for cert study.
- EVE-NG — excellent browser-based labbing, but note that v7 moved to a freemium model with a small free tier; the older Community Edition still runs without new updates.
- Cisco Packet Tracer — free with a Cisco Skills for All account. Simplified, but perfect for the first 90 days.
- Cisco Modeling Labs (CML) — paid but cheap and official, with every Cisco image you could want.
Five projects that end up on resumes
- VLAN segmentation that actually works. Management, wired, IoT, guests, lab — inter-VLAN routing on the hEX, DHCP per VLAN, firewall rules between them. Size each VLAN's subnet first with the subnet calculator, then sanity-check your switch config with the config verifier.
- Pi-hole DNS with DHCP failover. The Pi becomes your network's brain: DNS filtering, static DHCP leases for lab gear, and a dashboard you screenshot later.
- A WireGuard tunnel to a cheap VPS. Site-to-site crypto, policy routing, NAT exemption — production skills in an evening.
- Monitoring that pages you. Uptime checks from the Pi against your lab devices; SNMP walk practice; syslog from the switch and router.
- A troubleshooting portfolio. Break the lab on purpose — mismatched native VLANs, a switch loop without STP, DNS pointing nowhere — capture the Wireshark traces, write up the diagnosis. Three of these is an interview portfolio.
A sane VLAN plan to start from
| VLAN | Name | Subnet | Notes |
|---|---|---|---|
| 10 | mgmt | 192.168.10.0/24 | Switch, router, Pi management only |
| 20 | users | 192.168.20.0/24 | Your real devices |
| 30 | lab | 192.168.30.0/24 | Where the chaos lives |
| 40 | iot/guest | 192.168.40.0/24 | Tight firewall rules; internet-only |
- Start physical: managed switch + router + Raspberry Pi. Virtualize the rest for free.
- GNS3 is free and open; EVE-NG v7 moved to freemium — plan accordingly.
- Build projects with resume-ready outcomes, not random topologies.
- Avoid vintage rack gear: noise and power bills teach nothing.