VLAN subnets and identity

Documentation Index

Fetch the complete documentation index at: https://docs.moodmnky.com/llms.txt

Use this file to discover all available pages before exploring further.

This page is the canonical reference for layer-3 segment identity: what each /24 is for, which Proxmox node anchors it, and how it relates to the edge (pfSense) and overlay (NetBird). For live VM/LXC inventory, use the Data Center Map. For operator secrets and env keys, use Datacenter Environment Inventory (never commit secrets to Mintlify).

​

How segments fit together

Site VLANs terminate at pfSense on MNKY-HQ. Remote peers reach them through NetBird to pfSense hub routing (not via competing subnet routers on hypervisors). See Edge network overview and NetBird for routes and groups.

​

Summary table

An additional routed internal segment 10.0.13.0/24 (DATA internal, vmbr1) appears in NetBird route inventory; treat it as infrastructure on the DATA side, not a separate MNKY brand plane. See NetBird.

​

Per-segment narrative

​

10.0.0.0/24 — DATA (site core)

DATA is the most stable anchor next to the WAN path: default-gateway adjacency, TrueNAS, self-hosted NetBird, Traefik, Coolify HQ, container registry, and typical monitoring targets. Home-adjacent clients (for example Shield on the same L2 or L3 design) consume SMB or internal services here. This is not the primary segment for MOOD public customer apps; those lean on 10.1.0.0/24 and published hostnames.

​

10.1.0.0/24 — MOOD (public production plane)

MOOD hosts production-quality, outward-facing workloads: Coolify MOOD, the media stack (Jellyfin, arr suite, qBittorrent), and other apps you expect to expose or treat as prod. Traffic often leaves via Traefik on DATA and Cloudflare; keep segmentation in mind when opening firewall paths from WAN or overlay.

​

10.2.0.0/24 — SAGE (staging, storage-heavy lab)

SAGE is the staging and experimentation plane with a large dedicated ZFS pool (STUD-zfs). Use it for smaller projects, replicas, and GPU-backed internal APIs (for example local vision or Comfy UI). Think of an internal API layer here as inference or tooling that MOOD or edge proxies might call, not as a substitute for hosted cloud control planes.

​

10.3.0.0/24 — CODE (automation + primary AI accelerator)

CODE is the automation and AI accelerator host: NVIDIA Tesla P40, canonical Supabase and n8n VMs, PegaProx, and Ollama (for example 10.3.0.33:11434 on the CODE VLAN). It is the default home for heavy automation, databases used by agents, and GPU inference that the rest of the estate depends on. Reconcile exact IPs with live Proxmox and the Data Center Map after changes.

​

10.4.0.0/24 — CASA (capacity and isolation)

CASA provides general-purpose cluster capacity without pinning you to MOOD public-facing posture or CODE core automation. Use it for migration targets, burst capacity, or experiments that should remain logically separate from production customer paths while still joining cluster storage (for example hyper-mnky-shared NFS).

​

MNKY-HQ (standalone)

MNKY-HQ is not one of the five cluster nodes in the summary table. It hosts pfSense and cluster-adjacent networking; management may use a distinct prefix (for example 101.0.0.0/24 — see MNKY-HQ node). Do not conflate HQ management space with DATA 10.0.0.0/24.

​

Overlay (NetBird)

NetBird uses CGNAT 100.64.0.0/10 on peer interfaces (wt0). RFC1918 site routes (10.0.0.0/24 through 10.4.0.0/24 and internal segments) are advertised from the pfSense hub peer. Details: NetBird.

​

Operational hygiene

When you add or move a service:

1. Record which segment it belongs to and whether it is internal-only or internet-published.
2. Update datacenter.env (or Infisical) variable blocks — see Datacenter Environment Inventory.
3. Refresh the Data Center Map and any affected node deep dives.

​

Related pages