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

Whether IPNI indexer-provider supports NAT Hole punching? #444

Open
wenyue opened this issue Jun 3, 2024 · 2 comments
Open

Whether IPNI indexer-provider supports NAT Hole punching? #444

wenyue opened this issue Jun 3, 2024 · 2 comments

Comments

@wenyue
Copy link

wenyue commented Jun 3, 2024

I noticed that there are such description in the documentation:

index-provider must be publicly reachable. IPNI will try to establish connection into it to fetch Advertisement chains. If that can't be done CIDs will not appear in IPNI. Ensure that your firewall is configured to allow incoming connections on the ProviderServer port specified in the index-provider configuration. Ensure that the index-provider is configured to advertise routable addresses in its announcements (where indexers get advertisements) and in its advertisements (where retrieval clients get content).

Does this mean the provider must have a public IP? What if I use libp2p pubsub instead of HTTP?

@willscott
Copy link
Member

Yes. the provider does need a public IP.
It is meant for larger, stable providers - if you do not have a public / stable IP, the DHT is likely a better choice.

IPNI reduces the overhead of re-publishing content daily to show "your still there" with the expectation that indexers can poll the provider at a regular interval to confirm it's still there.

@wenyue
Copy link
Author

wenyue commented Jun 3, 2024

ok, thanks for your reply.

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