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

Use DCUtR to synchronize hole punching #1460

Closed
Tracked by #1461
p-shahi opened this issue Oct 20, 2022 · 3 comments · Fixed by #1928
Closed
Tracked by #1461

Use DCUtR to synchronize hole punching #1460

p-shahi opened this issue Oct 20, 2022 · 3 comments · Fixed by #1928
Labels
kind/architecture Core architecture of project

Comments

@p-shahi
Copy link
Member

p-shahi commented Oct 20, 2022

@p-shahi p-shahi added the kind/architecture Core architecture of project label Oct 20, 2022
@BigLep
Copy link
Contributor

BigLep commented Jun 14, 2023

@p-shahi : I assume this is needed for browsers being able to dial or be dialable by server nodes with WebRTC. Is that right?

@SgtPooki
Copy link
Member

related: ipfs/helia#180

@aschmahmann
Copy link
Collaborator

Related to the linked issue(s) above. If implementing synchronized hole punching via DCUtR is going to take a while, it's probably worth doing the minimal amount of DCUtR that enables dialbacks to nodes that are publicly reachable.

While it's only a subset, it's likely an easier subset and unlocks js-libp2p nodes (including those in browsers) being reachable by any libp2p node which is itself publicly reachable (on a shared transport). This enables a path forward for users to build systems where their browser nodes are reachable from non-browser nodes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/architecture Core architecture of project
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants