From owner-freebsd-ports-bugs@freebsd.org Fri Jun 26 12:12:26 2015 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5E3B398DC23 for ; Fri, 26 Jun 2015 12:12:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 40FBC19AE for ; Fri, 26 Jun 2015 12:12:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t5QCCQmq040374 for ; Fri, 26 Jun 2015 12:12:26 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 201108] security/py-fail2ban: ssh log entries are ignored Date: Fri, 26 Jun 2015 12:12:25 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jason.unovitch@gmail.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jun 2015 12:12:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201108 --- Comment #4 from Jason Unovitch --- (In reply to oz42 from comment #3) Ok, so it looked like you had adapted your configuration as you went since you started with IPTables. Starting from the bottom the issue seems to be ipfw(8) configuration related since that is returning an error when it gets a valid IP address from Fail2Ban. 2015-06-25 18:04:09,540 fail2ban.action [605]: ERROR ipfw table 1 delete 5.190.61.182 -- stdout: '' 2015-06-25 18:04:09,540 fail2ban.action [605]: ERROR ipfw table 1 delete 5.190.61.182 -- stderr: 'ipfw: setsockopt(IP_FW_TABLE_XDEL): No such process\n' 2015-06-25 18:04:09,541 fail2ban.action [605]: ERROR ipfw table 1 delete 5.190.61.182 -- returned 71 If you post the link to your forum thread we can carry on the discussion there. I didn't seem to see it. -- You are receiving this mail because: You are the assignee for the bug.