- Full Obsidian vault content - Host configs (ice, grizzley, ubuntu, proxmox, truenas, panda, hyte) - Media stack documentation - Traefik HA setup - Automation scripts - Bachelor party planning
2.7 KiB
2.7 KiB
project
| project | |||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
UniFi Final Change Report 2026-03-17
Before
Managementincluded bothDefaultandFamily of D.ubuntu,proxmox, andtruenasstill used legacy192.168.1.xpathsgrizzleyandicestill had active Wi-Fi participation onFamily of D.truenas,grizzley, andicestill had staging-side192.168.40.xaddresses- staging access policies were still enabled
After
Family of D.now lives inInternalManagementnow maps only toDefault- legacy
192.168.1.xremoved from:ubuntuproxmoxtruenas
- Wi-Fi removed from:
grizzleyice
- staging
192.168.40.xremoved from:truenasgrizzleyice
- disabled:
Vpn to StagingAllow Servers to Staging
Verified Retained 192.168.30.x Paths
These were intentionally retained because they still expose live service endpoints:
| Host | Retained Address | Verified Ports |
|---|---|---|
ubuntu |
192.168.30.61 |
80, 443, 8096 |
proxmox |
192.168.30.11 |
22, 8006, 3128 |
grizzley |
192.168.30.84 |
80, 443, 8080 |
ice |
192.168.30.197 |
22, 4096, 18791 |
Controller State Notes
- UniFi no longer shows the removed legacy
192.168.1.61path forubuntu - UniFi shows
iceonly on the wired production path - UniFi still shows one disconnected/no-IP
grizzleyIoT-side record - A direct delete attempt against that stale
grizzleyclient record returnedapi.err.NotFound, so the safest assumption is controller-history lag rather than an active client entry
Remaining Follow-Up
- Decide service-by-service whether the retained
192.168.30.xaddresses should remain long-term - Allow the stale disconnected
grizzleyUniFi record to age out, or revisit if it persists - Review public
HTTPexposure and duplicate firewall rules in a future maintenance pass