* Phillip Carroll <domainmana...@enablingsimplicity.com> [09-03-20 11:27]: > On 9/1/2020 4:48 PM, Phillip Carroll wrote: > > when I list the ipset sets on the console, the only sets listed are > > those managed by csf. Clearly I have implemented something incorrectly. > > Problem solved! > > It turns out, I had everything configured correctly. > > All I had to do to resolve the issue was reboot with the fail2ban server > started automatically at boot time. All of my prior testing was with > fail2ban started manually. > > I just applied my computer golden rule: "When all else fails, reboot the > system."
you must come from windows > Immediately after rebooting, listed ipsets and the set I had configured > appeared in the list. systemctl restart fail2ban no need to reboot linux unless dbus or kernel changes. there may be one or two more now, but "used to be" only necessary for changing kernel. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode _______________________________________________ Fail2ban-users mailing list Fail2ban-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fail2ban-users
