Chrome appears to create workable local ICE candidates even when STUN/TURN servers are down--can I use them somehow?

Question

I'm using the chrome://webrtc-internals/ URL to debug our WebRTC application behavior when the STUN/TURN servers are down. One interesting thing I'm noticing is that under "Stats Tables" there appear to be good, "peerreflexive" local ICE candidates being generated, for example:

Cand-2rjZ43jF (localcandidate)
Statistics Cand-2rjZ43jF
timestamp   10/24/2017, 9:19:39 AM
ipAddress   192.168.59.1
networkType unknown
portNumber  40555
priority    1845501695
transport   udp
candidateType   peerreflexive

The thing is this candidate never comes to me through the onicecandidate callback.

Is this just an internal quirk of Chrome or is there a way to get these perfectly good candidates?

Answer 1

I don't know exactly how this ICE candidate is generated. But as you can see, the candidate points to 192.168.59.1 which is your LAN IP address. So this candidate will only work for connecting to someone at the same LAN as you're computer.