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

Hole punching TCP and P2P #1152

Open
leonardospeca opened this issue Oct 10, 2023 · 0 comments
Open

Hole punching TCP and P2P #1152

leonardospeca opened this issue Oct 10, 2023 · 0 comments

Comments

@leonardospeca
Copy link

Hi.
Can you explain why a TCP hole punching doesn't allow to make a peer-to-peer connection anymore?

I have this scenario:

  • supernode v2 on a VPS listening on port 8005
  • supernode v3 on a VPS listening on port 8006
  • NGINX configured that a UDP request to port 443 redirect to local port 8006 (supernode v3)

I would like that
v2.supernode.mysite.com:443 forward to 8005,
v3.supernode.mysite.com:443 forward to 8006

But seems like in UDP with NGINX, HAPROXY or any other program, is not possible to distinguish the request by a subdomain name..

Maybe with the TCP option, the problem could be solved, but we don't want to lose the ability of doing the connection P2P...

I'm trying to do that cause I want to open just a port on the VPS (the 443 UDP or TCP) I tried also something like udp2raw but it doesn't allow to specify a domain name as remote server. Do you have other suggestions?

Thank you very much

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant