<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Mar 19, 2014 at 10:57 PM, Orion Poplawski <span dir="ltr"><<a href="mailto:orion@cora.nwra.com" target="_blank">orion@cora.nwra.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 03/19/2014 09:10 PM, Richard Shaw wrote:<br>
> Ok using Jonathan's suggestion for the settings from a clean install I'm<br>
> getting an error whether I use the systemd backend or not...<br>
><br>
</div><div class="">>[12698]: ERROR ipset<br>
> create fail2ban-sshd hash:ip timeout 600<br>
> firewall-cmd --direct --add-rule ipv4 filter INPUT 0 -p tcp -m multiport<br>
> --dports ssh -m set --match-set fail2ban-sshd src -j REJECT<br>
> --reject-with icmp-port-unreachable -- stderr: '/bin/sh: ipset: command<br>
> not found\n'<br>
</div> ^^^^^^^^<br>
<br>
Currently we're missing a requires on ipset.</blockquote><div><br></div><div><br></div><div>Ok, is installing ipset sufficient or do I need to enable the service as well?</div><div><br></div><div>Thanks,</div><div>Richard </div>
</div></div></div>