Homelab Network Setup
Use this skill to design a home or small-lab network that can grow without
needing a full rebuild.
When to Use
- Planning a new home network or redesigning an ISP-router-only setup.
- Choosing gateway, switch, and access point roles.
- Designing IP ranges, DHCP scopes, static reservations, and DNS.
- Preparing for future VLANs, Pi-hole, NAS, lab servers, or VPN access.
- Troubleshooting a new network that has double NAT, unstable Wi-Fi, or changing
server addresses.
How It Works
Start by separating device roles:
Internet
|
Modem or ONT
|
Gateway or router NAT, firewall, DHCP, DNS, inter-VLAN routing
|
Managed switch wired clients, AP uplinks, optional VLAN trunks
|
Access points Wi-Fi only; ideally wired backhaul
Servers and NAS stable addresses, DNS names, monitoring
Clients and IoT DHCP pools, isolated later if VLANs are available
Pick a gateway that matches the operator, not just the feature checklist:
| Option |
Best fit |
Notes |
| ISP router |
Basic internet only |
Limited control and often poor VLAN support |
| UniFi gateway |
Managed home network |
Good UI, ecosystem lock-in |
| OPNsense or pfSense |
Flexible homelab |
Strong VLAN, firewall, VPN, and DNS control |
| MikroTik |
Advanced network users |
Powerful, but easy to misconfigure |
| Linux router |
Tinkerers |
Document rollback before using as primary gateway |
IP Plan
Avoid the most common default, 192.168.1.0/24, when you expect to use VPNs.
It often conflicts with hotels, offices, and ISP routers.
Example small homelab plan:
192.168.10.0/24 trusted clients
192.168.20.0/24 IoT and media devices
192.168.30.0/24 servers and NAS
192.168.40.0/24 guest Wi-Fi
192.168.99.0/24 network management
Gateway convention: .1
Infrastructure reservations: .2 through .49
Dynamic DHCP pool: .50 through .240
Spare room: .241 through .254
Use home.arpa for local names. It is reserved for home networks and avoids the
leakage/conflict problems of ad hoc names like home.lan.
nas.home.arpa
pihole.home.arpa
gateway.home.arpa
switch-01.home.arpa
DHCP And DNS
- Use DHCP reservations for anything you SSH into, bookmark, monitor, or expose
as a service.
- Hand out the gateway as DNS until a local resolver is intentionally deployed.
- If using Pi-hole or another DNS filter, give it a reservation first, then point
DHCP DNS options at that address.
- Keep a small static/reserved range per subnet so replacements do not collide
with dynamic leases.
Cabling And Wi-Fi
- Prefer wired AP backhaul over mesh when you can run Ethernet.
- Use a PoE switch for APs and cameras if the budget allows it.
- Label both ends of each cable and keep a simple port map.
- Put the gateway, switch, DNS server, and NAS on UPS power if outages are common.
Examples
Beginner Upgrade
Goal: Keep the ISP router but stabilize a small lab.
- Set DHCP reservations for NAS, Pi, and any SSH hosts.
- Move local names to
home.arpa.
- Disable duplicate DHCP servers on secondary routers or APs.
- Wire the main AP instead of relying on wireless backhaul.
VLAN-Ready Plan
Goal: Prepare for future segmentation without enabling it immediately.
- Choose non-overlapping /24 ranges for trusted, IoT, servers, guest, and
management.
- Reserve .1 for the gateway and .2-.49 for infrastructure on every subnet.
- Buy a gateway and switch that support VLANs and inter-VLAN firewall rules.
- Document which SSIDs and switch ports will eventually map to each network.
Anti-Patterns
- Double NAT without a reason or documentation.
- Using
192.168.1.0/24 when VPN access is planned.
- Dynamic addresses for NAS, Pi-hole, Home Assistant, or other service hosts.
- Consumer routers repurposed as APs while their DHCP servers are still enabled.
- Flat networks with cameras, smart plugs, laptops, and servers all sharing the
same trust boundary.
See Also
- Skill:
network-interface-health
- Skill:
network-config-validation
1---
2name: homelab-network-setup
3description: 家庭与实验室网络规划实战——网关、交换机、AP、IP 范围、DHCP 预留及 Wi-Fi 信道规划
4origin: community
5metadata:
6 source: https://skillmd.com/skills/azusagasaku/homelab-network-setup
7---
8
9# Homelab Network Setup
10
11Use this skill to design a home or small-lab network that can grow without
12needing a full rebuild.
13
14## When to Use
15
16- Planning a new home network or redesigning an ISP-router-only setup.
17- Choosing gateway, switch, and access point roles.
18- Designing IP ranges, DHCP scopes, static reservations, and DNS.
19- Preparing for future VLANs, Pi-hole, NAS, lab servers, or VPN access.
20- Troubleshooting a new network that has double NAT, unstable Wi-Fi, or changing
21 server addresses.
22
23## How It Works
24
25Start by separating device roles:
26
27```text
28Internet
29 |
30Modem or ONT
31 |
32Gateway or router NAT, firewall, DHCP, DNS, inter-VLAN routing
33 |
34Managed switch wired clients, AP uplinks, optional VLAN trunks
35 |
36Access points Wi-Fi only; ideally wired backhaul
37Servers and NAS stable addresses, DNS names, monitoring
38Clients and IoT DHCP pools, isolated later if VLANs are available
39```
40
41Pick a gateway that matches the operator, not just the feature checklist:
42
43| Option | Best fit | Notes |
44| --- | --- | --- |
45| ISP router | Basic internet only | Limited control and often poor VLAN support |
46| UniFi gateway | Managed home network | Good UI, ecosystem lock-in |
47| OPNsense or pfSense | Flexible homelab | Strong VLAN, firewall, VPN, and DNS control |
48| MikroTik | Advanced network users | Powerful, but easy to misconfigure |
49| Linux router | Tinkerers | Document rollback before using as primary gateway |
50
51## IP Plan
52
53Avoid the most common default, `192.168.1.0/24`, when you expect to use VPNs.
54It often conflicts with hotels, offices, and ISP routers.
55
56```text
57Example small homelab plan:
58
59192.168.10.0/24 trusted clients
60192.168.20.0/24 IoT and media devices
61192.168.30.0/24 servers and NAS
62192.168.40.0/24 guest Wi-Fi
63192.168.99.0/24 network management
64
65Gateway convention: .1
66Infrastructure reservations: .2 through .49
67Dynamic DHCP pool: .50 through .240
68Spare room: .241 through .254
69```
70
71Use `home.arpa` for local names. It is reserved for home networks and avoids the
72leakage/conflict problems of ad hoc names like `home.lan`.
73
74```text
75nas.home.arpa
76pihole.home.arpa
77gateway.home.arpa
78switch-01.home.arpa
79```
80
81## DHCP And DNS
82
83- Use DHCP reservations for anything you SSH into, bookmark, monitor, or expose
84 as a service.
85- Hand out the gateway as DNS until a local resolver is intentionally deployed.
86- If using Pi-hole or another DNS filter, give it a reservation first, then point
87 DHCP DNS options at that address.
88- Keep a small static/reserved range per subnet so replacements do not collide
89 with dynamic leases.
90
91## Cabling And Wi-Fi
92
93- Prefer wired AP backhaul over mesh when you can run Ethernet.
94- Use a PoE switch for APs and cameras if the budget allows it.
95- Label both ends of each cable and keep a simple port map.
96- Put the gateway, switch, DNS server, and NAS on UPS power if outages are common.
97
98## Examples
99
100### Beginner Upgrade
101
102Goal: Keep the ISP router but stabilize a small lab.
103
1041. Set DHCP reservations for NAS, Pi, and any SSH hosts.
1052. Move local names to `home.arpa`.
1063. Disable duplicate DHCP servers on secondary routers or APs.
1074. Wire the main AP instead of relying on wireless backhaul.
108
109### VLAN-Ready Plan
110
111Goal: Prepare for future segmentation without enabling it immediately.
112
1131. Choose non-overlapping /24 ranges for trusted, IoT, servers, guest, and
114 management.
1152. Reserve .1 for the gateway and .2-.49 for infrastructure on every subnet.
1163. Buy a gateway and switch that support VLANs and inter-VLAN firewall rules.
1174. Document which SSIDs and switch ports will eventually map to each network.
118
119## Anti-Patterns
120
121- Double NAT without a reason or documentation.
122- Using `192.168.1.0/24` when VPN access is planned.
123- Dynamic addresses for NAS, Pi-hole, Home Assistant, or other service hosts.
124- Consumer routers repurposed as APs while their DHCP servers are still enabled.
125- Flat networks with cameras, smart plugs, laptops, and servers all sharing the
126 same trust boundary.
127
128## See Also
129
130- Skill: `network-interface-health`
131- Skill: `network-config-validation`