ecc-homelab-network-setup

Plan home and homelab networks covering gateways, switches, IP ranges, DHCP, DNS, and cabling.

Updated Apr 18, 2025
One-click install
npx skills add https://github.com/adriancodes/dotfiles --skill ecc-homelab-network-setup-adriancodes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ecc-homelab-network-setup
Source: https://github.com/adriancodes/dotfiles/tree/main/dot_agents/skills/ecc-homelab-network-setup
Command: npx skills add https://github.com/adriancodes/dotfiles --skill ecc-homelab-network-setup-adriancodes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing or fixing a home or homelab network often leads to double NAT, unstable Wi-Fi, conflicting IP ranges, and servers whose addresses keep changing. This Skill provides a structured reference for planning a network that can grow without a full rebuild. ## Core Features & Use Cases - Device Role Separation: Guides selection of gateway, managed switch, and access points, comparing options like ISP routers, UniFi, OPNsense/pfSense, MikroTik, and Linux routers. - IP, DHCP, and DNS Planning: Provides example subnet layouts, DHCP reservation conventions, and use of the reserved home.arpa domain for local names. - Cabling and Wi-Fi Guidance: Covers wired AP backhaul, PoE switches, cable labeling, and UPS placement for core infrastructure. - Use Case: When setting up a new homelab with a NAS and Pi-hole, use this Skill to design non-overlapping subnets, reserve static addresses for service hosts, and avoid VPN conflicts with the default 192.168.1.0/24 range. ## Quick Start Ask the assistant to design a homelab network plan with separate subnets for trusted clients, IoT devices, servers, and guests, including DHCP reservations and local DNS names.

Frequently Asked Questions about ecc-homelab-network-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan IP ranges for a homelab network?▼

Assign separate /24 subnets per device class, such as 192.168.10.0/24 for trusted clients and 192.168.30.0/24 for servers. Reserve .1 for the gateway, .2-.49 for infrastructure, and use .50-.240 as the dynamic DHCP pool.

What gateway should I use for a home network with VLANs?▼

OPNsense or pfSense offers strong VLAN, firewall, VPN, and DNS control for flexible homelabs. UniFi gateways suit managed home networks with a good UI, while MikroTik fits advanced users comfortable with complex configuration.

Why should I avoid 192.168.1.0/24 in my home network?▼

The 192.168.1.0/24 range is the most common default and often conflicts with hotel, office, and ISP router networks when you connect over VPN. Choosing a less common range like 192.168.10.0/24 avoids routing conflicts.

Should I use mesh Wi-Fi or wired access points in a homelab?▼

Wired AP backhaul is preferred over mesh whenever Ethernet can be run, since it provides more stable throughput. A PoE switch simplifies powering access points and cameras over the same cable.

What local domain name should I use for home network DNS?▼

Use home.arpa, which is reserved specifically for home networks and avoids the leakage and conflict problems of ad hoc names like home.lan. Examples include nas.home.arpa and pihole.home.arpa.

Why does my homelab have double NAT and how do I fix it?▼

Double NAT happens when a secondary router performs NAT behind the ISP router, breaking port forwarding and some VPNs. Fix it by bridging the ISP router or converting secondary routers to pure access points with DHCP disabled.