Silence allowipv6 warning #357
Merged
Conversation
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
Contributor
|
I am a bot, here are the test results for this PR: |
aptalca
approved these changes
Mar 29, 2023
Member
Author
|
confirmed warning is gone on amd64 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
resolves #335
I've been closing these issues and ignoring them in discord as they'rea benign warning, but it doesn't seem like it's much effort to resolve.
currently logs will show
2023-03-29 08:48:35,232 fail2ban.configreader [515]: WARNING 'allowipv6' not defined in 'Definition'. Using default one: 'auto'this is because by default the line is commented out in the shipped fail2ban. this just sets it to exactly what it's defaulting to. this should eliminate the warning without any change in functionality.