From: Stephen Frost <sfrost@snowman.net>
To: Rowan Reid <rreid@studio3arc.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Count/limit feature
Date: Wed, 2 Apr 2003 22:36:53 -0500 [thread overview]
Message-ID: <20030403033653.GH18434@ns.snowman.net> (raw)
In-Reply-To: <000401c2f95d$6b2a8a60$1001a8c0@s3ac>
[-- Attachment #1: Type: text/plain, Size: 468 bytes --]
* Rowan Reid (rreid@studio3arc.com) wrote:
> I was talking to someone of BSD persuasion and they noted that the ipfw
> feature had a count parameter which can be used to limit icmp attacks.
> Ie more then n number of pings and you begin to ignore the client or
> address range. Is there something similar for netfilter
You can do this with ipt_recent to ignore the address it's coming from.
I'm thinking about adding an ability to do address ranges to it.
Stephen
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-04-03 3:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F27pMHi0SYNIPukg3nO0000612d@hotmail.com>
2003-04-02 12:16 ` migrating ipchains to iptables Arnt Karlsen
2003-04-02 21:18 ` Count/limit feature Rowan Reid
2003-04-03 3:36 ` Stephen Frost [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=20030403033653.GH18434@ns.snowman.net \
--to=sfrost@snowman.net \
--cc=netfilter@lists.netfilter.org \
--cc=rreid@studio3arc.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox