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

Integrate nat testing tool into ipfs daemon #4352

Open
whyrusleeping opened this issue Oct 29, 2017 · 8 comments
Open

Integrate nat testing tool into ipfs daemon #4352

whyrusleeping opened this issue Oct 29, 2017 · 8 comments
Labels
kind/feature A new feature

Comments

@whyrusleeping
Copy link
Member

I wrote a tool to help diagnose NAT setups: https://github.com/whyrusleeping/natest

I'm thinking we should look at integrating it into the ipfs daemon. A simple way would be to make an ipfs diag nat utility that runs the diagnostic, then advises the user on potential config changes they should make.

Slightly more interesting is doing this automatically (either on init, or on daemon startup) and automatically setting certain config options (as described here).

@whyrusleeping whyrusleeping added the help wanted Seeking public contribution on this issue label Oct 29, 2017
@overbool
Copy link
Contributor

overbool commented Sep 9, 2018

Hey @whyrusleeping , does this work need to continue? I found the compiling error undefined: swarm.NewNetwork in https://github.com/whyrusleeping/natest/blob/master/main.go. Maybe it should use new libp2p method.

@Stebalien
Copy link
Member

It should.

@vyzo
Copy link
Contributor

vyzo commented Sep 13, 2018

We are planning to integrate services for NAT autodetection: see #4993.

@vyzo
Copy link
Contributor

vyzo commented Sep 13, 2018

Implementation WIP: libp2p/go-libp2p-autonat#1

@overbool
Copy link
Contributor

@vyzo I'm interested in it, is there anything I can do to help?

@momack2 momack2 added this to Inbox in ipfs/go-ipfs May 9, 2019
@Stebalien Stebalien added needs refinement help wanted Seeking public contribution on this issue kind/feature A new feature and removed help wanted Seeking public contribution on this issue needs refinement labels May 16, 2019
@Stebalien
Copy link
Member

Stebalien commented May 16, 2019

Blocked on libp2p/go-libp2p#467. At the moment, there's no good way to access the NAT client from go-ipfs.

@momack2
Copy link
Contributor

momack2 commented Mar 5, 2020

Checking in on this issue - is it still blocked?

@Stebalien
Copy link
Member

We've worked around the issue with an event bus. We can (once we cut a libp2p release) listen for nat routability events.

I've filed #6951 to track printing this to stdout automatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature A new feature
Projects
No open projects
Development

No branches or pull requests

5 participants