[BEP32] Implement IPv6 DHT support #636
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This implements BEP32 by hosting two independent DHT stacks. This can be augmented in future to allow returning IPv4 responses to IPv6 queries, and vice versa.
Features:
portmessage from BEP5 is set to the IPV4 dht port, or IPV6 dht port, depending on which protocol is used to send the message.valuesshould be a list of compact ipv4 peers, or a list of compact ipv6 peers.FindNodesResponseandGetPeersResponseshould (optionally?) supportnodes6FindNodesandGetPeersshould support thewantparameter, a bencoded list ofn4and/orn6. This controls whether to include anodesornodes6response.wantparameter, return nodes matching the request addressfamily.valuesmust only contain peers whose contact information matches the request addressfamily