docs: record unifi firewall enforcement and closeout
Some checks failed
secret-guardrails / artifact-secret-scan (push) Has been cancelled
secret-guardrails / gitleaks (push) Has been cancelled

This commit is contained in:
Fizzlepoof
2026-05-23 02:08:15 +00:00
parent bec21292de
commit 462b39e572
14 changed files with 841 additions and 41 deletions

View File

@@ -0,0 +1,51 @@
# Google/Cast Batch Move Result — 2026-05-23
Purpose: record the live move of the Google/Chromecast-class clients onto IoT for household testing.
## First pilot device
The first device I kicked over earlier was:
- `dc:e5:5b:8f:57:d2`
That device is now verified on IoT with:
- IP: `10.5.10.161`
- network: `IoT`
- VLAN: `510`
## Additional Google/cast-class devices moved to IoT
Using the same per-client virtual-network override method plus reassociation kick, these were also moved and verified:
- `3c:8d:20:f3:92:36` -> `10.5.10.56`
- `90:ca:fa:b6:7f:6e` -> `10.5.10.6`
- `f8:0f:f9:42:08:6d` (`Google-Home-Mini`) -> `10.5.10.196`
## Current verified state
All four target Google/cast-class clients now show:
- network: `IoT`
- network id: `6963cb461131084f05461642`
- VLAN: `510`
- virtual network override: enabled to the IoT network
Verified client set:
- `dc:e5:5b:8f:57:d2` -> `10.5.10.161`
- `3c:8d:20:f3:92:36` -> `10.5.10.56`
- `90:ca:fa:b6:7f:6e` -> `10.5.10.6`
- `f8:0f:f9:42:08:6d` -> `10.5.10.196`
## Method used
For each client:
1. `PUT rest/user/<user_id>` with:
- `virtual_network_override_enabled=true`
- `virtual_network_override_id=6963cb461131084f05461642`
2. `POST cmd/stamgr` with `{"cmd":"kick-sta","mac":"<mac>"}`
3. wait for reassociation and DHCP settle to a `10.5.10.x` address
## Next step
John should now test from the real household path:
- Plex playback
- casting/discovery
- Dispatcharr if relevant
If behavior is bad, rollback is straightforward per client:
- disable that client virtual network override
- kick the station again
- verify it returns to the prior lane/subnet