-
Notifications
You must be signed in to change notification settings - Fork 310
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
Connect clients using WAN #47
Comments
Hi @bokidotnet, In theory, by pasting Your WAN IP:Port to other peer and vice versa, then pressing Connect (both) at the same time, you should be able to establish a connection? Thank you. |
I know but that is theory. I tested already and didn't work over wan. |
having same issue, i assume the STUN servers dont matter for p2p?? |
the stun servers that work on my pc at home dont work on my laptop |
Yes Im facing with same issue. Cannot connect through wan |
Hello, can you connect via wan now? |
STUN (Session Traversal Utilities for NAT) enables peer-to-peer connections by allowing devices behind network address translation (NAT) to discover their public IP addresses and determine the best way to establish a connection. However, in certain scenarios like symmetric NAT or strict firewalls, STUN might not work. Symmetric NAT creates unique mappings for each connection, hindering STUN's ability to find the correct address for direct communication. Similarly, strict firewalls might block STUN requests, preventing the establishment of peer-to-peer connections. |
Hi Miroslave,
Can you tell me is there any practical workaround to connect clients over WAN IP's directlly since you have WAN IP's as well?
In local lan working very well.
Nice work!
Keep going.
Cheers.
The text was updated successfully, but these errors were encountered: