Search results

Sorry for the confusion. It looks like it is working now. When I changed the jail [recidive-route] to 2 retrys instead of 5 several entries in ip route shoed up. So I was not waiting long enough for 5 to happen in the span of time. This is solved.

Enabled debug incorrectly but when I do the log is justed filled with: 2015-11-03 10:09:37,232 fail2ban.datedetector [4684]: DEBUG Got time 1437193756.000000 for "u'Sat Jul 18 00:29:16 2015'" using template (?:DAY )?MON Day 24hour:Minute:Second(?:\.Microseconds)?(?: Year)? 2015-11-03...

[recidive-route] enabled = true filter = recidive action = route[name=recidive-route] logpath = /var/log/fail2ban.log bantime = 604800 maxretry = 5

Enabling loglevel = DEBUG resulted in this error: I commented it back out after this error showed up in ui of plesk->fail2ban Internal error: f2bmng failed: ERROR:f2bmng:File contains no section headers. file: /etc/fail2ban/fail2ban.conf, line: 9 'loglevel = DEBUG\n' Message f2bmng failed...

Fail2ban route not working : fail2ban 0.9.2, A virgin install of centos 7 - plesk 12.5.30 #8 Fail2ban route working: fail2ban 0.8.3, centos 7 and a centos 6 server both with plesk 12.0.xx (lastest one don't remember the number) I was using fal2ban route.conf to create jails like recidive-route...

Subsequent fail2ban listings ARE showing up in iptables -L. So the off then on seemed to work. Have not tested survival after restart.

Subsequent fail2ban listings are not showing up in iptables at this time. Fail2ban not working properly

Enabling the firewall on plesk after turning on fail2ban seemed to disable it. iptables --list did not show iptables entries for the list in fail2ban. Switched off fail2ban then switch on iptables --list now shows fail2ban entries. Don't know if it will last. I am on a new centos 7-64bit with...