-
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
Update IPFS network diagnostics with NAT type #1043
Comments
Is there anything we expect an end user to be able to do based on the NAT type? it might be vaguely interesting to say, but i'm not sure if the explanation can change much as a result. |
@willscott Ask them to currently give up all hopes of being reachable on the Internet and also...change their ISP :) |
I need this feature too, I think this is useful. |
Should this issue be move to IPFS? I don't think there's anything actionable here on the go-libp2p side. |
I don't have permissions here. Maybe @p-shahi does? |
I'll close this issue here and create a new one in IPFS (can't move issues across organizations.) |
Once ipfs/kubo#7068 AND #1042 are merged,
we should update the network diagnostics in IPFS to also emit the NAT type to the use and corresponding explanation regarding Hole Punching.
The text was updated successfully, but these errors were encountered: