From: Franck JONCOURT <franck.mail@dthconnex.com>
To: netfilter@vger.kernel.org
Subject: Re: ipt_recent: how long does a violater stay in the bad guys list?
Date: Mon, 26 May 2008 19:21:21 +0200 [thread overview]
Message-ID: <ff7734792942c4556be2db3610afedd8@localhost> (raw)
In-Reply-To: <alpine.LNX.1.10.0805261437050.19084@fbirervta.pbzchgretzou.qr>
On Mon, 26 May 2008 14:40:02 +0200 (CEST), Jan Engelhardt
<jengelh@medozas.de> wrote:
> On Thursday 2008-05-22 17:16, Akhil Sharma wrote:
>
>>Question: in ipt_recent, if a client is added to a hitlist
>>(/proc/net/ipt_recent/hitlist) after having violated a rule of sending
>>over 10 packets in a minute, how long is the entry maintained in the
>>list? Does it ever get removed from the hitlist? Instead, would it just
>>track the last time the packets arrived and never get removed from the
>>hitlist until the PC is rebooted?
>
> The list keeps a number of timestamps the client last sent a packet (at
> least it seems so); when a new timestamp is added to the head of the
> list, one gets evicted at the tail if the list has already reached
> its maximum length.
> Whether or not a packet subsequently matches the rule depends not on the
> number of timestamp values recorded, but on the parameter you specified
> in your rule (--seconds, etc.).
As a matter of fact, on a local network, you can remove yourself from the
list
by overloading the table with spoof addresses, since by default a table
remember ip_list_tot=100 ip adresses, and then attempt a new connection
with your own ip :p! It works fine.
---
Franck Joncourt
http://www.debian.org/ - http://smhteam.info/wiki/
prev parent reply other threads:[~2008-05-26 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 15:16 ipt_recent: how long does a violater stay in the bad guys list? Akhil Sharma
2008-05-26 12:40 ` Jan Engelhardt
2008-05-26 17:21 ` Franck JONCOURT [this message]
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=ff7734792942c4556be2db3610afedd8@localhost \
--to=franck.mail@dthconnex.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.