From 72bcb04b4b28fa55f72ffc9c2337c2d7e7175c66 Mon Sep 17 00:00:00 2001 From: Dominik Winter Date: Sat, 4 Jun 2016 13:25:15 +0200 Subject: [PATCH] Updated Configure Fail2ban (markdown) --- Configure-Fail2ban.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Configure-Fail2ban.md b/Configure-Fail2ban.md index 2451f64..3b789d9 100644 --- a/Configure-Fail2ban.md +++ b/Configure-Fail2ban.md @@ -1,6 +1,6 @@ -Fail2ban is installed automatically and bans IP addresses for 3 hours after 3 failed attempts in 10 minutes, see https://github.com/tomav/docker-mailserver/blob/master/target/fail2ban/jail.conf#L58-L66 for these configs. +Fail2ban is installed automatically and bans IP addresses for 3 hours after 3 failed attempts in 10 minutes by default. If you want to change this, you can easily edit [config/fail2ban-jail.cf](https://github.com/tomav/docker-mailserver/blob/master/config/fail2ban-jail.cf). -__Important__: the mail container must be launched with the NET_ADMIN capability in order to be able to install the iptable rules that actually ban IP addresses. Thus either include `--cap-add=NET_ADMIN` in the docker run commandline or the equivalent docker-compose.yml: +__Important__: The mail container must be launched with the NET_ADMIN capability in order to be able to install the iptable rules that actually ban IP addresses. Thus either include `--cap-add=NET_ADMIN` in the docker run commandline or the equivalent docker-compose.yml: ``` cap_add: - NET_ADMIN