Your message dated Fri, 19 Sep 2008 22:49:02 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#460119: confirmed on sid
has caused the Debian Bug report #460119,
regarding fail2ban doesn't ban
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
460119: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=460119
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: fail2ban
Version: 0.8.1-3~bpo31+1
Severity: normal
fail2ban doesn't ban, it is only "founding" the IPs and does nothing more.
one another machine with the same configurations its working.
....
2008-01-10 20:36:15,503 fail2ban.filter : DEBUG Found 125.177.62.139
2008-01-10 20:36:25,523 fail2ban.filter : DEBUG Found 88.106.179.37
2008-01-10 20:36:35,543 fail2ban.filter : DEBUG Found 89.129.144.209
2008-01-10 20:36:45,564 fail2ban.filter : DEBUG Found 88.227.193.9
2008-01-10 20:36:55,584 fail2ban.filter : DEBUG Found 83.132.234.76
2008-01-10 20:37:05,604 fail2ban.filter : DEBUG Found 83.132.234.76
2008-01-10 20:37:15,624 fail2ban.filter : DEBUG Found 88.227.193.9
2008-01-10 20:37:25,644 fail2ban.filter : DEBUG Found 201.240.28.121
2008-01-10 20:37:35,665 fail2ban.filter : DEBUG Found 201.240.28.121
2008-01-10 20:37:45,685 fail2ban.filter : DEBUG Found 77.64.46.37
2008-01-10 20:37:55,705 fail2ban.filter : DEBUG Found 77.64.46.37
2008-01-10 20:38:05,725 fail2ban.filter : DEBUG Found 77.64.46.37
....
#iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
fail2ban-postfix tcp -- anywhere anywhere multiport
dports smtp
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain fail2ban-postfix (1 references)
target prot opt source destination
RETURN all -- anywhere anywhere
-- System Information:
Debian Release: 3.1
APT prefers oldstable
APT policy: (500, 'oldstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27-1-386
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored:
LC_ALL set to [EMAIL PROTECTED])
--- End Message ---
--- Begin Message ---
sorry to do so but no party revealed their interest in providing more
information to even confirm some specific issue, thus I am closing this
bug
On Tue, 26 Aug 2008, Yaroslav Halchenko wrote:
> well -- in the logs you Lee sent to me I don't see 'Invariant check
> failed', also I don't see anything suspicious -- everything is found and
> banned and unbanned appropriately -- that is why iptables is clean at
> the end since everything was unbanned already.
> The only question is -- your jail.conf sets bantime to be some high
> number, while fail2ban.log says that bantime is taken to be 600 (10 min)
> and those 10min are in effect according to the logs. I modified on my
> box -- and bantime was set appropriately, so I guess either it gets
> overriden in jail.local (which you btw should have used instead of
> direct modification of jail.conf), or this config is newer from when you
> sent fail2ban.log. Any ideas/comments?
--
Yaroslav Halchenko
Research Assistant, Psychology Department, Rutgers-Newark
Student Ph.D. @ CS Dept. NJIT
Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171
101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102
WWW: http://www.linkedin.com/in/yarik
--- End Message ---
