Linux Netfilter development
 help / color / mirror / Atom feed
From: Thomas Jacob <jacob@internet24.de>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Plans for future iptables versions / jumpset feature
Date: Thu, 22 May 2008 22:27:16 +0200	[thread overview]
Message-ID: <20080522202715.GA28875@internet24.de> (raw)
In-Reply-To: <alpine.LNX.1.10.0805222140160.9332@fbirervta.pbzchgretzou.qr>

> There have been a few changes regarding insertion speed. Even if one
> has 500 rules (see that URL), they can probably be optimized using
> IPMARK or chaintrees. 

I was thinking more along the lines of >100k rules. Iptables
can easily handles those numbers at the moment, it's just a bit
awkward to deal with.

By chaintrees I presume you mean trees of iptables chains and not
some sort of tool named this way?

> Also, one should use iptables-restore for
> updates, at least when changing more than one rule in a go. Lots of
> people fail to actually use it.

To be sure, but I am also interested in improving the time required
to find to correct chain given 1000s or 10000s of ip to chain mappings
and of course the usability of a construct like that.


  parent reply	other threads:[~2008-05-22 20:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-22 19:00 Plans for future iptables versions / jumpset feature Thomas Jacob
2008-05-22 19:18 ` Patrick McHardy
2008-05-22 19:57   ` Jan Engelhardt
2008-05-22 20:15     ` Patrick McHardy
2008-05-22 20:27     ` Thomas Jacob [this message]
2008-05-22 20:14   ` Thomas Jacob
2008-05-22 20:18     ` Patrick McHardy
2008-05-22 20:47       ` Thomas Jacob
2008-05-22 20:51         ` Patrick McHardy
2008-05-22 21:43           ` Thomas Jacob
2008-05-23 11:55   ` Nishit Shah
2008-05-23 12:15     ` Patrick McHardy
2008-05-23 12:47       ` Thomas Jacob
2008-05-23 13:28         ` Patrick McHardy

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=20080522202715.GA28875@internet24.de \
    --to=jacob@internet24.de \
    --cc=jengelh@medozas.de \
    --cc=netfilter-devel@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