All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Adem" <for-gmane@alicewho.com>
To: netfilter@vger.kernel.org
Subject: Re: banning bot ips with ipset
Date: Tue, 25 Nov 2008 23:54:08 +0100	[thread overview]
Message-ID: <gghvpm$1cc$1@ger.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.58.0811252145030.31197@mail3.jubileegroup.co.uk

"G.W. Haywood" wrote:
> On Tue, 25 Nov 2008, Nigel Heron wrote:
> 
> > We're being attacked by a botnet ... started dropping them in
> > iptables, once we got to ~1700 banned ips the server stopped nat'ing
> > completely (not sure why..)
> 
> It probably just ran out of steam.  The performance of iptables with
> thousands of rules can be poor if you don't structure them carefully.
> 
> > Is ipset stable enough to be deployed on live environments?
> 
> I've been using it for years with absolutely zero problems.
> 
> > iphash seems like the best set type for us, how many
> > ips can the set handle before there's a noticeable slowdown?
> 
> I currently have about 50,000 ipset (iphash) rules on modest hardware,
> with no noticeable performance impact.  There's a good report here:
> http://people.netfilter.org/kadlec/nftest.pdf

Do you understand what the authors means with this statement in section 4.2:

  "As the graph displays, the system handled almost 
   3,500,000 concurrent connections at the peak."

I wonder how this is possible... :-)
I think one would need a machine with 54 NIC's (real and/or virtual) attached to it, isn't it? :-)



  reply	other threads:[~2008-11-25 22:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25 21:00 banning bot ips with ipset Nigel Heron
2008-11-25 22:25 ` G.W. Haywood
2008-11-25 22:54   ` Adem [this message]
2008-11-26  8:16     ` Jozsef Kadlecsik
2008-11-26  7:45 ` Marek Kierdelewicz
2008-11-26  8:25 ` Jozsef Kadlecsik
2008-11-26 16:28   ` Nigel Heron

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='gghvpm$1cc$1@ger.gmane.org' \
    --to=for-gmane@alicewho.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.