0Pricing
Real-Time Streaming Systems (WebRTC + Live Data) · 课时

STUN 服务器功能详解

了解 STUN（用于 NAT 会话穿越）服务器如何帮助对等端发现其公共 IP 地址和端口映射。

STUN 服务器功能详解 是 CoddyKit 上的免费 Real-Time Streaming Systems (WebRTC + Live Data) 课时。 这是第 2 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Real-Time Streaming Systems (WebRTC + Live Data) 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Real-Time Streaming Systems (WebRTC + Live Data) 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

What is a STUN Server?

Welcome! Today we'll unravel the mystery of STUN servers. STUN stands for Session Traversal Utilities for NAT. It's a key technology that helps WebRTC connections work.

Its main job is to help devices behind a NAT (Network Address Translator) discover their public IP address and port number. This is crucial for establishing direct peer-to-peer connections.

NAT: A Quick Reminder

Remember NAT from our previous lesson? NAT helps multiple devices in a private network share a single public IP address. While great for conserving IPs, it hides your device's true network address from the outside world.

For WebRTC, this is a problem! Peers need to know each other's actual, routable addresses to connect directly. STUN is here to solve this.

STUN's Core Function: Discovery

Think of a STUN server as a friendly helper on the public internet. When your device wants to know its public identity, it asks the STUN server, "Hey, what's my public IP and port from your perspective?"

The STUN server replies with the public address it observed your request coming from. This is your device's public 'face' to the internet.

The STUN Request Flow

Here's how a STUN request typically works:

  • Your WebRTC client sends a 'binding request' to a known STUN server.
  • This request travels through your local network and then through your NAT.
  • The NAT modifies the packet, assigning a public IP and port before sending it out.
  • The STUN server receives this request.

Understanding the STUN Response

When the STUN server gets your request, it records the source IP and port of the incoming packet. This is what it sees as your public address.

It then sends a 'binding response' back to your client, containing this observed public IP and port. Your client now knows how it appears to the outside world!

Binding Requests in Detail

The 'binding request' isn't just a simple 'hello'. It's a specific message format defined by the STUN protocol.

  • It contains a transaction ID to match requests with responses.
  • It asks the server to reflect the client's observed network address.
  • The response carries attributes like XOR-MAPPED-ADDRESS, which is the public IP and port.

STUN & WebRTC's ICE

STUN servers are a fundamental part of WebRTC's ICE (Interactive Connectivity Establishment) framework.

ICE uses STUN (and sometimes TURN) to gather all possible network addresses (called 'candidates') for a peer. These candidates include local IPs, public IPs (from STUN), and relayed IPs (from TURN).

Configuring STUN in WebRTC

In WebRTC, you configure STUN servers as part of your RTCPeerConnection setup. The browser then handles the communication with the STUN server automatically to gather ICE candidates.

Here's how you define a STUN server for your peer connection:

const configuration = {
  iceServers: [
    {
      urls: 'stun:stun.l.google.com:19302'
    }
  ]
};

const peerConnection = new RTCPeerConnection(configuration);

// The browser will now use the STUN server
// to discover public IP/port for ICE candidates.

STUN vs. NAT Types

STUN works very well with certain types of NATs, like Full Cone NAT and Restricted Cone NAT, where the mapping of internal to external ports is consistent.

However, STUN can struggle with more complex NATs, such as Symmetric NATs. For these, a TURN server (which we'll cover next!) is often required to relay traffic.

Test Your STUN Knowledge

Which of the following best describes the primary role of a STUN server in WebRTC?

STUN: Your NAT Helper

Great job! You've learned that STUN (Session Traversal Utilities for NAT) servers are vital for WebRTC.

  • They help devices behind NATs find their public IP and port.
  • This discovery is crucial for ICE to gather connectivity candidates.
  • STUN works well for many NAT types, but not all.

Next, we'll explore TURN servers, which tackle the toughest NAT challenges!

常见问题解答

「STUN 服务器功能详解」课时是免费的吗？

是的 — 「STUN 服务器功能详解」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Real-Time Streaming Systems (WebRTC + Live Data) 课程的其余内容，请升级到 CoddyKit PRO。 Real-Time Streaming Systems (WebRTC + Live Data) 课程共包含 4 节课。

「STUN 服务器功能详解」这节课中我会学到什么？

了解 STUN（用于 NAT 会话穿越）服务器如何帮助对等端发现其公共 IP 地址和端口映射。 你通过在浏览器中直接运行的动手代码来练习 Real-Time Streaming Systems (WebRTC + Live Data)，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Real-Time Streaming Systems (WebRTC + Live Data) 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Real-Time Streaming Systems (WebRTC + Live Data) 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 2 节课，共 4 节。

「STUN 服务器功能详解」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Real-Time Streaming Systems (WebRTC + Live Data) 课中编写并运行代码吗？

能。每节 Real-Time Streaming Systems (WebRTC + Live Data) 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

  1. NAT 与防火墙带来的挑战
  2. STUN 服务器功能详解
  3. 用于中继连接的 TURN 服务器
  4. 部署并保护您自己的 TURN 服务器
← 返回 Real-Time Streaming Systems (WebRTC + Live Data)