FS#56715 - [fail2ban] Not working

Attached to Project: Community Packages
Opened by Neil Romig (nromig) - Thursday, 14 December 2017, 10:05 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 15 September 2018, 02:30 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

This used to be OK, but latest version seems not to work. No rules created in iptables, no actions taken, and fail2ban-testcases fails.

Additional info:
* package version(s)
* config and/or log files etc.

fail2ban version 0.10.1-2

all other packages up-to-date at time of submitting

Steps to reproduce:

Start fail2ban. Wait for some login attempt to trigger fail2ban - nothing happens. (I am using courier-smtp and courier-imap filters)
This task depends upon

Closed by  Doug Newgard (Scimmia)
Saturday, 15 September 2018, 02:30 GMT
Reason for closing:  Fixed
Additional comments about closing:  fail2ban 10.3.1-1
Comment by Neil Romig (nromig) - Thursday, 14 December 2017, 11:05 GMT
Update: my last working version was 0.9.7-1
Comment by Luca Weiss (z3ntu) - Wednesday, 10 January 2018, 20:44 GMT
$ iptables -L -n
Chain INPUT (policy ACCEPT)
target prot opt source destination
f2b-postfix-sasl tcp -- 0.0.0.0/0 0.0.0.0/0 multiport dports 25,465,587,220,993,110,995

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Chain f2b-postfix-sasl (1 references)
target prot opt source destination
RETURN all -- 0.0.0.0/0 0.0.0.0/0

works for me with fail2ban 0.10.1-2.
The testcases fail the same though.
Comment by Francois (francoism90) - Wednesday, 20 June 2018, 13:55 GMT
Has this been fixed?
Comment by Zach Callear (Magotchi) - Thursday, 13 September 2018, 15:07 GMT
I've been running 0.10.1-2 or later since 2017-11-27, I'm currently using 0.10.3.1-2, and it's been working the whole time, including properly temp.-banning IPs in iptables.
Comment by Neil Romig (nromig) - Friday, 14 September 2018, 18:25 GMT
Latest versions working for me so will close.

Loading...