Investigate why the Pearl-2 (11.0.6.76) has no internet egress so the YouTube livestream cannot send data. Sub-ticket of the livestream contingency (#687).
Known facts (verified 2026-09-10 via the Pearl API and the Mac mini on the same gateway):
- Pearl encodes fine (channel 2, 6.2 Mbps) but transmits almost nothing to YouTube; YouTube Studio shows "No data".
- Pearl eth0: IP 11.0.6.76, gateway 11.0.0.1, DNS 8.8.8.8, /20, link 1Gbps, default route status ok.
- Mac mini turbo-pancake-76 (11.0.5.207) on the SAME gateway 11.0.0.1 reaches YouTube RTMPS fully (TLS verify code 0). So the venue path works from 11.0.5.x but not from the Pearl at 11.0.6.x.
Key lead from Tom (2026-09-10): yesterday he changed the Pearl's default gateway from 0.0.0.0 to 8.8.8.8 to make streaming work. Note 8.8.8.8 is a DNS address, not a valid gateway; the Pearl currently reads gateway 11.0.0.1 / DNS 8.8.8.8. This suggests the Pearl's network settings are unstable or revert on reboot (it worked yesterday after Tom's change, then failed today after the reboots).
To investigate:
- Confirm the Pearl's intended gateway (should be 11.0.0.1) and whether the setting reverts after a reboot or power-cycle.
- Clarify with Tom exactly what he changed (gateway vs DNS) and whether it was static or DHCP.
- Determine whether the venue firewall (Citymesh) isolates the 11.0.6.x AV subnet from internet egress while allowing 11.0.5.x.
- Fix: set a correct, persistent gateway on the Pearl, and/or have Citymesh open egress for 11.0.6.76 to YouTube ingest (TCP 1935 and 443) + DNS. Alternatively move the Pearl to a drop/subnet with proven egress (the 11.0.5.x network the Mac uses).
Once egress is restored the publisher (already configured with the correct key and started) goes live automatically.