• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Question Fail2Ban recidive: how it work ?

OverWolf

Regular Pleskian
Hi,

I'm on CentOS 7.3 with Plesk 17.5.3 and I'm configuring fail2ban (0.9.6) recidive to ban for 24 hours an ip. But if you look at the print-screen seems that it doesn't work as I expect.
When an IP is found for a specific jail it's banned for the period that I have configured for that event (my postfix example is banned for 2 hours) even if that IP is found as recidive.
So, what's wrong ? Am I missing something ?

Thank you
 

Attachments

  • Fail2Ban.png
    Fail2Ban.png
    40.4 KB · Views: 72
Hi,
i've done other tests, and probably I found the error; I've changed the interval for detection of subsequent attacks and now seems that recidive works as expected.
So, I would like to know if I understand how it works: after the max numbers of failed login attempts (ssh, ftp, postfix, etc.), the ip is ban as recidive. If it so, why the default interval of detection is so sort ?
 
The recidive jail analyzes the fail2ban.log file. It does not directly analyze the postfix (maillog) log. Recidive counts the number of bans in the fail2ban.log.
 
You can define the duration of bans using the "bantime" directive in the according recidive section of /etc/fail2ban/jail.local. You can also exclude your own IP from tests by adding it to the "ignoreip" directive.
 
Back
Top