Enabling fail2ban 0.10 on ipv6

fail2banipv6

I just upgraded to fail2ban version 0.10 on debian via apt-get.

I see things like this in 'iptables -n -L':

Chain f2b-apache-auth (1 references)
...
Chain f2b-pam-generic (1 references)
...

but I don't see anything similar in the output of 'ip6tables -n -L'.
Is there something specific I need to do to enable fail2ban 0.10 for
iptables/ip6tables?

Best Answer

The answer is that fail2ban doesn't create these chains until it has an entry to put in a chain. Hence why the chains don't exist.

After installing fail2ban 0.10, about a day later, I saw my first ban on ipv6 and it indeed created the chain at that point.

Good to know, just have to be a little patient!

Related Solutions

Fail2Ban – How to Unban an IP Properly

With Fail2Ban before v0.8.8:

fail2ban-client get YOURJAILNAMEHERE actionunban IPADDRESSHERE

With Fail2Ban v0.8.8 and later:

fail2ban-client set YOURJAILNAMEHERE unbanip IPADDRESSHERE

The hard part is finding the right jail:

Use iptables -L -n to find the rule name...
...then use fail2ban-client status | grep "Jail list" | sed -E 's/^[^:]+:[ \t]+//' | sed 's/,//g' to get the actual jail names. The rule name and jail name may not be the same but it should be clear which one is related to which.

Why Fail2ban Isn’t Blocking Failures on Debian Lenny

I had exactly the same problem. Actually, the time was not sync.

dpkg-reconfigure tzdata
cp /usr/share/zoneinfo/Europe/Paris /etc/localtime
vim /etc/rsyslog.conf
#see all messages
$RepeatedMsgReduction off
service rsyslog restart

Best Answer

Related Solutions

Fail2Ban – How to Unban an IP Properly

Why Fail2ban Isn’t Blocking Failures on Debian Lenny

Related Topic