← Back to Projects

Homelab Network Architecture

VLAN-segmented flat network with pfSense as the edge router/firewall, managed switch for trunking, and full DNS + DHCP control.

pfSense VLANs Networking Firewall DNS
15 October 2024

What

The physical and logical design of my homelab network. Everything sits behind a pfSense VM acting as the default gateway and firewall. A managed HP ProCurve switch handles 802.1Q trunking down to Proxmox Linux bridges.

VLANs in use:

VLANNamePurpose
1NativeUntagged physical ports
10LANTrusted home devices
20LabVMs and containers
30IoTSmart home devices (isolated)
99MgmtProxmox, switch, AP management

Why

A flat network means a compromised IoT device can reach every other device. Segmenting with VLANs limits blast radius and mirrors real ISP/enterprise design. It also means I practice the same troubleshooting workflow (trace the VLAN, check the trunk, check the firewall rule) that I use every day at work.

How

pfSense Setup

  1. Installed pfSense CE 2.7 as a Proxmox VM with two virtual NICs:
    • vtnet0 → WAN (connected to home router via a /30)
    • vtnet1 → LAN trunk (carries all VLANs to Proxmox)
  2. Created VLAN interfaces (VLAN 10, 20, 30, 99) as children of vtnet1.
  3. Assigned IP gateways: 10.10.X.1/24 per VLAN.
  4. Configured DHCP server per VLAN with short leases for lab (10 min) and long for LAN (24 h).

Firewall Rules (simplified)

LAN → any: allow (trusted)
Lab → LAN: block
Lab → internet: allow
IoT → LAN: block
IoT → internet: allow (port 80/443 only)
Mgmt → any: allow from 10.10.99.0/24 only

Switch Trunking

Challenges

Tech Used