All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin Schiøtz" <malinux@gmail.com>
To: Jason Opperisano <opie@817west.com>, netfilter@lists.netfilter.org
Subject: Re: iptables performance
Date: Thu, 26 May 2005 11:22:40 +0200	[thread overview]
Message-ID: <e208f5d1050526022231390100@mail.gmail.com> (raw)
In-Reply-To: <20050525212523.GA18093@bender.817west.com>

Yes - This looks like the right thing. Thanks :-) 

On 5/25/05, Jason Opperisano <opie@817west.com> wrote:
> On Wed, May 25, 2005 at 07:20:53PM +0000, Martin Schiøtz wrote:
> > Hi
> >
> > I'm planning to set up a bridge running iptables on an uplink of a lot
> > of internet user. The uplink is on maximum at about 30 mbit/s. There
> > are about 1800 * /29 ip nets - some /29 nets needs to be stopped be
> > the bridge and some can pass. I'm wondering about the performance of
> > iptables when having 1800*2 rules worst case (PREROUTING rules on src
> > and dst nets).
> 
> sounds like a job for ipset [1].  if you have 1800 nets that fall into 2
> categories, you'd have 2 rules, 1 for set 1 and 1 for set 2.  depending
> how the nets break down on CIDR boundaries, you could auto-summarize the
> nets that have the same rules to be applied to them.
> 
> -j
> 
> [1] - http://people.netfilter.org/kadlec/ipset/
> 
> --
> "Quagmire: Don't look at me like that. Fat chicks need love too... but
>  they got to pay."
>         --Family Guy
> 
>


  reply	other threads:[~2005-05-26  9:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-25 19:20 iptables performance Martin Schiøtz
2005-05-25 21:25 ` Jason Opperisano
2005-05-26  9:22   ` Martin Schiøtz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-15 19:48 Bart Duchesne
     [not found] <4104105C.4040306@switzer.org>
2004-07-30  8:15 ` IPTables Performance Harald Welte

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=e208f5d1050526022231390100@mail.gmail.com \
    --to=malinux@gmail.com \
    --cc=netfilter@lists.netfilter.org \
    --cc=opie@817west.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 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.