On a network change, re-create the peer gracefully when it closes #12
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.
Instead of forcibly disconnecting all peers on a network change, mark all peers as needing a restart. This results in no forced disconnects in the case of false positives but will also cause the peer to come back online again once it closes. The downside of this is there will be a bunch of dead peers floating around if IPs change benignly and any of the active peers disconnect eventually, since they'll be re-created.