This repository was archived by the owner on Jul 21, 2023. It is now read-only.
fix: do not pollute routing table with useless peers #254
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If a remote peer doesn't have private addresses, do not add it to the routing table for the lan DHT, if they don't have public addresses, do not add them to the routing table for the wan DHT. Also adds more logging.
achingbrain
deleted the
fix/do-not-pollute-routing-table-with-useless-peers
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
If a remote peer doesn't have private addresses, do not add it to the
routing table for the lan DHT, if they don't have public addresses,
do not add them to the routing table for the wan DHT.
Also adds more logging.