PeerShare Diagnostics

Go/no-go gate: can two devices on this network gather ICE candidates that resolve to each other? No STUN/TURN is configured, and nothing is sent to any server. Everything runs in this page.

1. Environment

2. Candidate gathering

Creates an RTCPeerConnection with no ICE servers and a data channel, then waits for iceGatheringState === 'complete'.

The comparison gathers once, asks for microphone permission, gathers again, then releases the mic. Chrome only exposes real LAN IPs (instead of .local names) after a media permission is granted. If permission was already granted for this site, the first run will already show real IPs. Reset the site's permissions to see the difference.

3. Two-device connection test (the actual gate)

Open this page on two devices. On device A press Create offer and copy it to device B (any way you like: paste, messaging, QR later). On B paste it and press Accept offer, then copy B's answer back to A and press Accept answer. If the data channel opens and ping works, direct LAN connectivity is proven. Same encoding as the planned QR payload (stripped SDP, deflate-raw, base64url).

idle

4. Report