39 lines
1.4 KiB
Markdown
39 lines
1.4 KiB
Markdown
# Google/Cast IoT Test Failure and Rollback — 2026-05-23
|
|
|
|
Purpose: record the failed Chromecast/Plex discovery test after moving Google/cast-class devices to IoT, and the immediate rollback.
|
|
|
|
## Observed failure
|
|
User-tested result:
|
|
- Plex on Chromecast could not see the Plex server after the Google/cast batch was moved to IoT.
|
|
|
|
This is consistent with discovery/cast behavior breaking across the current segmentation boundary.
|
|
|
|
## Rollback action taken
|
|
I reverted the per-client virtual network override and kicked each client to reassociate back to its prior lane.
|
|
|
|
Rolled back devices:
|
|
- `dc:e5:5b:8f:57:d2`
|
|
- `3c:8d:20:f3:92:36`
|
|
- `90:ca:fa:b6:7f:6e`
|
|
- `f8:0f:f9:42:08:6d` (`Google-Home-Mini`)
|
|
|
|
## Verified post-rollback state
|
|
All four now show:
|
|
- network: `Old IoT`
|
|
- network id: `6963e11c1131084f054622f1`
|
|
- virtual network override: disabled
|
|
|
|
Observed IPs after rollback settle:
|
|
- `dc:e5:5b:8f:57:d2` -> `192.168.1.132`
|
|
- `3c:8d:20:f3:92:36` -> `192.168.1.192`
|
|
- `90:ca:fa:b6:7f:6e` -> `192.168.1.129`
|
|
- `f8:0f:f9:42:08:6d` -> `192.168.1.185`
|
|
|
|
## Interpretation
|
|
The current clean IoT placement is not yet compatible with Plex discovery/cast behavior for these Google devices under the present network/policy setup.
|
|
|
|
## Safe next options
|
|
1. Leave Google/cast-class devices on `Old IoT` for now.
|
|
2. Finish other cleanup first.
|
|
3. Later, if desired, design a narrow, intentional cast/discovery exception instead of broad trust expansion.
|