Talk:Interactive Connectivity Establishment
| This is the talk page for discussing improvements to the Interactive Connectivity Establishment article. This is not a forum for general discussion of the article's subject. |
Article policies
|
| Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
 | This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||
| ||||||||||||||
Unnamed section
editThe terms NAT and Firewall should be carefully considered and contrasted in this topic. While both functions are sometimes combined in a signgle device, ICE's procedures are designed to optimize the NAT Traversal technique chosen, not to traverse firewalls. ICEs techniques (STUN, TURN, etc.) will typically succeed in crossing a router/nat/firewall device designed for minimal administrative managment (i.e. home/small business devices like those marketed under brands like D-Link and Linksys), but will frequently not cross a corporate firewall. This is because the corporate firewall devices are often configured so that UDP traffic is blocked.
24.19.31.45 (talk) 16:51, 3 May 2008 (UTC)
- To my understanding ICE helps in both. STUN is used for the client to gain knowledge of its NAT if there is one and TURN to relay messages through a third party where Firewalls would block peer to peer traffic Mmick66 (talk) 08:21, 3 May 2011 (UTC)
How does ICE work?
editThis page does not at all explain how ICE works. Can someone add some information on the principles and limitations of this? THANKS -- Michael Janich (talk) 03:43, 5 February 2014 (UTC)
- Hmm... Still no explanation. And the text that is on the page talks about NAT, STUN, and TURN, but never mentions how they relate to ICE. Is ICE just the agglomeration of those three protocols? Ben (talk) 20:23, 19 November 2021 (UTC)