I've been a fail2ban user on Ubuntu for several years. I'm finally building a Ubuntu 18.04 machine. I installed the fail2ban package (v0.10.2) from Synaptic and tried using my previous jail.local configuration. But after starting/reloading fail2ban, the jails are not being populated in iptables. In other words, "sudo iptables -n -L" shows no "f2b-." chains.
When I start or reload fail2ban: I see no errors in the fail2ban log. But I do see "Jail sshd is not a JournalFilter instance". I don't know what that's about. I see no errors in the syslog systemctl status shows no errors fail2ban-client status shows no errors, and "-d" appears correct (as far as I can tell). Nevertheless, no chains are not created in iptables when fail2ban is started/reloaded. I removed all .local jail files, which leaves only the sshd jail turned on by jail.d/defaults_debian.conf. Still no joy. I added back in only my own .local sshd config. Still no joy. By no joy, I mean there is no "f2b-sshd" chain in iptables, yet there are no errors reported in the logs and fail2ban-client shows that the sshd jail is active. Is this a known bug? If so, what's the solution? If not, what information is needed to troubleshoot? Thanks, Michael
_______________________________________________ Fail2ban-users mailing list Fail2ban-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fail2ban-users
