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

Find out why implicit NAT traversal is not working for DHT #27

Open
F483 opened this issue Nov 28, 2015 · 1 comment
Open

Find out why implicit NAT traversal is not working for DHT #27

F483 opened this issue Nov 28, 2015 · 1 comment
Assignees
Labels

Comments

@F483
Copy link
Contributor

F483 commented Nov 28, 2015

As can be observed in the attached network map, nodes without a public IP (blue) never link to other nodes without a public IP.

Given that nodes update there routing table every 2 min, they should implicitly UDP punch each other over time. For some reason this is not happening.

network map 2015-11-28 17 17 14 389707

@F483 F483 added the bug label Nov 28, 2015
@F483 F483 self-assigned this Nov 28, 2015
@F483
Copy link
Contributor Author

F483 commented Dec 1, 2015

It may be that nodes behind a NAT have actually linked to other nodes behind a NAT, its just that we cant observe this because nodes are contacted directly. Thus we see the links from nodes with a public ip to nodes behind a NAT because we can contact the public node.

It will be more clear once relay messages are use to get node information.

@super3 super3 changed the title Find out why implicit NAT traversal is not working for DHT. Find out why implicit NAT traversal is not working for DHT Dec 16, 2015
@super3 super3 modified the milestone: Test Group B Dec 16, 2015
@ELQET ELQET added ready and removed ready labels Jan 15, 2016
@super3 super3 removed this from the Test Group B milestone Jan 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants