-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
webrtc: private/browser-to-private/server #2009
Comments
@p-shahi working branch for this work: https://github.com/ckousik/go-libp2p/tree/ckousik/webrtc-m3 |
What's gonna be our strategy for finding STUN servers ? Given STUN is cheap and can be easily rate limited I would argue public go-libp2p servers should include a STUN server, similar to how autonat and relay v2 is implemented right now, then in Kubo I can do the same thing I do for relay v2 where I select nodes based on the DHT keyspace. |
I don't have a good solution here. I would start with this, i.e. I would start with a hard-coded set of servers. Though products would need to make it explicit to the user that they are using the services of company X. |
Bump: I can see many open PRs. Any update on this? |
We have prioritized other work right now and this won't be picked up for a few more months. I first want to get /webrtc-direct in non experimental mode and then work on adding webrtc private to private. I can help if someone is interested in working on this and landing this in. Out of curiority, what do you need this for? |
To reduce confusion (for myself and others), is this issue is solely focused on the WebRTC spec and not the WebRTC-Direct spec? Can you confirm this @sukunrt? |
@2color correct |
eta: 2023-09-30
This is the browser side implementation in go-libp2p (a scenario where the go-libp2p node is in a private network e.g. behind a NAT/firewall). It is required for a browser node to hole punch to a private non-browser node and will “complete” the browser connectivity story.
Done Criteria
The text was updated successfully, but these errors were encountered: