Le 10.03.2008 17:29:52, Yaroslav Halchenko a écrit : >tested all those 3 commands on my box and it worked fine... may be >there >is leftover chain left or smth... so do >/etc/init.d/fail2ban stop > >iptables -L -n -v | grep fail2ban ># should be empty! if not -that would be a reason I guess ;-) just >prune ># those manually and start fail2ban
Empty here... > >and if it is then run >iptables -N fail2ban-ssh >iptables -A fail2ban-ssh -j RETURN >iptables -I INPUT -p tcp -m multiport --dports ssh -j fail2ban-ssh [EMAIL PROTECTED] % sudo /etc/init.d/fail2ban stop [EMAIL PROTECTED] % sudo iptables -L -n -v | grep fail2ban [EMAIL PROTECTED] % sudo iptables -N fail2ban-ssh [EMAIL PROTECTED] % sudo iptables -A fail2ban-ssh -j RETURN >and if those fail -- what do they spit out? [EMAIL PROTECTED] % sudo iptables -I INPUT -p tcp -m multiport -- dports ssh -j fail2ban-ssh iptables: No chain/target/match by that name At this point, the rules list is like this: [EMAIL PROTECTED] % sudo iptables -L -n -v | grep fail2ban Chain fail2ban-ssh (0 references) >what version of iptables? [EMAIL PROTECTED] % sudo iptables --version iptables v1.4.0 Regards Jean-Luc
pgpiIisRtreFY.pgp
Description: PGP signature
