I have configured fail2ban to run on my central log server rather than
on individual servers. fail2ban updates an ACL in my network
firewall[1] to impose a blanket ban instead of a per-server or
per-service ban. Updating the firewall ACL is moderately expensive, so
I'd rather not do it more than absolutely necessary. The firewall ACLs
are persistent across reboots of the firewall; the firewall is competely
unaffected by the central log server rebooting (or fail2ban
restarting). Given my setup, fail2ban need not, and because of the
expense should not, re-ban everything on fail2ban restarting. Is there
some way to prevent fail2ban from re-banning IPs on startup?
Thanks,
MJB
[1] I modified the scripts at
https://www.crypt.gen.nz/2017/09/20/ciscoios-acl-a-fail2ban-module-for-managing-cisco-ios-acls/
to handle my firewall.
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/fail2ban-users
