Summary
TURN (Traversal Using Relays around NAT) is a protocol defined in RFC 8656 that relays traffic between two endpoints when a direct peer-to-peer path cannot be established across NATs or firewalls.
What is TURN?
TURN extends STUN. While STUN only helps peers discover their public mapping so they can talk directly, TURN steps in when direct hole punching fails — for example because of symmetric NAT, carrier-grade NAT, or strict corporate firewalls. The TURN server allocates a public address on behalf of the client and forwards traffic to and from the peer on the other side.
A typical client tries multiple connection paths in parallel: direct host-to-host, direct via STUN-discovered public mappings, and finally relayed via TURN. Frameworks like ICE (Interactive Connectivity Establishment) automate this selection. Because TURN carries actual payload traffic, its servers are bandwidth-sensitive and benefit from being placed close to users.
TURN is widely used by WebRTC, SIP, and modern overlay networks such as WireGuard-based mesh VPNs. NetBird's bundled coturn is a popular open-source TURN/STUN implementation used by many products and self-hosted setups.
Why is TURN relevant?
- Connectivity guarantee: Provides a fallback path even in the strictest NAT or firewall conditions
- Encrypted relay: Forwards encrypted payload without decrypting it, preserving end-to-end protection
- Production reliability: Removes "it works at home but not at the customer site" surprises
- Open source: Robust implementations (notably
coturn) are freely available
Related Terms
- STUN: Companion protocol for direct hole punching; TURN takes over when STUN fails
- NAT Traversal: Broader concept that TURN belongs to as a fallback strategy
- Peer-to-Peer: Communication model that TURN keeps usable behind strict NATs
- Mesh VPN: VPN topology where TURN ensures connectivity in restrictive networks