User Tools

Site Tools


computing:fail2ban

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
computing:fail2ban [2019/11/03 04:36] oemb1905computing:fail2ban [2019/11/03 05:30] oemb1905
Line 28: Line 28:
   maxretry = 4   maxretry = 4
  
-TheIf over the last 3 weeks the ip address in question was banned at least once, then the stricter ban of 20 weeks takes effect.  If you plan to review 3 weeks of information, with up to three violations each for a week, then you probably need at least 21 days of data.  I rounded to 30 for slightly more granularity. +TheIf over the last 3 weeks the ip address in question was banned at least twice, then the stricter ban of 20 weeks takes effect.  If you plan to review 3 weeks of information, with up to three violations each for a week, then you probably need at least 21 days of data.  I rounded to 30 for slightly more granularity. 
  
   [recidive]   [recidive]
Line 36: Line 36:
   bantime  = 20w   bantime  = 20w
   findtime = 3w   findtime = 3w
-  maxretry = 1+  maxretry = 2
  
 In order for this to work, the database purge parameter needs to be adjusted to be greater than or equal to what you specify for the find time in recidive. In order for this to work, the database purge parameter needs to be adjusted to be greater than or equal to what you specify for the find time in recidive.
computing/fail2ban.txt · Last modified: 2023/12/27 16:08 by oemb1905