You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
On some systems 'iptables' gives an error. This implements the solution from https://github.com/crazy-max/docker-fail2ban ie. install iptables-legacy, and if iptables gives an error symlink iptables -> iptables-legacy.
This allows fail2ban to work. I was hitting this problem and this resolved it for me.
Benefits of this PR and context:
Fixes broken fail2ban on some systems.
How Has This Been Tested?
I ran with this fix with a Qnap host. I can docker exec -it swag /bin/sh and see banned ips with 'iptable -L -n' now - previously it would just give an error.
tested by me on a system not needing the fallback to legacy. it stayed on iptabled 1.8.10 nf_tables rather than legacy. no impact to functionality that I was able to see.
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.
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Description:
Closes #476
On some systems 'iptables' gives an error. This implements the solution from https://github.com/crazy-max/docker-fail2ban ie. install iptables-legacy, and if iptables gives an error symlink iptables -> iptables-legacy.
This allows fail2ban to work. I was hitting this problem and this resolved it for me.
Benefits of this PR and context:
Fixes broken fail2ban on some systems.
How Has This Been Tested?
I ran with this fix with a Qnap host. I can docker exec -it swag /bin/sh and see banned ips with 'iptable -L -n' now - previously it would just give an error.
Source / References:
See issue #476 and the crazy-max fail2ban image.