On 6/22/2018 3:11 PM, Lucas Cotta wrote: > Somebody, any idea?
Look into the fail2ban log (/var/log/fail2ban.log), after the "Start
Fail2ban v0.10.1" or similar, look for the "Creating new jail", and
about 4 lines below "Added logfile:"...
When you delete the persistent database f2b scans the log, that's the
only other place were it can get the info to ban. Deleting the log is
not a correct procedure (neither is deleting the database), those logs
are usually managed by the syslog daemon.
Perhaps you are trying to do things in some "fast way", but the correct
way for unbanning an IP is done with:
fail2ban-client set <JAIL> unbanip <IP>
Even if you have many addressed to unban (you said 90), its easy with
shell functionality, just put them in a list (one per line), and loop
over it, for instance in bash:
echo THE_LIST.txt | while read ip; do
fail2ban-client set dovecot unbanip $ip
done
The list can be made with:
grep "Ban " /var/log/fail2ban.log | cut -sd ' ' -f 16 > THE_LIST.txt
(all is one line)
--
René Berber
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Fail2ban-users mailing list Fail2ban-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fail2ban-users
