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

The port is opened using the upnp protocol, but it is not used #1142

Closed
godcong opened this issue Jul 27, 2021 · 7 comments
Closed

The port is opened using the upnp protocol, but it is not used #1142

godcong opened this issue Jul 27, 2021 · 7 comments

Comments

@godcong
Copy link
Contributor

godcong commented Jul 27, 2021

Version Information

  1. When I start the ipfs client, upnp is correctly activated.
    image
  2. But I failed to connect to the local ipfs client through the reverse link.
  3. Then I try to forward the data of port 4001 to ipfs.
  4. The local ipfs client is successfully connected
  5. suspect that although upnp is enabled correctly, ipfs still sends data through port 4001 instead of through upnp port

my router is mi ax6000
ipfs version: 0.9.1
libp2p:v0.14.3

@Stebalien
Copy link
Member

Given machines:

  1. A: behind NAT with peer ID QmA.
  2. B: dialing the peer behind the NAT.

What's the output of ipfs id on machine A, and what's the output of ipfs id QmA on machine B?

Unfortunately, a lot of NATs are buggy... libp2p tries to guess all reasonable addresses, but this doesn't always work.

@godcong
Copy link
Contributor Author

godcong commented Aug 12, 2021

Hope #1057 can fix this problem.
I will try again after this release.

@Stebalien
Copy link
Member

That might let you do hole punching, but it won't fix this problem.

@godcong
Copy link
Contributor Author

godcong commented Aug 19, 2021

That might let you do hole punching, but it won't fix this problem.

Are there any logs to track relevant information?
I want to open these logs to check

@Stebalien
Copy link
Member

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.

@Stebalien
Copy link
Member

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.

@godcong
Copy link
Contributor Author

godcong commented Aug 24, 2021

ok

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants