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.

Sign up for GitHub

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

Jump to bottom

NAT Traversal #209

Closed
3 of 5 tasks
yilunzhang opened this issue Jul 24, 2018 · 1 comment
Closed
3 of 5 tasks

NAT Traversal #209

yilunzhang opened this issue Jul 24, 2018 · 1 comment
Labels
discussion Discussion needed enhancement New feature or request

Comments

@yilunzhang
Copy link
Member

Description of the issue

Currently we require node to have public IP address. It MAY be beneficial to add NAT traversal for nodes so that people behind NAT can start mining. However, this may cause a few troubles:

  1. A node cannot know its public ports before all connections have already been established
  2. Because of 1, a node cannot know its chord ID in advance
  3. Reconnecting to the network may change chord ID as port is changed
  4. May reduce the performance of the network if some NAT traversal are problematic

Issue-Type (put a x sign in the square brackets)

  • bug report
  • feature request
  • Documentation improvement

Checklist

  • Running latest version of code.
  • This issue has not been reported earlier.
@yilunzhang yilunzhang added enhancement New feature or request discussion Discussion needed labels Jul 24, 2018
@yilunzhang
Copy link
Member Author

Implemented in #347

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion Discussion needed enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yilunzhang