Skip to content

Home network (LAN IP scheme)

Current network

LAN 10.0.0.0/24 (subnet mask 255.255.255.0)
Gateway / router 10.0.0.1 — CenturyLink C400XG

The layout is meant for readability, role-based grouping, and a clean path to VLANs / extra subnets later.

IP ranges

Range Purpose Examples / notes
10.0.0.1 Router / gateway CenturyLink C400XG
10.0.0.2 – 10.0.0.9 Networking infrastructure Managed switch (TL-SG105E), future APs, PoE injectors, etc.
10.0.0.10 – 10.0.0.19 Storage / NAS Leviathon (Synology) → 10.0.0.10
10.0.0.20 – 10.0.0.29 Application / service servers Seamoth → 10.0.0.20, Prawn → 10.0.0.21 (see projects/Homelab-Mac-Mini-Hosts)
10.0.0.30 – 10.0.0.39 Lab / experiments / VMs Test VMs, temporary containers, experimental hardware
10.0.0.40 – 10.0.0.99 IoT / smart home / peripherals Printers, cameras, hubs, etc. (assign as needed)
10.0.0.100 – 10.0.0.254 DHCP pool (clients) Phones, laptops, tablets, consoles, guests

Device assignments (current)

  • 10.0.0.1 — CenturyLink C400XG router
  • 10.0.0.2 — TL-SG105E managed switch
  • 10.0.0.10 — Leviathon (Synology NAS, primary storage)
  • 10.0.0.20 — Seamoth (Macmini6,1 — Jellyfin, Home Assistant, media stack, Technitium DNS primary (ports 53/1053), acme.sh wildcard cert (~/docker/acme), Cloudflare DDNS, Tailscale exit)
  • 10.0.0.21 — Prawn (Macmini5,1 — Minecraft, Technitium DNS secondary (port 53, mirrors Seamoth), Tailscale tag:gameserver). Back online 2026-10-22; 100% CPU was Minecraft memory pressure, fixed by lowering heaps

Off this LAN: Aurora (gaming/AI PC) sits on the campus dorm network, not 10.0.0.0/24. It reaches home 10.0.0.x only through Leviathon over Tailscale. projects/Aurora-Gaming-PC.

WAN / ISP

ISP CenturyLink (gigabit service)
Customer router CenturyLink-provided C400XG
DDNS (Synology) leviathon.synology.me → current home WAN (updated by Synology on Leviathon). Many proxied kiefermenard.com names chain to this hostname in Cloudflare — see projects/Self-Hosted-Services#dns-and-domains-cloudflare

The CenturyLink router’s firewall / port-forward UI is limited (for example no CIDR in the “source IP” field for forwards), so IP allowlisting for Minecraft happens on Prawn (UFW) after traffic is proxied — see projects/Game-Servers#tcpshield-ddos-protection-for-minecraft.

Router DNS: DNS1 = 10.0.0.20 (Technitium primary on Seamoth), DNS2 = 10.0.0.21 (Technitium secondary on Prawn).

Resolvers (2026-10-27): Technitium DNS (Docker) is serving homelab DNS (cutover done). Seamoth 10.0.0.20 is the primary (ports 53 and 1053); Prawn 10.0.0.21 is the secondary (port 53) and mirrors zones from Seamoth (10.0.0.20:1053). Pi-hole was removed from both hosts on 2026-10-23. Confirmed as DNS for Snowfox, which reaches it over the tailnet via Tailscale’s DNS setting. The API/web UI is reachable only on the LAN IPs (port 5380), not localhost. Local names: seamoth.home, prawn.home, leviathon.home.

Split horizon (2026-10-27): 21 kiefermenard.com zones (LAN shortcuts that send service subdomains straight to Leviathon) were re-enabled once Leviathon stopped serving its default leviathon.synology.me certificate on local connections (that mismatch hit Uptime Kuma and browsers). The ab, abyssal, mc, and rlcraft zones remain disabled. acme.sh in Docker on Seamoth (~/docker/acme) now issues a Let’s Encrypt wildcard for kiefermenard.com, assigns it to Leviathon’s DSM reverse-proxy entries, and auto-renews and redeploys it to DSM with a dedicated DSM user. Cloudflare SSL mode for kiefermenard.com is Full (strict); the homelab service subdomains work with it. Open: kiefermenard.com / www on Leviathon was still serving a self-signed certificate and was being investigated. Detail: projects/Self-Hosted-Services#technitium-dns-2026-10-22, projects/Self-Hosted-Services#wildcard-certificate-2026-10-27.

Router port forwards (WAN → LAN)

Only the forwards actively in use need to be enabled.

WAN port LAN destination Purpose
80 10.0.0.10:80 Synology reverse proxy (HTTP)
443 10.0.0.10:443 Synology reverse proxy (HTTPS)
25565 10.0.0.21:25565 Minecraft (mc-router on Prawn)

DSM: ports 5000 / 5001 (direct DSM) are intentionally not forwarded. DSM is reached only via diskstation.kiefermenard.com through the reverse proxy.

Synology firewall (Leviathon)

Control Panel → Security → Firewall — rules are evaluated top to bottom; order matters.

Priority Source Action Purpose
1 172.17.0.0/255.255.0.0 Allow Docker bridge (inter-container traffic, e.g. iGotify Assistant → Gotify)
2 10.0.0.0/255.255.255.0 Allow LAN (ABB, NFS from Seamoth, NUT/SSH/rsync from Mac minis, etc.)
3 Canada, United States Allow Geo-allow
5 All Deny Default deny

Without the 172.17.0.0/16 Docker rule, containers on the default bridge cannot reach each other even on the same network. Without the LAN rule, NAS services used from Seamoth (NFS, ABB) break once geo rules are in place.

Migration notes (from 192.168.0.0/24)

Rough order of operations:

  1. Change router LAN settings first.
  2. Update static IPs on NAS and Mac Mini (and any other fixed hosts).
  3. Update Tailscale advertised subnet on Leviathon to 10.0.0.0/24 and the matching ACL grant (see projects/Game-Servers#tailscale-acl-grants-config) — done (tailnet policy now uses 10.0.0.0/24 instead of 192.168.0.0/24).
  4. Update port forwards, NFS mounts, Docker / compose references, internal bookmarks, and any DDNS-related origin configs.

Service-level checklists live with each stack: projects/Self-Hosted-Services, projects/Game-Servers, projects/Home-Assistant-menu-json-deploy.

Future expansion (planned)

When moving to owned space and stronger routing gear, extend into multiple VLANs / subnets along the same numbering idea:

Planned subnet Role
10.0.0.0/24 Management / trusted core
10.0.10.0/24 Servers
10.0.20.0/24 Storage
10.0.30.0/24 Lab
10.0.40.0/24 IoT / smart home
10.0.99.0/24 Guest / untrusted

Why this scheme

  • Easy to remember and type
  • Clear separation by device role
  • Room for a large DHCP pool (~150 addresses)
  • Foundation for later VLAN segmentation
  • Avoids common consumer defaults (192.168.x.x)