-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Open
Labels
P2Medium: Good to have, but can wait until someone steps upMedium: Good to have, but can wait until someone steps uparea/networkeffort/hoursEstimated to take one or several hoursEstimated to take one or several hourskind/featureA new featureA new featuretopic/libp2pTopic libp2pTopic libp2p
Description
Checklist
- My issue is specific & actionable.
- I am not suggesting a protocol enhancement.
- I have searched on the issue tracker for my issue.
Description
Problem
Users currently have no easy way to determine if their IPFS node is publicly reachable. Indeed, you can use the ipfs id to see your IP addresses, however, due to circuit relay multiaddrs and the many transports, it's not very user friendly. There are also situations when ipfs id returns a public IP that isn't in fact reachable.
Proposed Solution
Add ipfs stats network command that:
- Reports reachability status:
public,private, orrelayed(if you have circuit relay reservations. - Shows the external IP address(es) and port(s) other peers can reach you on
- Uses AutoNAT for determining the output
Example Output
$ ipfs stats network
Public Reachability: public
External Addresses:
- /ip4/203.0.113.42/tcp/4001/p2p/...
- /ip6/2001:db8::1/tcp/4001/p2p/...
AutoNAT Status: public (confirmed by 3/5 peers)
Note: We could also return JSON
Where this might be useful
This can help a lot in the IPFS docs for debugging information and guides focused on publishing data where this matters for retrieval without NAT traversal.
Metadata
Metadata
Assignees
Labels
P2Medium: Good to have, but can wait until someone steps upMedium: Good to have, but can wait until someone steps uparea/networkeffort/hoursEstimated to take one or several hoursEstimated to take one or several hourskind/featureA new featureA new featuretopic/libp2pTopic libp2pTopic libp2p