harmonize logs when dropping connections for abuse or protocol violation #7081
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.
Those will be a warning level log in the net.failconn category, including
the offending IP, and the "dropping connection" string. This should make
it easier to use fail2ban with monero.
Note that connections dropped for more innocuous reasons (such as already
having the maximum number of incoming connections) do not generate such
a log line (they will typically include "dropping connections", but will
not be in the net.connfail category.