3 ms·
This article is essentially claiming that for WebRTC to use TCP you have to be using TURN. While I am willing to believe I am wrong here (our product feels a bi
by saurik 6y ago
This article is essentially claiming that for WebRTC to use TCP you have to be using TURN. While I am willing to believe I am wrong here (our product feels a bit crippled over TCP to the point where I just recommend you not use it, so if it isn't working I might not even notice), I am nearly certain this is not true.
- Sean-Der 6y agoYou are right, ICE does support TCP. Not all ICE implementations support it though, probably where the incorrect anecdote comes from. ICE TCP did get a little more limited recently in Chromium though [0] because of the TCP port scanning issue [1] I have also heard that some gateways/firewalls/$x don't allow any non-TLS traffic, so you can't even establish ICE. In those cases the DTLS/TLS transport of TURN is nice. [0] https://lists.w3.org/Archives/Public/public-webrtc/2020Feb/0022.html https://lists.w3.org/Archives/Public/public-webrtc/2020Feb/0... [1] https://medium.com/tenable-techblog/using-webrtc-ice-servers-for-port-scanning-in-chrome-ce17b19dd474 https://medium.com/tenable-techblog/using-webrtc-ice-servers...