From: Andrew Beverley <andy@andybev.com>
To: Azerty Ytreza <007liamg007@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Problem with log which are corrupted and need help with hitcount and FORWARD rules
Date: Sun, 23 Oct 2011 14:51:02 +0100 [thread overview]
Message-ID: <1319377862.26402.6410.camel@andybev-desktop> (raw)
In-Reply-To: <CACMGiwbCxg8a19r-wErFyh-KWDX9tx42GvFo20Pq2zF_Sr9cKg@mail.gmail.com>
On Sat, 2011-10-22 at 18:21 +0200, Azerty Ytreza wrote:
> > Hitcount matches when the number of packets is greater than or *equal*,
> > so defining a number of "1" will always match.
>
> I have try to increase that but it's the same thing.
> iptables -A FORWARD -i eth1 -p tcp -m tcp --dport 443 -m state --state
> NEW -m recent --update --seconds 600 --hitcount 10 -j DROP
>
> >
> > Also, hitcount refers to number of packets, so you'll need a rule in
> > there to only apply the DROP to NEW connections, otherwise you'll block
> > a successful connection as soon as that number of packets has been sent.
>
> Yes, I have modified this rules by removing "NEW" but the port is
> always blocked :(
> iptables -A FORWARD -i eth1 -p tcp -m tcp --dport 443 -m state --state
> RELATED,ESTABLISHED -j ACCEPT
Can you re-post all the rules please so that we can have a look at them?
> > This website is quite good:
> >
> > http://thiemonagel.de/2006/02/preventing-brute-force-attacks-using-iptables-recent-matching/
> >
> > Although you'll have to change INPUT to FORWARD.
> >
>
> This website use blacklist and name but it's the same no in my rules ?
"Probably", although I've not looked closely. If you really have written
equivalent rules then it should work okay. If you can re-post all your
rules then we can check.
Andy
P.S. You forgot to copy the list again!
next prev parent reply other threads:[~2011-10-23 13:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-22 8:43 Problem with log which are corrupted and need help with hitcount and FORWARD rules Azerty Ytreza
2011-10-22 13:20 ` Andrew Beverley
[not found] ` <CACMGiwZ-4Q-xvVQOx3MM79U7YrwafcW+cMxsU932dRKfkM46GQ@mail.gmail.com>
2011-10-22 14:25 ` Andrew Beverley
2011-10-22 15:11 ` Azerty Ytreza
2011-10-22 15:27 ` Andrew Beverley
2011-10-22 15:33 ` Azerty Ytreza
2011-10-22 16:01 ` Andrew Beverley
[not found] ` <CACMGiwbCxg8a19r-wErFyh-KWDX9tx42GvFo20Pq2zF_Sr9cKg@mail.gmail.com>
2011-10-23 13:51 ` Andrew Beverley [this message]
[not found] ` <1319377798.26402.6408.camel@andybev-desktop>
2011-10-23 21:04 ` Azerty Ytreza
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1319377862.26402.6410.camel@andybev-desktop \
--to=andy@andybev.com \
--cc=007liamg007@gmail.com \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.