netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Neal P. Murphy" <neal.p.murphy@alum.wpi.edu>
To: alvin <alvin.sm@Mail.Linux-Consulting.com>
Cc: netfilter@vger.kernel.org
Subject: Re: iptables based appliances - ipset
Date: Mon, 8 Jun 2015 12:02:42 -0400	[thread overview]
Message-ID: <20150608120242.577d3ff1@playground> (raw)
In-Reply-To: <201506081402.t58E2CrZ021258@Mail.Linux-Consulting.com>

On Mon, 8 Jun 2015 07:02:12 -0700 (PDT)
alvin <alvin.sm@Mail.Linux-Consulting.com> wrote:

> 
> hi neal
> 
> > On Sun, 7 Jun 2015 08:04:40 -0700 (PDT)
> ....
> > > even if the src IP# might be spoof'd, you, i still do NOT want
> > > those incoming DDoS attacks coming in at 1,000 or 10,000 packets
> > > per second
> > 
> > Yes, 1000 rules is a little overboard.
> 
> and if there's 10,000 iptables rules, it's galacticly overboard ?
> 
> 	- it was also a test to see if iptables would fail
> 	and it didnt seem to break iptables

A few years ago, I tested iptables and a similar program. I used each
to add 250 000 rules (don't remember if I tried 1M). I found they had
to be added in batches of 15 000 to 20 000. (And it turned out that the
other program took about 5% less time than iptables to complete.)

> ...
> my other iptables todo would be to AutoExpire the DDoS attackers 
> to minimize the list of active ddos attackers  ... manually deleting
> the attackers that went away is for the birds :-)

IIRC, ipset has a way to auto-expire entries; I think it is a set
setting.

N

      reply	other threads:[~2015-06-08 16:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-07 15:04 iptables based appliances alvin
2015-06-07 19:51 ` Neal P. Murphy
2015-06-08 14:02   ` iptables based appliances - ipset alvin
2015-06-08 16:02     ` Neal P. Murphy [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=20150608120242.577d3ff1@playground \
    --to=neal.p.murphy@alum.wpi.edu \
    --cc=alvin.sm@Mail.Linux-Consulting.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).