matsandClaude Sonnet 5
5836424baf
A connection failing specifically when both peers are on the same LAN (as opposed to over the open internet) usually means direct/STUN candidates are being silently dropped by the router — either AP/router client isolation (common on home/guest Wi-Fi) or no NAT hairpin/ loopback support for two LAN devices reaching each other via their own public IP. On the first retry after a connection failure, set iceTransportPolicy: 'relay' so the rebuilt RTCPeerConnection only offers TURN-relayed candidates, bypassing the LAN path entirely. Confirmed the coturn secret and pod are up in-cluster so relay auth will actually succeed. Only one side needs to do this — since it only offers relay candidates, whatever pairs with them is forced through the relay regardless of what the other side additionally tried. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>