Your message dated Mon, 10 Mar 2008 15:46:41 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#470305: fail2ban: Return an error 100 at start
has caused the Debian Bug report #470305,
regarding fail2ban: Return an error 100 at start
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.)
--
470305: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=470305
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: fail2ban
Version: 0.8.2-1
Severity: normal
Hi,
Versions earlier then 0.7.5-2 return and error ant start:
<snip>
2008-03-10 14:07:13,559 fail2ban.actions.action: INFO Set actionBan =
iptables -I fail2ban-<name> 1 -s <ip> -j DROP
2008-03-10 14:07:13,560 fail2ban.actions.action: INFO Set actionStop =
iptables -D INPUT -p <protocol> -m multiport --dports <port> -j fail2ban-<name>
iptables -F fail2ban-<name>
iptables -X fail2ban-<name>
2008-03-10 14:07:13,562 fail2ban.actions.action: INFO Set actionStart =
iptables -N fail2ban-<name>
iptables -A fail2ban-<name> -j RETURN
iptables -I INPUT -p <protocol> -m multiport --dports <port> -j fail2ban-<name>
2008-03-10 14:07:13,563 fail2ban.actions.action: INFO Set actionUnban =
iptables -D fail2ban-<name> -s <ip> -j DROP
2008-03-10 14:07:13,564 fail2ban.actions.action: INFO Set actionCheck =
iptables -n -L INPUT | grep -q fail2ban-<name>
2008-03-10 14:07:13,741 fail2ban.actions.action: ERROR iptables -N fail2ban-ssh
iptables -A fail2ban-ssh -j RETURN
iptables -I INPUT -p tcp -m multiport --dports ssh -j fail2ban-ssh returned 100
<snip/>
Regards
Jean-Luc
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.25-rc5-k8-1 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages fail2ban depends on:
ii lsb-base 3.2-4 Linux Standard Base 3.2 init scrip
ii python 2.4.4-6 An interactive high-level object-o
ii python-central 0.5.15-0.1 register and build utility for Pyt
Versions of packages fail2ban recommends:
ii iptables 1.4.0-3 administration tools for packet fi
-- no debconf information
--- End Message ---
--- Begin Message ---
oki doki -- that closes the bug ;-)
> My kernel was not compiled with multiport.
> zgrep -i multiport /proc/config.gz
> # CONFIG_NETFILTER_XT_MATCH_MULTIPORT is not set
> It is repaired now. Thank you for your patience.
--
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 ---
