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

NAT traversal #2052

Open
9 of 14 tasks
mxinden opened this issue Apr 20, 2021 · 13 comments
Open
9 of 14 tasks

NAT traversal #2052

mxinden opened this issue Apr 20, 2021 · 13 comments
Labels
tracking-issue Issues which are the entry point to bigger projects.

Comments

@mxinden
Copy link
Member

mxinden commented Apr 20, 2021

This GitHub issue tracks the status of NAT traversal capabilities for rust-libp2p. For an overview across libp2p implementations see libp2p/specs#312.

Please comment below to suggest additions or corrections.

Contributions of any form are welcome. Before you start working on something, please comment below to make sure no work is duplicated.


Transport protocols

TURN-like protocols

Signaling protocols

STUN-like protocols

Other protocols

Misc

@mxinden
Copy link
Member Author

mxinden commented Apr 27, 2021

Changelog

@dvc94ch dvc94ch mentioned this issue May 4, 2021
@mxinden
Copy link
Member Author

mxinden commented May 4, 2021

Changelog

@mxinden
Copy link
Member Author

mxinden commented May 5, 2021

Changelog

@mxinden
Copy link
Member Author

mxinden commented May 25, 2021

Changelog

r-zig added a commit to r-zig/rust-libp2p that referenced this issue May 26, 2021
with all peers run together via docker compose libp2p#2052
@mxinden
Copy link
Member Author

mxinden commented Jul 23, 2021

Changelog

@mxinden
Copy link
Member Author

mxinden commented Sep 26, 2021

@mxinden
Copy link
Member Author

mxinden commented Oct 14, 2021

Changelog

@mxinden
Copy link
Member Author

mxinden commented Nov 25, 2021

Great news! I have been able to punch through both NATs and Firewalls using #2066 #2059 and #2076.

The "only" thing missing for basic hole punching in rust-libp2p are code-reviews for the pull requests above.

Do folks have some time to spare? I know it is a large amount of code. Reviews of subsets are just fine. Maybe @thomaseizinger, @elenaf9. @wngr, @divagant-martian or @MarcoPolo? 😇

Also happy to post a write-up on how folks can punch some holes themselves in case there is interest.

@mxinden
Copy link
Member Author

mxinden commented Nov 28, 2021

@mxinden
Copy link
Member Author

mxinden commented Jan 14, 2022

Changelog

@mxinden
Copy link
Member Author

mxinden commented Feb 9, 2022

Changelog

Thus all protocols for basic hole punching are in master now 🎉 If you want to punch holes yourself, check out #2460.

@thomaseizinger thomaseizinger changed the title NAT traversal tracking issue (rust-libp2p) Tracking issue for NAT traversal Sep 17, 2023
@thomaseizinger thomaseizinger changed the title Tracking issue for NAT traversal NAT traversal Sep 19, 2023
@thomaseizinger thomaseizinger added the tracking-issue Issues which are the entry point to bigger projects. label Sep 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tracking-issue Issues which are the entry point to bigger projects.
Projects
None yet
Development

No branches or pull requests

2 participants