diff --git a/config/action.d/iptables-xt_recent-echo.conf b/config/action.d/iptables-xt_recent-echo.conf new file mode 100644 index 00000000..f3ac80b5 --- /dev/null +++ b/config/action.d/iptables-xt_recent-echo.conf @@ -0,0 +1,76 @@ +# Fail2Ban configuration file +# +# Author: Zbigniew Jędrzejewski-Szmek +# +# $Revision: 1 $ +# + +[Definition] + +# Option: actionstart +# Notes.: command executed once at the start of Fail2Ban. +# Values: CMD +# +# Changing iptables rules requires root priviledges. If fail2ban is +# configured to run as root, firewall setup can be performed by +# fail2ban automatically. However, if fail2ban is configured to run as +# a normal user, the configuration must be done by some other means +# (e.g. using static firewall configuration with the +# iptables-persistent package). +# +# Explanation of the rule below: +# Check if any packets coming from an IP on the fail2ban- +# list have been seen in the last 3600 seconds. If yes, update the +# timestamp for this IP and drop the packet. If not, let the packet +# through. +# +# Fail2ban inserts blacklisted hosts into the fail2ban- list +# and removes them from the list after some time, according to its +# own rules. The 3600 second timeout is independent and acts as a +# safeguard in case the fail2ban process dies unexpectedly. The +# shorter of the two timeouts actually matters. +actionstart = iptables -I INPUT -m recent --update --seconds 3600 --name fail2ban- -j DROP + +# Option: actionstop +# Notes.: command executed once at the end of Fail2Ban +# Values: CMD +# +actionstop = echo / > /proc/net/xt_recent/fail2ban- + +# Option: actioncheck +# Notes.: command executed once before each actionban command +# Values: CMD +# +actioncheck = test -e /proc/net/xt_recent/fail2ban- + +# Option: actionban +# Notes.: command executed when banning an IP. Take care that the +# command is executed with Fail2Ban user rights. +# Tags: IP address +# number of failures +#