Candidati ICE e connettività
Esplori i candidati ICE, il modo in cui rappresentano gli indirizzi di rete e come ICE faciliti la ricerca del percorso migliore per una connessione peer-to-peer.
Candidati ICE e connettività è una lezione Real-Time Streaming Systems (WebRTC + Live Data) gratuita su CoddyKit. Questa è la lezione 3 di 4. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento Real-Time Streaming Systems (WebRTC + Live Data), e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso Real-Time Streaming Systems (WebRTC + Live Data) include 4 lezioni in totale.
Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.
ICE: The Connectivity Finder
ICE stands for Interactive Connectivity Establishment. It's a crucial framework in WebRTC that helps establish direct connections between peers, even when they are behind tricky networks like NATs or firewalls.
Think of ICE as a smart detective. It finds all possible routes for two people to talk directly and then picks the best one.
Overcoming Network Barriers
Many devices connect to the internet through routers that use NAT (Network Address Translation) or have firewalls. These act like security guards, often blocking direct incoming connections.
- NAT: Hides private network IPs behind a single public IP.
- Firewalls: Block unauthorized access.
Without ICE, establishing a direct peer-to-peer connection in such environments would be nearly impossible.
What Are ICE Candidates?
An ICE Candidate is essentially a potential network address and port where a peer can be reached. Each peer collects multiple candidates representing different ways it can communicate.
These candidates are like different phone numbers or addresses you might have: your home number, your work number, a friend's number where you can be reached, etc. ICE tries them all.
Types of ICE Candidates
There are three main types of ICE candidates:
- Host Candidates: These are the peer's actual local IP addresses. They work best for direct connections within the same local network.
- Server Reflexive Candidates: Obtained from a STUN server. This is your public IP address and port as seen by an external server, helping peers behind NATs find each other.
- Relayed Candidates: Obtained from a TURN server. If direct connection isn't possible, a TURN server relays all traffic. This is the last resort.
Gathering Candidates: The Process
When a WebRTC connection is initiated, each peer's browser (the WebRTC agent) starts collecting ICE candidates. It actively queries the local network, STUN servers, and potentially TURN servers to find all possible communication paths.
This collection process happens continuously in the background as the RTCPeerConnection is being set up.
Code: Listening for Candidates
In JavaScript, you listen for icecandidate events on your RTCPeerConnection object to get these candidates. Each event provides a new candidate to share with the remote peer via your signaling server.
const pc = new RTCPeerConnection();
pc.onicecandidate = (event) => {
if (event.candidate) {
console.log("New ICE candidate found:");
console.log(event.candidate.candidate);
// Send this candidate to the remote peer via signaling server
} else {
console.log("ICE candidate gathering complete.");
}
};
console.log("Listening for ICE candidates...");
// Note: This snippet requires a full browser WebRTC context to run
// and produce actual candidates. It's for demonstration.Exchanging Candidates: Signaling
Once candidates are gathered, they must be exchanged between the two peers. This happens through your signaling server, the same server used to exchange SDP offers and answers.
- Each peer sends its collected candidates to the signaling server.
- The signaling server forwards these candidates to the other peer.
This process is often called "trickle ICE" because candidates are sent as they are found, rather than waiting for all of them.
The Connectivity Check
After exchanging candidates, ICE begins its connectivity checks. Both peers try to establish connections using every possible pair of local and remote candidates. This involves sending small "STUN binding requests" to test reachability.
ICE then prioritizes and selects the most efficient and reliable path. It prefers direct host connections, then STUN-relayed public IPs, and finally TURN-relayed connections.
Quick Check: ICE Candidate Types
Which type of ICE candidate is obtained with the help of a STUN server to reveal a peer's public IP address?
Recap: ICE in Action
In this lesson, you learned about ICE Candidates and how they enable WebRTC to establish peer-to-peer connections across diverse networks.
- ICE candidates are potential network addresses.
- They come in types: Host, Server Reflexive (STUN), and Relayed (TURN).
- Peers gather and exchange these candidates via a signaling server.
- ICE then performs connectivity checks to find the best possible path for direct communication.
ICE is the unsung hero ensuring your real-time calls find a way through the internet's complexities!
Domande Frequenti
La lezione «Candidati ICE e connettività» è gratuita?
Sì — il testo completo di «Candidati ICE e connettività» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso Real-Time Streaming Systems (WebRTC + Live Data), passa a CoddyKit PRO. Il corso Real-Time Streaming Systems (WebRTC + Live Data) include 4 lezioni in totale.
Cosa imparerò in «Candidati ICE e connettività»?
Esplori i candidati ICE, il modo in cui rappresentano gli indirizzi di rete e come ICE faciliti la ricerca del percorso migliore per una connessione peer-to-peer. Eserciti Real-Time Streaming Systems (WebRTC + Live Data) con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.
Ho bisogno di esperienza per iniziare Real-Time Streaming Systems (WebRTC + Live Data)?
Non è richiesta alcuna esperienza precedente. Real-Time Streaming Systems (WebRTC + Live Data) su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 3 di 4.
Quanto tempo richiede la lezione «Candidati ICE e connettività»?
La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.
Posso scrivere ed eseguire codice in questa lezione Real-Time Streaming Systems (WebRTC + Live Data)?
Sì. Ogni lezione Real-Time Streaming Systems (WebRTC + Live Data) include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.
Tutte le lezioni di questo corso
- Il ruolo dei server di signaling
- SDP: Session Description Protocol
- Candidati ICE e connettività
- Rinegoziazione e stato della connessione