Homelab Network Setup
FreeDesign scalable home or small-lab networks efficiently.
Free · Opens the source repo
What Homelab Network Setup does
The Homelab Network Setup skill provides a comprehensive guide for designing and configuring a home or small-lab network that can grow over time without requiring a complete overhaul. This skill is particularly useful for individuals looking to establish a robust network infrastructure that supports various devices and services while maintaining flexibility for future expansions. By following the structured approach outlined in this skill, users can effectively plan their network layout, device roles, and IP addressing schemes.
The skill begins with the foundational aspect of network design, emphasizing the importance of separating device roles such as gateways, switches, and access points. Users are guided through the selection of appropriate devices based on their specific needs and technical expertise. For instance, it outlines the differences between using a basic ISP router versus more advanced options like OPNsense or pfSense, which offer greater control over network management features such as VLANs and firewall settings. This tailored approach ensures that users can choose the right equipment that aligns with their operational requirements.
Additionally, the skill provides detailed recommendations for IP planning, DHCP configurations, and DNS management. Users are encouraged to avoid common pitfalls, such as using the default 192.168.1.0/24 subnet, which can lead to conflicts with other networks. Instead, it suggests a structured IP range allocation that supports future scalability and segmentation. This foresight is crucial for users who may want to implement advanced features like VLANs or VPNs later on.
Finally, the skill addresses practical considerations for cabling and Wi-Fi setup, advocating for wired connections where feasible and offering tips for organizing and labeling network infrastructure. With this skill, users can troubleshoot common network issues and prepare their setups for future enhancements, making it an essential resource for anyone looking to build a reliable home or small-lab network.
When to use it
Use this skill when planning a new home network or redesigning an existing setup to ensure future growth and stability.
When not to use it
This skill may not be suitable for users seeking a quick, one-size-fits-all solution without the need for customization or planning.
What you can build with it
Beginner Upgrade
Stabilize a small lab by setting DHCP reservations for key devices and moving local names to a reserved domain.
VLAN-Ready Plan
Prepare for future segmentation by choosing non-overlapping IP ranges and documenting future SSIDs and switch ports.
Troubleshooting Network Issues
Use the skill to identify and resolve common networking problems such as double NAT and unstable connections.
How to install Homelab Network Setup
View source1. Install with the skills CLI
npx skills add affaan-m/ecc/homelab-network-setup --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by affaan-mHomelab 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
Frequently asked questions about Homelab Network Setup
Similar skills
Audio Editor
Automate your audio cleaning and editing process.
Watchers
Monitor feeds and APIs for new updates efficiently.
Moderator Actions
A comprehensive toolkit for moderating Civitai content.
Fleet Maintenance
Manage and audit Mac fleets efficiently.
AdGuard Home CLI
Manage AdGuard Home from the command line.
DoorDash Order Playbooks
Manage and automate your DoorDash orders with ease.