-
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
The port is opened using the upnp protocol, but it is not used #1142
Comments
Given machines:
What's the output of Unfortunately, a lot of NATs are buggy... libp2p tries to guess all reasonable addresses, but this doesn't always work. |
Hope #1057 can fix this problem. |
That might let you do hole punching, but it won't fix this problem. |
Are there any logs to track relevant information? |
Those would be in go-libp2p-nat. You'll have to enable debug logging for the "nat" subsystem, and may want to add additional logging. See ipfs/go-log#120 for documentation on how to enable logging for individual subsystems. |
I'm going to close this for now because there's probably nothing we can do. If you find more information, please leave a comment and we can reopen. |
ok |
Version Information
my router is mi ax6000
ipfs version: 0.9.1
libp2p:v0.14.3
The text was updated successfully, but these errors were encountered: