Rev 34 | Blame | Compare with Previous | Last modification | View Log | RSS feed
# Fail2Ban configuration file## Author: Donald Yandt# Because of the --remove-rules in stop this action requires firewalld-0.3.8+[INCLUDES]before = iptables-common.conf[Definition]actionstart = firewall-cmd --direct --add-chain ipv4 filter f2b-<name>firewall-cmd --direct --add-rule ipv4 filter f2b-<name> 1000 -j RETURNfirewall-cmd --direct --add-rule ipv4 filter <chain> 0 -j f2b-<name>actionstop = firewall-cmd --direct --remove-rule ipv4 filter <chain> 0 -j f2b-<name>firewall-cmd --direct --remove-rules ipv4 filter f2b-<name>firewall-cmd --direct --remove-chain ipv4 filter f2b-<name># Example actioncheck: firewall-cmd --direct --get-chains ipv4 filter | sed -e 's, ,\n,g' | grep -q '^f2b-recidive$'actioncheck = firewall-cmd --direct --get-chains ipv4 filter | sed -e 's, ,\n,g' | grep -q '^f2b-<name>$'actionban = firewall-cmd --direct --add-rule ipv4 filter f2b-<name> 0 -s <ip> -j <blocktype>actionunban = firewall-cmd --direct --remove-rule ipv4 filter f2b-<name> 0 -s <ip> -j <blocktype>[Init]# Default name of the chain#name = defaultchain = INPUT_direct# DEV NOTES:## Author: Donald Yandt# Uses "FirewallD" instead of the "iptables daemon".### Output:# actionstart:# $ firewall-cmd --direct --add-chain ipv4 filter f2b-recidive# success# $ firewall-cmd --direct --add-rule ipv4 filter f2b-recidive 1000 -j RETURN# success# $ sudo firewall-cmd --direct --add-rule ipv4 filter INPUT_direct 0 -j f2b-recidive# success