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

How can i use kademlia behind a NAT? #100

Closed
ilyesarf opened this issue Jun 26, 2021 · 1 comment
Closed

How can i use kademlia behind a NAT? #100

ilyesarf opened this issue Jun 26, 2021 · 1 comment

Comments

@ilyesarf
Copy link

Hello, (again)
I saw an Issue earlier about how kademlia works behind NAT. And, i didn't find any module for that. That's one.
Two, i think you didn't understand my last issue. I meant, how can i read the IP addresses list. When i run the scripts, i just see the output of the kademlia.crawling but i need to use this output in further scripts.
I'm sorry for all those questions. Thanks in advance!

@bmuller
Copy link
Owner

bmuller commented Jun 26, 2021

@An0nB0y github issues is used exclusively for reporting bugs and issues - if you have any general questions about the library please email the address shown on my github profile page.

I saw an Issue earlier about how kademlia works behind NAT. And, i didn't find any module for that.

Because the lib uses RPC over UDP, it is possible to have a node behind a NAT due to UDP holepunching.

Two, i think you didn't understand my last issue. I meant, how can i read the IP addresses list. When i run the scripts, i just see the output of the kademlia.crawling but i need to use this output in further scripts.

If you need to get the IP's of all of the other nodes that your node knows about, you can iterate over your node's self.protocol.router.buckets which each contain lists of nodes that each contain an ip property.

@bmuller bmuller closed this as completed Jun 26, 2021
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