From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-2?Q?=A3ukasz_Hejnak?= Subject: Re: SSH Brute force attacks Date: Tue, 17 May 2005 18:06:57 +0200 Message-ID: <428A16A1.9000105@wp.pl> References: <427B93EE.3030905@eccotours.dyndns.org> <427C4EA3.5090501@riverviewtech.net> <4281FC1A.8090000@eccotours.dyndns.org> <42824D1E.7040508@riverviewtech.net> <4285C016.2060900@wp.pl> <42864CA9.7050802@riverviewtech.net> <428856F8.60706@wp.pl> <42897A5E.7010401@wp.pl> <42897EE5.90703@wp.pl> <42898402.10507@eccotours.dyndns.org> <4289E72F.7020901@wp.pl> <4289EF97.2060009@eccotours.dyndns.org> <1116336980.24331.28.camel@debianbox> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1116336980.24331.28.camel@debianbox> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-bounces@lists.netfilter.org Errors-To: netfilter-bounces@lists.netfilter.org Content-Type: text/plain; charset="iso-8859-1"; format="flowed" To: netfilter@lists.netfilter.org Sadus . wrote: > $ipt -A SSH_Brute_Force -m recent ! --rcheck --name SSH --seconds 60=20 >--hitcount 3 -j RETURN > -j RETURN didn't work here. It was blocking all my ssh connections, so i > used ACCEPT and its working now. yes, because most probably by default all packets get dropped at the end of Your INPUT chain, thus If You wan't to perform any other checks of the ssh packet You need a -j RETURN, and a -j ACCEPT later, if not a -j ACCEPT here is ok :) -- With regards =A3ukasz Hejnak