You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
A node cannot know its public ports before all connections have already been established
Because of 1, a node cannot know its chord ID in advance
Reconnecting to the network may change chord ID as port is changed
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.
The text was updated successfully, but these errors were encountered:
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:
Issue-Type (put a
x
sign in the square brackets)Checklist
The text was updated successfully, but these errors were encountered: