3 ms·

There are several free STUN services available, and you can fix a lot of connections with just STUN. STUN is just an IP lookup effectively, so it's very cheap t

There are several free STUN services available, and you can fix a lot of connections with just STUN. STUN is just an IP lookup effectively, so it's very cheap to deploy. TURN is of course an entirely different beast because it's proxying all the data between clients. It's also where some more complex video stuff happens potentially. The good news is that there are solid, open source TURN servers available to run on your own hardware. The downside is that running those servers for non-trivial amounts of clients gets pretty resource intensive pretty quick.

zip1234 6y ago
So would STUN allow a connection to be established between a a user inside a LAN and internet user?
- vorpalhex 6y ago
  In my experience you typically don't need STUN for that to work - the ICE flow of WebRTC will handle regular NAT[1]. It's typically when ICE can't determine the first few steps (eg your public address) that you need STUN to help you out. TURN tends to be needed in hostile networking situations like double NAT'd networks or very restricted networks like hospitals. [1] - https://webrtcglossary.com/ice/ https://webrtcglossary.com/ice/