All of lore.kernel.org
 help / color / mirror / Atom feed
From: Susan Hinrichs <shinrich@thought-mesh.net>
To: casper@meteor.dp.ua
Cc: Martin Millnert <millnert@csbnet.se>,
	Oskar Berggren <oskar.berggren@gmail.com>,
	netfilter@vger.kernel.org
Subject: Re: Select chain from set?
Date: Thu, 07 May 2009 08:44:53 -0500	[thread overview]
Message-ID: <1241703893.2778.297.camel@chichi> (raw)
In-Reply-To: <1241690844.5166.3.camel@casper.meteor.dp.ua>


On Thu, 2009-05-07 at 13:07 +0300, Покотиленко Костик wrote:
> В Чтв, 30/04/2009 в 10:52 -0500, Susan Hinrichs пишет:
> > On Wed, 2009-04-29 at 11:11 +0300, Покотиленко Костик wrote:
> > > В Вто, 28/04/2009 в 10:39 -0500, Susan Hinrichs пишет:
> > > > I also agree that a runtime structure to track traffic attributes and
> > > > match them to targets would be great.  I created my own match-tree table
> > > > generator to achieve a similar effect.  It works, but updating large
> > > > static structures can be rather time consuming and fragile.
> > > 
> > > Can you share details?
> > > 
> > 
> > Sure, I have a tool that takes a list of IP's, MACs, or marks, and
> > builds a prefix-based binary tree of the data.  It generates the tree in
> > linked chains.  It operates in bulk and incremental model.
> 
> What is the purpose of this?

The tree lets you efficiently match a packet and do something unique for
each "client" or "grouping".  So set a mark or set a class ID or update
a unique recent set. As was noted in this thread earlier, ipset lets you
efficiently match a packet basic on an address, but it doesn't let you
do anything unique for each match. 


  reply	other threads:[~2009-05-07 13:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28  9:21 Select chain from set? Oskar Berggren
2009-04-28 12:27 ` Martin Millnert
2009-04-28 13:34   ` Покотиленко Костик
2009-04-28 15:39     ` Susan Hinrichs
2009-04-29  8:11       ` Покотиленко Костик
2009-04-30 15:52         ` Susan Hinrichs
2009-05-07 10:07           ` Покотиленко Костик
2009-05-07 13:44             ` Susan Hinrichs [this message]
2009-05-07 14:01               ` Thomas Jacob
2009-05-07 14:31                 ` Susan Hinrichs
2009-05-07 14:57                   ` Thomas Jacob
2009-05-07 15:48                 ` Покотиленко Костик

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=1241703893.2778.297.camel@chichi \
    --to=shinrich@thought-mesh.net \
    --cc=casper@meteor.dp.ua \
    --cc=millnert@csbnet.se \
    --cc=netfilter@vger.kernel.org \
    --cc=oskar.berggren@gmail.com \
    --cc=shinrich@ieee.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.