All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Welte <laforge@netfilter.org>
To: Kristen Carlson <kristenc@cs.pdx.edu>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: scripts for adding rulesets for performance testing?
Date: Fri, 10 Oct 2003 22:22:24 +0200	[thread overview]
Message-ID: <20031010202224.GG13456@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <20031009211452.GA16165@sirius.cs.pdx.edu>

[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]

On Thu, Oct 09, 2003 at 02:14:52PM -0700, Kristen Carlson wrote:
> Hi there.  I'm doing some performance testing of iptables with increasing
> rulesets and am wondering if anybody already has some scripts for adding
> rules (many many rules) that they would like to share?  I noticed in the
> archives that the nf-hipac folks had posted a link to a script they had used
> for their performance testing which seemed to do exactly what I wanted, 
> but the link is busted. 

please contact them at the email address given on their homepage.  I am
sure they are very willing to fix that broken link.

> Thanks,
> Kristen


-- 
- Harald Welte <laforge@netfilter.org>             http://www.netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-10-10 20:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-09 21:14 scripts for adding rulesets for performance testing? Kristen Carlson
2003-10-10  7:29 ` Willy Tarreau
2003-10-10 20:22 ` Harald Welte [this message]
2003-11-04 11:46 ` Roberto Nibali

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=20031010202224.GG13456@sunbeam.de.gnumonks.org \
    --to=laforge@netfilter.org \
    --cc=kristenc@cs.pdx.edu \
    --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.