diff --git a/config/action.d/firewall-cmd-direct-new.conf b/config/action.d/firewall-cmd-direct-new.conf
index c151ba48..55681887 100644
--- a/config/action.d/firewall-cmd-direct-new.conf
+++ b/config/action.d/firewall-cmd-direct-new.conf
@@ -5,6 +5,10 @@
 #  It uses "firewall-cmd" instead of "iptables".
 #  firewall-cmd is based on the command of version firewalld-0.3.4-1.fc19.
 
+[INCLUDES]
+
+before = iptables-blocktype.conf
+
 [Definition]
 
 actionstart = firewall-cmd --direct --add-chain ipv4 filter fail2ban-<name>
@@ -16,6 +20,7 @@ actionstart = firewall-cmd --direct --add-chain ipv4 filter 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 )
@@ -23,9 +28,9 @@ actionstop = firewall-cmd --direct --remove-rule ipv4 filter <chain> 0 -m state
 
 actioncheck = firewall-cmd --direct --get-chains ipv4 filter | grep -q 'fail2ban-<name>[ \t]'
 
-actionban = firewall-cmd --direct --add-rule ipv4 filter fail2ban-<name> 0 -s <ip> -j DROP
+actionban = firewall-cmd --direct --add-rule ipv4 filter fail2ban-<name> 0 -s <ip> -j <blocktype>
 
-actionunban = firewall-cmd --direct --remove-rule ipv4 filter fail2ban-<name> 0 -s <ip> -j DROP
+actionunban = firewall-cmd --direct --remove-rule ipv4 filter fail2ban-<name> 0 -s <ip> -j <blocktype>
 
 [Init]