Refine IP addressing plan in TODO

DHCP below 100, static VMIDs at 100+ matching their VMID number.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Mikkel Georgsen 2026-01-14 21:58:01 +00:00
parent c935edb0cc
commit eee9aa2a7c

10
TODO.md
View file

@ -2,7 +2,15 @@
## Pending Tasks ## 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) - [ ] **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) - 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)