Re: [Fail2ban-users] fail2ban with iptables and "invalid port/service"

On 16/07/2021 03:06, Alex wrote: Hi, I'm trying to use fail2ban with iptables because it's what I'm most comfortable using and this is on a real server with an extensive list of rules, not a home desktop. I have the following in my jail.d/00-firewalld.conf: banaction = iptables banaction_allpor

[Fail2ban-users] fail2ban with iptables and "invalid port/service"

Hi, I'm trying to use fail2ban with iptables because it's what I'm most comfortable using and this is on a real server with an extensive list of rules, not a home desktop. I have the following in my jail.d/00-firewalld.conf: banaction = iptables banaction_allports = iptables[type=allports] On re

Re: [Fail2ban-users] "Already banned" makes no sense

On 7/13/21 11:59 AM, Nick Howitt wrote: > Suricata is a Snort alternative. If it is anything like Snort, it can be > configured to be inside or outside the firewall. In ClearOS, it is > outside the firewall but I assume for other distros it is user configurable. > I am not clear what you mean

[Fail2ban-users] Adding to postfix filter

Hi, I'm using fail2ban-0.11 on fedora33 and would like to add the following syslog entry to my postfix file: Jul 15 18:41:26 cipher postfix/submission/smtpd[1935971]: warning: wsip-24-249-23-200.ks.ks.cox.net[24.249.23.200]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 I see several SASL entrie