4 ms·
Does this also work between two peers that are behind NAT's / routers? From what I vaguely remember when I tried playing around with this stuff, some NAT's / r
by ackbar03 4y ago
Does this also work between two peers that are behind NAT's / routers?
From what I vaguely remember when I tried playing around with this stuff, some NAT's / routers have some sort of port randomization thing so that the same ports don't always reach the desired location behind it.
Does WebRTC make that port connection persistent due to the streaming nature of it; is that the idea? Does the stream ever break and does it require getting ip and port information from the STUN and ICE servers again? If so, how often does that happen?
- 411111111111111 4y agoThe NAT hole punching they mentioned is a workaround for exactly that scenario. While I'm not involved in the project whatsoever, I'd expect that to work in most scenarios considering they've explicitly mentioned it. It's not a guarantee however and can get circumvented if the network owner wants to https://en.wikipedia.org/wiki/Hole_punching_(networking)#:~:text=Hole%20punching%20(or%20sometimes%20punch,network%20address%20translation%20(NAT) https://en.wikipedia.org/wiki/Hole_punching_(networking)#:~:....
- pojntfx 4y agoFrom my experience it works basically everywhere, but if it doesn't - just specify a TURN server on `--ice` and you'll be able to connect to a relay ^^ The ports/IP can actually change - I was traveling through Germany by train recently for example and whenever my public IP changed it signaled the updated candidates using trickle ICE :)