-
Notifications
You must be signed in to change notification settings - Fork 213
Turn server #13
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
Comments
Hi @chrisooo3, do you mean behind the same NAT? If they were behind the same NAT, they could just talk directly. If you mean behind two separate NATs, then yes, that's what TURN is designed for but I'm not sure how you're suggesting it be applied here. Will you provide more context? |
@samyk I mean behind two separate NATs. I would like to use stun to connect to device which is outside of my network. |
STUN and TURN will allow you to do that, though I don't think the slipstream technique is relevant. You may also be interested in other P2P technologies like https://samy.pl/pwnat/ which I hope to be releasing a modernized version of soon around a new technique. The benefit there is no dependence on a 3rd party server (such as a TURN or STUN server), however it will have much lower reliability than purpose-built relay protocols like TURN. |
@samyk I have already running server in LAN behind the nat. So it is not reachable from outside. How can I use stun server to obtain the public ip address of this web server, which is behind router and nat? |
Hi @samyk
Have you been thinking about using a turn server to establish a connection between two machines behind NAT?
If not could you explain why?
The text was updated successfully, but these errors were encountered: