On 03/21/2015 10:11 AM, Yaroslav Halchenko wrote:
On Tue, 10 Mar 2015, AJ Weber wrote:
I'm using v0.8.14. Is there any way to do this or is there a way to
trick fail2ban to do so (I tried touching one of the old log files,
but fail2ban still doesn't seem to re-read that file to ban ips).
I use ipset instead of iptables:
ipset -exist create fail2ban-IpPort hash:ip,port timeout 3600
ipset -exist create fail2ban-Ip hash:ip timeout 86400
and my action has a blank value for
actionunban =
You can pass any timeout value you want from the jail and just let the
operating system
keep
On 03/10/2015 09:14 AM, AJ Weber wrote:
I realize this has come-up a number of times. Seems like a very common
request (common-enough that it probably should be implemented as a
feature?).
Anyway, on restart/reload of fail2ban, I'd like to have it re-scan the
log files back findtime (at
Le 2015-03-10 14:14, AJ Weber a écrit :
I realize this has come-up a number of times. Seems like a very common
request (common-enough that it probably should be implemented as a
feature?).
Anyway, on restart/reload of fail2ban, I'd like to have it re-scan the
log files back findtime (at
