-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Comments
Hey @whyrusleeping , does this work need to continue? I found the compiling error |
It should. |
We are planning to integrate services for NAT autodetection: see #4993. |
Implementation WIP: libp2p/go-libp2p-autonat#1 |
@vyzo I'm interested in it, is there anything I can do to help? |
Blocked on libp2p/go-libp2p#467. At the moment, there's no good way to access the NAT client from go-ipfs. |
Checking in on this issue - is it still blocked? |
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. |
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).
The text was updated successfully, but these errors were encountered: