Back to the Lab
Lab — Reference design

REFERENCE HOME NETWORK

An example of a well-segmented home network. Every device class gets its own network, every network sits in a firewall zone, and traffic between zones only flows where a rule allows it. Addresses and names are illustrative.

ALL SYSTEMS OPERATIONAL8 networks online5 zones enforced0 alerts
WAN · 1 Gbps · no open ports↑ nightly sync from the PiEXTERNALuntrusted by defaultInternetISP uplink · fiber WAN● connectedOffsite Backupencrypted · versioned · 3-2-1● last sync OKEdge Firewall172.16.0.1 · router + zone-based firewalldefault deny · 42 policies active● enforcingCORE ZONE● 2/2 onlineInfrastructureVLAN 10 · 172.16.10.0/24Core switch (PoE)managed · .2Wi-Fi access pointsindoor + outdoor · .3–.4Raspberry Pi · .10home server · 10 services healthy● Technitium DNS · ad + malware filter● NTP time source● Uptime monitor · phone alerts● Metrics · CPU · disk · temps● Reverse proxy · TLS● Password vault● File shares● Backup jobs · nightly● NVR storage● Host firewall + ban listDNS + NTP authority for every networkAdminVLAN 15 · 172.16.15.0/24dedicated admin workstation→ manages firewall · switches · APs · serverprivileged access onlyTRUSTED ZONEPersonalVLAN 25172.16.25.0/24laptops · phones14 devices · UP→ Internet→ file shares→ password vault→ cast to TVsfiltered DNSadmin tools via AdminIOT ZONE● 2/2 onlineCamerasVLAN 40 · 172.16.40.0/246 cameras · recording 24/7→ local NVR · footage stays on-site→ live view through the VPNlocal-only by designmanaged from AdminSmart Home & TVVLAN 45 · 172.16.45.0/2418 devices · UPplugs · thermostat · streaming→ vendor cloud + updates (allowlist)← controlled from Personalcontained away from CoreGUEST ZONEVisitorsVLAN 80172.16.80.0/243 guests · UP→ Internet · rate limitedclient isolation onwalled off from homeREMOTE ZONEPersonal VPN172.16.100.0/24 · WireGuard→ same access as PersonalAdmin VPN172.16.110.0/24 · key + MFA→ same access as AdminForced DNS / NTPevery network → Technitium DNS on the Raspberry Pi (172.16.10.10), redirected at the firewall● 100% of clients covereddevices with hard-coded DNS are redirected to the filter · upstream lookups leave encryptedLEGENDCoreTrustedIoTGuestRemoteExternallive traffic through the firewallDNS / NTP to the Raspberry Pifirewall zoneonline→ allowed path · anything not shown is denied by default

Segmentation

8 Networks · 5 Zones

Network gear, admin, personal devices, cameras, smart home, visitors and two VPNs each get their own network.

Firewall posture

Default Deny

Every zone pair starts closed. Each allow is narrow and named, and no rule uses "any to any".

DNS control

1 Resolver

Technitium DNS on a Raspberry Pi answers for every network, so ad and malware blocking covers devices you can't install software on.

Illustrative reference design · private example address ranges · generic device names