We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
One question please: Why is it adviced to use a second container when banning with iptables the chain DOCKER-USER and INPUT at the same time as shown here: https://github.com/crazy-max/docker-fail2ban/blob/master/examples/compose-multi/docker-compose.yml
DOCKER-USER
INPUT
Wouldn't it be enough to use just one container and extend the used action to just add the second chain to iptables?
Something like this:
actionstart = <iptables> -N f2b-<name> <iptables> -A f2b-<name> -j <returntype> <iptables> -I INPUT -p <protocol> -j f2b-<name> <iptables> -I DOCKER-USER -p <protocol> -j f2b-<name>
The text was updated successfully, but these errors were encountered:
@verybadsoldier This would make the iptables rules more cumbersome but it could work. I'll think about this implementation.
Sorry, something went wrong.
Bringing the INPUT and DOCKER-USER chains together (#17 #46)
54f8a88
@verybadsoldier F2B_IPTABLES_CHAIN env var has been removed and README updated to use chain = <name> def. See also #46.
F2B_IPTABLES_CHAIN
chain = <name>
No branches or pull requests
One question please:
Why is it adviced to use a second container when banning with iptables the chain
DOCKER-USER
andINPUT
at the same time as shown here:https://github.com/crazy-max/docker-fail2ban/blob/master/examples/compose-multi/docker-compose.yml
Wouldn't it be enough to use just one container and extend the used action to just add the second chain to iptables?
Something like this:
The text was updated successfully, but these errors were encountered: