Skip to main content
Agent skill

Homelab Network Setup

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.

Get started

Get the complete skill folder, including its scripts and reference files.

·

When to use this skill

Use Homelab Network Setup when an AI agent needs a reusable SKILL.md workflow for this job: 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.

When not to use it

Skip Homelab Network Setup when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/homelab-network-setup
# Save SKILL.md to ~/.claude/skills/homelab-network-setup/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/homelab-network-setup/SKILL.md. For a shared project, commit the folder at .claude/skills/homelab-network-setup/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Homelab Network Setup skill for this task: Planning a new home network or redesigning an ISP-router-only setup. Confirm any required inputs or files before making changes.

What supports this recommendation?

83/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
92/100
Practical detail
92/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# 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:

```text 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.

```text 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`.

```text 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.

1. Set DHCP reservations for NAS, Pi, and any SSH hosts. 2. Move local names to `home.arpa`. 3. Disable duplicate DHCP servers on secondary routers or APs. 4. Wire the main AP instead of relying on wireless backhaul.

### VLAN-Ready Plan

Goal: Prepare for future segmentation without enabling it immediately.

1. Choose non-overlapping /24 ranges for trusted, IoT, servers, guest, and management. 2. Reserve .1 for the gateway and .2-.49 for infrastructure on every subnet. 3. Buy a gateway and switch that support VLANs and inter-VLAN firewall rules. 4. 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`

Intended uses

  • 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

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.