Home lab network diagram template
A home network split into three VLANs: one for the household, one for the lab (a Proxmox hypervisor, a TrueNAS NAS and Pi-hole for DNS) and one for IoT devices such as cameras and smart TVs, kept apart from everything else.
It's a quick way to write down how your own setup is wired: which VLAN each device is on, its address, and what talks to what.
How it's laid out
- The router and managed switch sit in front of all three segments. Each link from the switch is labelled with the VLAN it carries.
- The IoT segment (VLAN 40) is noted as having no access to Home or Lab.
- It includes the documentation rule pack, which points out devices that are missing an address or other details.
Networks and segments
| Name | Kind | Subnet | VLAN | Notes |
|---|---|---|---|---|
| Home | Segment | 192.168.0.0/24 | 1 | - |
| Lab | Segment | 192.168.30.0/24 | 30 | - |
| IoT | Segment | 192.168.40.0/24 | 40 | No access to Home or Lab |
Device inventory
In Schema this table isn't a separate document. It's generated from the diagram, can be edited in place, and exports as CSV.
| Device | Type | Hostname | IP address | Role | Owner | Segment |
|---|---|---|---|---|---|---|
| Internet | Internet | - | - | - | - | - |
| Router | Router | - | 192.168.0.1 | Gateway | - | - |
| Managed switch | Switch | - | 192.168.0.2 | - | - | - |
| Wi-Fi AP | Access Point | - | 192.168.0.5 | - | - | Home |
| Family devices | Laptop | - | - | - | - | Home |
| Proxmox | Hypervisor | pve-01 | 192.168.30.10 | Hypervisor | - | Lab |
| NAS | NAS / SAN | nas-01 | 192.168.30.20 | - | - | Lab |
| Pi-hole | DNS | pihole | 192.168.30.53 | DNS | - | Lab |
| Cameras | CCTV | - | - | - | - | IoT |
| Smart TV | Display | - | - | - | - | IoT |
Rules it checks
The template comes with these rule packs switched on. Schema checks them as you edit and marks anything that breaks a rule on the canvas. Every rule can be edited, turned off or deleted.
Documentation completeness
Every server, database and network device has the fields someone on call at 3am will need: an address, an owner, a role.
- Servers must have an IP address
- Servers must have an owner
- Servers must have a role
- Servers must record their OS
- Databases must have an IP address
- Databases must have an owner
- Firewalls must have an IP address
- Routers must have an IP address
Start from this template
Open it in Schema, replace the example addresses with yours, and you have a diagram, an inventory and a written report of your network. Free during early access.
Use this template freeOther templates
- Small office networkFirewall, a staff LAN, a server VLAN and isolated guest Wi-Fi - the classic single-site SMB layout.
- Three-tier web applicationDMZ, web, app and data tiers with addressed hosts, labelled flows and two firewall boundaries.
- Hybrid cloudA head office joined to a cloud VPC by site-to-site VPN, with public and private subnets.
- Zero trust accessUsers reach private apps only through an identity-aware access proxy backed by SSO, device checks and a SIEM.