homelab-network-setup
- Use it when:
- You're planning a home or lab network, outgrowing the ISP router, or fighting double NAT, flaky Wi-Fi or servers that change address.
- It does:
- Separates gateway, switch and access point roles, compares gateway options and lays out an IP plan that's ready for VLANs later.
- You get:
- A subnet per device group, DHCP reservation and local DNS conventions, and a list of mistakes to avoid.
- Keep in mind:
- It advises and gives example plans; it doesn't configure any device.
TL;DR
A planning guide for home and small-lab networks that should grow without a rebuild. It starts by separating roles: the modem, a gateway that handles NAT, firewall, DHCP and DNS, a managed switch, access points for Wi-Fi only, then servers and clients. A table weighs gateway options, from the ISP router through UniFi, OPNsense or pfSense and MikroTik to a Linux router. The IP plan avoids 192.168.1.0/24, which clashes with hotels, offices and ISP routers once you use a VPN, and gives each group its own range (trusted clients, IoT, servers, guest, management) with the gateway on .1, infrastructure on .2 to .49 and the DHCP pool from .50. Local names go under home.arpa, the name reserved for home networks. Anything you SSH into, bookmark or monitor gets a DHCP reservation, and a Pi-hole gets its address before DHCP points clients at it. It favours wired access point backhaul, PoE switches, labelled cables and UPS power, and walks through a beginner upgrade and a VLAN-ready plan.
Summarizes the skill at d2ef268.
npx skills add https://github.com/affaan-m/ecc --skill homelab-network-setup More weekly downloads than 60% of skills
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 268 |
| Sep 28 | 161 |
| Oct 5 | 150 |
| Oct 12 | 231 |
| Oct 19 | 411 |
| Oct 26 | 411 |
| Nov 2 | 482 |
| Nov 9 | 449 |
Fewer downloads than 87% of skills
More stars than 97% of repos
Newer than 66% of skills
| Category |
Computer networks: home labs, VLANs, VPNs, DNS, routing and network diagnostics. |
|---|---|
| Type |
Knowledge and rules the agent applies while it works: best practices, design principles, API references. |
| Effect |
Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code. |
| Needs |
Instructions only. Works in any agent that supports skills. |
| Publisher |
Everyone else. Unverified vendor claims default to community. |
| Topics |
SKILL.md
From affaan-m/ecc at d2ef268. Checked daily, last changed Nov 6, 2026.
Frontmatter
name: homelab-network-setup
description: Practical home and homelab network planning for gateways, switches, access points, IP ranges, DHCP reservations, DNS, cabling, and common beginner mistakes. Use when planning or fixing a home or homelab network — gateway, switch, AP, IP ranges, DHCP, DNS, or cabling.
metadata:
origin: communityHomelab 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/24when 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