Hi, > I'm not an iptables expert but it seems that fail2ban add a "-w" parameter > that in some ways is not correct. > By the way just before the update all worked perfectly. > > Thanks in advice to anyone could help me
If you have a /etc/fail2ban/action.d/iptables-common.conf, check if there are some lines like --- # Option: lockingopt # Notes.: Option was introduced to iptables to prevent multiple instances from # running concurrently and causing irratic behavior. -w was introduced # in iptables 1.4.20, so might be absent on older systems # See https://github.com/fail2ban/fail2ban/issues/1122 # Values: STRING lockingopt = -w ---- in it. Change lockingopt = -w to lockingopt = if you haven't iptables 1.4.20 installed, restart fail2ban and you should be good. Iosif Fettich ------------------------------------------------------------------------------ _______________________________________________ Fail2ban-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fail2ban-users
