Home Lab Networking Setup: How I Built Mine (VLANs, Firewall & DNS)

By /

Last updated on April 22nd, 2026 at 12:25 pm

Building a home lab isn’t just about spinning up VMs — I learned that the hard way.

Early on, I had everything sitting on one flat network. It worked, sort of. But the moment I started adding Active Directory, SCCM, and Intune into the mix, things got messy fast. Traffic was bleeding everywhere, DNS was a nightmare, and I had no real control over what was talking to what.

That’s when I sat down and properly built out my network — VLANs, a proper firewall, internal DNS, the lot.

This guide covers exactly how I set it up, what gear and software I use, and the mistakes I’d tell past-me to avoid.

🌐 Why Networking Matters in a Home Lab

Most home lab guides skip past networking like it’s an afterthought. It’s not — it’s the foundation everything else runs on.

Once I got my network properly segmented, my whole lab started to feel like a real enterprise environment. I could isolate test machines, simulate client/server relationships, and actually break things without taking down my home internet in the process.

Good networking lets you:

  • Isolate lab environments safely
  • Simulate real-world enterprise setups
  • Control traffic between services
  • Keep your lab completely separate from your home network

Core Networking Concepts (Simplified)

Before diving into configs, here are the essentials:

IP Addressing

Every device in your lab needs an IP address to communicate.

  • Example: 192.168.10.5
  • Usually assigned via DHCP or set statically for servers

Subnets

Subnets divide your network into smaller segments.

  • Example:
    • 192.168.10.0/24 → Servers
    • 192.168.20.0/24 → Clients

This is key for lab organisation and security.

VLANs (Virtual LANs)

VLANs let you separate networks without extra hardware.

Typical setup:

  • VLAN 10 → Management (Proxmox, switches)
  • VLAN 20 → Servers
  • VLAN 30 → Clients
  • VLAN 40 → Testing / isolated

If you’re running Proxmox VE, VLANs are incredibly useful for separating VM traffic.

DNS

Internal DNS makes your lab usable.

Instead of:

  • 192.168.10.10

You get:

  • dc01.lab.local

This becomes essential when working with Microsoft Configuration Manager or domain services.

My Home Lab Network Setup

Here’s the actual layout I’m running on my Dell R730:

  • Firewall/Router — handles internet access and VLAN routing
  • Managed Switch — TP-Link Omada, supports full VLAN tagging
  • Proxmox Host — all VMs sit here, each on their own VLAN
  • Windows Server VM — handles AD, DNS, and DHCP for the lab

Traffic flow: Internet → Firewall → VLANs → Proxmox → VMs

The key thing that made this click for me was realising the firewall is the brain — everything else just follows the rules you set there. Once I understood that, VLAN configs stopped feeling like voodoo magic.

Firewall & Routing Basics

This is where I spent the most time experimenting — and honestly, it’s been one of the best learning experiences of the whole lab build.

I’ve run both pfSense and OPNsense at different points. Both are excellent. I eventually landed on OPNsense for my main setup, but pfSense is equally capable — it really comes down to personal preference.

For hardware, I’ve used and can genuinely recommend:

  • TP-Link Omada – great value, solid VLAN support, easy to manage
  • Unify – more polished UI, slightly steeper cost

With a proper firewall in place, you can build rules like:

  • Clients → Internet ✅
  • Clients → Servers ❌ (unless explicitly needed)
  • IoT devices → blocked from everything ✅

Common Mistakes to Avoid

  • I made most of these myself, so learn from my pain:

    • Flat networking — everything on one subnet feels fine until it really isn’t
    • Not documenting IP ranges — you will forget. Write it down. I use a simple spreadsheet
    • Skipping DNS — this single-handedly broke my SCCM setup twice
    • Overcomplicating too early — I went deep on VLANs before I understood basic routing. Start simple, layer complexity in gradually

Final Thoughts

Networking used to be the part of IT I avoided — too abstract, too much acronym soup.

Building it out in my home lab changed that completely. Once you’ve actually configured VLANs, set firewall rules, and watched DNS either save or destroy your day — it stops being theory and becomes instinct.

If you’re just starting out, don’t overthink it. Get a managed switch, pick a firewall (pfSense or OPNsense), and start with two VLANs. You’ll expand from there naturally.

Got questions about my specific setup? Drop a comment below — happy to share configs.

Scroll to Top