Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure TURN servers for the proxy and/or client #18

Closed
keroserene opened this issue Jan 26, 2016 · 1 comment
Closed

Configure TURN servers for the proxy and/or client #18

keroserene opened this issue Jan 26, 2016 · 1 comment

Comments

Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@keroserene
Copy link
Owner

@keroserene keroserene commented Jan 26, 2016

This may require spinning up our own TURN servers somewhere.

In most cases, the public ip candidates given by STUN servers are sufficient for peers to negotiate a working p2p path. But sometimes, maybe 14% of the time [1], this isn't enough -- usually due to symmetric NAT / lack of port preservation, and a TURN relay is required as a last resort.

Also, once snowflake proxies & clients are multiplexed, perhaps the likelihood that TURN continuous to be absolutely required for every pair of peers greatly decreases and we might be fine again. More thought is needed here.

@arlolra
Copy link
Collaborator

@arlolra arlolra commented Mar 22, 2018

@arlolra arlolra closed this Mar 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment