Protocols
Saved & recent

Session Traversal Utilities for NAT

Also called: STUN, server-reflexive address

STUN supplies building blocks for NAT traversal. A binding request can reveal the source IP address and port that a server observes, which may differ from a device’s local address. STUN messages also support connectivity checks and maintaining mappings in a larger protocol design.

A laptop might send from a private address while a STUN server sees a router’s public address and translated port. That observation can help ICE build a candidate. STUN does not relay the application’s audio or video, and learning a mapped address does not guarantee that another peer can send traffic through the NAT to it.

Related
Interactive Connectivity Establishment, Traversal Using Relays around NAT, UDP
Further reading
IETF RFC 8489 — Session Traversal Utilities for NAT
local laptop NAT STUN server binding request mapped source reply · observed mapped endpoint 203.0.113.7:62000 illustrative documentation endpoint
A STUN server reports the endpoint it observes. This example uses a documentation address; reachability must still be checked.

View in the full Protocols collection