Update Legion LAN IP from 192.168.68.77 to 192.168.8.148

Static IP assigned on new network segment. Updates:
- variables.tf default legion_ip
- headscale nameserver config
- bootstrap.sh default target
- README/RUNBOOK documentation
- media ingress comment
This commit is contained in:
Will Anderson
2026-04-21 10:32:30 -05:00
parent 26c7d2259e
commit 3b3811942c
6 changed files with 12 additions and 12 deletions
+4 -4
View File
@@ -2,7 +2,7 @@
Ubuntu 24.04 home server running k3s. Hosts all personal and platform infrastructure.
**LAN IP:** `192.168.68.77`
**LAN IP:** `192.168.8.148`
**SSH:** `ssh legion`
**Kubeconfig:** `~/.kube/legion-config`
@@ -76,14 +76,14 @@ git push # Argo CD auto-syncs within ~30s
## Networking
**Router:** TP-Link Deco BE5000 mesh network, router mode. Subnet `192.168.68.x`, DHCP DNS points to AdGuard (`192.168.68.77`).
**Router:** TP-Link Deco BE5000 mesh network, router mode. Subnet `192.168.68.x`, DHCP DNS points to AdGuard (`192.168.8.148`).
External traffic reaches Legion two ways:
1. **Cloudflare Tunnel** — public services (`*.neuralplatform.ai`) route through a tunnel pod in k8s. No ports open on the router.
2. **Direct port forward** — DoT on port 853 (TCP) is forwarded from the router to `192.168.68.77:853`. Required because Cloudflare can't proxy raw TCP.
2. **Direct port forward** — DoT on port 853 (TCP) is forwarded from the router to `192.168.8.148:853`. Required because Cloudflare can't proxy raw TCP.
LAN devices use AdGuard as their DNS server (`192.168.68.77`). AdGuard rewrites `*.nook.family` and `*.neuralplatform.ai` to the LAN IP so local traffic stays local.
LAN devices use AdGuard as their DNS server (`192.168.8.148`). AdGuard rewrites `*.nook.family` and `*.neuralplatform.ai` to the LAN IP so local traffic stays local.
ddclient keeps the `dot.nook.family` A record updated if the home IP changes.