well -- try to do not from sudo (just to eliminate any possible
weirdness)
also --
strace -fF iptables -I INPUT -p tcp -m multiport --dports ssh -j fail2ban-ssh
might give you idea of what actually it couldn't open
also make sure multiport kernel module is loaded
lsmod | grep multiport
On Mon, 10 Mar 2008, Jean-Luc Coulon (f5ibh) wrote:
> Le 10.03.2008 18:25:16, Yaroslav Halchenko a écrit :
> >> [EMAIL PROTECTED] % sudo iptables -I INPUT -p tcp -m multiport --
> >> dports ssh -j fail2ban-ssh
> >> iptables: No chain/target/match by that name
> >so imho this is incorrect... but may be there was a huge change in
> >1.4.0
> >since I am running 1.3.8.0debian1-1... ok -- will check 1.4.0 (but
> >later
> >on)
> I've just tried 1.3.8.Debian-1 and got a different error:
> sudo /etc/init.d/fail2ban stop
> sudo iptables -L -n -v | grep fail2ban
> sudo iptables -N fail2ban-ssh
> sudo iptables -A fail2ban-ssh -j RETURN
> sudo iptables -I INPUT -p tcp -m multiport --dports ssh -j fail2ban-ssh
> getsockopt failed strangely: No such file or directory
> J-L
--
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
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
