From eee9aa2a7c1ca9eec0469944c825fec52bf4c805 Mon Sep 17 00:00:00 2001 From: Mikkel Georgsen Date: Wed, 14 Jan 2026 21:58:01 +0000 Subject: [PATCH] Refine IP addressing plan in TODO DHCP below 100, static VMIDs at 100+ matching their VMID number. Co-Authored-By: Claude Opus 4.5 --- TODO.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/TODO.md b/TODO.md index c2e4b1c..1194907 100644 --- a/TODO.md +++ b/TODO.md @@ -2,7 +2,15 @@ ## Pending Tasks -- [ ] **Review vmbr1 IP addressing scheme** - Consider reorganizing IPs so each container uses IP matching its VMID (e.g., VMID 114 = 10.5.0.114). Shrink DHCP range to 220-253 or similar. Current range is 100-200 which conflicts with some VMIDs. +- [ ] **Reorganize vmbr1 IP addressing scheme** + - New scheme: VMID = IP (e.g., VMID 114 = 10.5.0.114) + - `.1-.9` - Reserved for special services + - `.10-.99` - DHCP range (change from current 100-200) + - `.100-.253` - Static IPs matching VMIDs + - `.254` - Gateway (PVE host) + - Exception: VMID 1000 (tailscale) → use .250 + - Containers to migrate: npm (.1→.100), dockge (.10→.101), pbs (.6→.106), forgejo (.14→.114), dns (.2→.115) + - Already correct: mgmt (.102), general (.113) - [ ] **Fix ping on all unprivileged containers** - Run `setcap cap_net_raw+ep /bin/ping` on each container (requires restart or at least root access inside container) - Containers to fix: 100 (npm), 101 (dockge), 102 (mgmt), 103 (postgresql01), 104 (redis01), 105 (sentry), 107 (pve-scripts-local), 108 (jukebox), 110 (sense), 111 (dev), 112 (dataloes), 114 (forgejo), 115 (dns), 1000 (tailscale)