Packet Path/

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.

Labs · Beginner · 15 min · September 30, 2026

Isometric illustration of a compact home network lab with a rack, switch, and desk
In plain EnglishA home lab is a flight simulator for network engineers: a small, safe setup where you can configure real routers and switches, break things on purpose, and learn how packets actually move — without risking anyone's production network. You need about three small boxes on a desk (a router, a managed switch, a Raspberry Pi) plus free software for the rest. This guide shows you exactly what to buy, how to wire it, and which five projects turn it into interview answers.

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:

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.

HOME LAB — BLUEPRINT v1 · 192.168.0.0/16 private space ISP internet MikroTik hEX 192.168.10.1 router · OSPF/BGP/NAT WAN · DHCP TL-SG108E 192.168.10.3 managed switch trunk · VLANs 10,20,30,40 Raspberry Pi 5 192.168.10.2 DNS · DHCP · syslog VLAN 10 Laptop 192.168.20.100 VLAN 20 · users VLAN 20 GNS3 VM 192.168.30.x VLAN 30 · lab chaos VLAN 30 IoT / guest 192.168.40.x VLAN 40 · internet-only VLAN 40 USB console cable 10 · mgmt 20 · users 30 · lab 40 · iot/guest Dashed box = virtual. Dots = live traffic: mgmt (teal), user (green), lab chaos (amber).
The recommended lab, wired. The hEX routes between VLANs, the switch carries them all on one trunk, and the Pi is the network's brain.

The hardware core

Three physical pieces and one cable. Everything else, virtualize.

RolePickWhy
RouterMikroTik hEX (RB750Gr3)Runs RouterOS: real OSPF, BGP, NAT, firewall. Quiet, cheap to run, and the whole protocol stack is unlocked.
Managed switchTP-Link TL-SG108E or Ubiquiti Switch Flex MiniVLANs, trunks, port mirroring — the entire switching fundamentals set. Go Cisco CBS350 if your career is Cisco-shaped.
ServerRaspberry Pi 5Silent, sips power, and runs Pi-hole DNS, a DHCP server, syslog, and Docker containers for weeks without complaint.
CableUSB-to-serial console cableThe 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:

PACKET TRACE — laptop → internet via WireGuard Laptop .20.100 VLAN 20 Switch adds 802.1Q tag trunk → router hEX router strips tag · NAT routes to WAN VPS WireGuard encrypted tunnel ① Laptop sends a frame — access port, untagged, VLAN 20 ② Switch stamps the 802.1Q tag (red badge) and forwards up the trunk ③ Router strips the tag, NATs the source IP, routes toward the WAN ④ WireGuard encrypts it — the tunnel to your VPS carries it home-encrypted One packet, four jobs: switch (Layer 2) → router (Layer 3) → NAT → crypto. Say this out loud in the interview. Nail the filter syntax for watching it live with the Wireshark filter builder — link below.
The packet's journey, staged. The green dot is your packet; the red badge is the 802.1Q tag the switch adds and the router strips.

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

What not to buySkip vintage rack gear — old Catalyst 3750s and datacenter switches are loud, draw hundreds of watts, and do not teach you anything a modern small managed switch doesn't. Your electricity meter is not a curriculum.

Five projects that end up on resumes

  1. 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.
  2. 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.
  3. A WireGuard tunnel to a cheap VPS. Site-to-site crypto, policy routing, NAT exemption — production skills in an evening.
  4. Monitoring that pages you. Uptime checks from the Pi against your lab devices; SNMP walk practice; syslog from the switch and router.
  5. 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

VLANNameSubnetNotes
10mgmt192.168.10.0/24Switch, router, Pi management only
20users192.168.20.0/24Your real devices
30lab192.168.30.0/24Where the chaos lives
40iot/guest192.168.40.0/24Tight firewall rules; internet-only
Safety firstNever expose lab management interfaces to the internet, and never open your resolver (port 53) to the world — open DNS becomes a DDoS amplifier. VPN back home instead.
Try it yourselfPlan the lab before you buy: the subnet calculator sizes each VLAN's subnet, the config verifier sanity-checks your switch and router configs, and the Wireshark filter builder writes the capture filters for watching your packet journeys live.
Key takeaways

Keep reading