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

Fix accounting for NAT nodes in the Clearinghouse #147

Open
aaaaalbert opened this issue Sep 23, 2014 · 0 comments
Open

Fix accounting for NAT nodes in the Clearinghouse #147

aaaaalbert opened this issue Sep 23, 2014 · 0 comments
Assignees

Comments

@aaaaalbert
Copy link
Contributor

The current Clearinghouse includes code to use Affix for working with nodes that are behind NAT gateways or firewalls, but the accounting/vessel selection functions were not updated. At the moment, the clearinghouse code erroneously assumes that NATted nodes have a prefix of "NAT$" to their node names. Since this is not the case with the latest nodemanager, the clearinghouse will assume it controls no NATted nodes.

With the latest nmmain, nodes will not use IP addresses anymore, but opaque hex-strings as identifiers. The clearinghouse will need to look up the identifier and port number on the advertise services and find out what the Affix string to contact the node is (if any). It can only recognize a NATted node then, because such node will use the TCPRelayAffix (or the future TransparentTCPRelayAffix).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants