All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: nth, random and fuzzy match
Date: Thu, 06 Apr 2006 19:53:30 +0200	[thread overview]
Message-ID: <4435559A.60904@trash.net> (raw)

Also following the decisions from the netfilter workshop,
I've started merging nth and random into a new "statistic"
match. I won't merge fuzzy since it seems to obscure and
complex and I don't see what it offers beyond nth + random.

The current nth match optionally uses shared state for the
counters (which as we know isn't pretty with the current
iptables userspace interface) and has a compile-time limit
on the number of shared counters. I don't see the need for
this shared state, I think everything expressable today
should also be expressable using just per-match state.

So my questions to the nth users: is anyone using the nth
match in a way that can't be done by just matching on every
nth packet with an optional starting point?

             reply	other threads:[~2006-04-06 17:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-06 17:53 Patrick McHardy [this message]
2006-04-12  8:47 ` nth, random and fuzzy match Harald Welte
2006-04-12 18:57   ` 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=4435559A.60904@trash.net \
    --to=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.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.