* Yan Seiner ([EMAIL PROTECTED]) wrote:
> Stephen:
> 
> Thanks.  That indeed looks like what I need, but I am stuck trying to
> make it work.
> 
> This is what I'm using:
> 
> $IPTABLES -v -A INPUT -p tcp --source $OUTSIDE -m recent --hitcount 10
> --update --seconds 60 -j LOGDROP
> 
> But here's what I get:
> LOGDROP  tcp opt -- in * out * !192.168.0.0/16  -> 0.0.0.0/0  recent:
> UPDATE seconds: 60hit_count: 10
> iptables: No chain/target/match by that name
> 
> LOGDROP is my log & drop chain - here's a rule from just prior to the -m
> recent one:
> 
> # limit connections from outside to 4 per C block
> $IPTABLES -A INPUT -p tcp --source $OUTSIDE --syn -m iplimit
> --iplimit-mask 24 --iplimit-above 4 -j LOGDROP
> 
> and that works fine.  Is it possible that the recent module only works
> for FORWARD chain?  I hope not; I run some services on my firewall box
> that I want to protect....
> 
> Oh yeah, I'm running kernel 2.4.17 and 1.2.5 iptables.

Nope, doesn't matter what chain it's on.  I'm using it to protect my
firewall right now actually.  You'll need to use patch-o-matic to
compile the ipt_recent module for your kernel and I'd strongly suggest
you use the CVS version of ipt_recent, it's got some fixes.

If you continue to have problems let me know, I don't have time right
now to go into more detail but I can look at it more later.

        Thanks,

                Stephen

Attachment: msg00581/pgp00000.pgp
Description: PGP signature

Reply via email to