On 9/3/2020 9:16 AM, Phillip Carroll wrote:
Most likely I didn't need the reboot. All I needed to do was use the
console command:
systemctl restart fail2ban.
All of my "manual restarts" of fail2ban server were previously done
using Webmin. Webmin presents a nice interactive page with "Fqa
On 9/3/2020 8:23 AM, Phillip Carroll wrote:
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!
One more discovery:
Most likely I didn't need
* Phillip Carroll [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
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 w
At the bottom of /etc/fail2ban/action.d/iptables-ipset-proto6.conf:
[Init]
# Option: default-timeout
# Notes: specifies default timeout in seconds (handled default ipset timeout
only)
# Values: [ NUM ] Default: 600
default-timeout = 600
ipmset = f2b-
familyopt =
[Init?family=inet6]
ipmse
