diff --git a/config/action.d/firewall-cmd-direct-new.conf b/config/action.d/firewall-cmd-direct-new.conf
index ac06aa57..0f7388a2 100644
--- a/config/action.d/firewall-cmd-direct-new.conf
+++ b/config/action.d/firewall-cmd-direct-new.conf
@@ -15,15 +15,8 @@ actionstart = firewall-cmd --direct --add-chain ipv4 filter fail2ban-<name>
               firewall-cmd --direct --add-rule ipv4 filter fail2ban-<name> 1000 -j RETURN
               firewall-cmd --direct --add-rule ipv4 filter <chain> 0 -m state --state NEW -p <protocol> --dport <port> -j fail2ban-<name>
 
-# The following rule does not work, because firewalld keeps its own database of firewall rules.
-# firewall-cmd --direct --passthrough ipv4 -F fail2ban-<name>
-# The better rule would be the following, but firewall-cmd has not implemented this command with firewalld-0.3.3-2.fc19 .
-# firewall-cmd --direct --flush-chain ipv4 filter fail2ban-<name>
-# The following is a workaround using a loop to implement the --flush-chain command.
-# https://fedorahosted.org/firewalld/ticket/10
-
 actionstop = firewall-cmd --direct --remove-rule ipv4 filter <chain> 0 -m state --state NEW -p <protocol> --dport <port> -j fail2ban-<name>
-             ( IFS='|' ; for r in $( firewall-cmd --direct --get-rules ipv4 filter fail2ban-<name> | tr '\n' '|' ) ; do eval firewall-cmd --direct --remove-rule ipv4 filter fail2ban-<name> $r ; done )
+             firewall-cmd --direct --remove-rules ipv4 filter fail2ban-<name>
              firewall-cmd --direct --remove-chain ipv4 filter fail2ban-<name>
 
 actioncheck = firewall-cmd --direct --get-chains ipv4 filter | grep -q 'fail2ban-<name>[ \t]'