Improve the address logging in case of a ConnectPeerFail event#85
Merged
Karmastic merged 4 commits intoalgorand:masterfrom Jun 25, 2019
Merged
Conversation
algobolson
approved these changes
Jun 24, 2019
algorandskiy
pushed a commit
to algorandskiy/go-algorand
that referenced
this pull request
May 15, 2020
Basic unit tests for data/basics/teal.go
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Summary
Existing address specified in the ConnectPeerFail reflect the connection origin, which might not be the originated IP address.
More Details
Our actual per-ip connection limit is using the originating IP address. we should also log this rather then using the connection IP address.