From: Maximilian Wilhelm <max@rfc2324.org>
To: netfilter@lists.netfilter.org
Subject: Whats faster? multiple rules vs. multiport match
Date: Thu, 15 Feb 2007 22:37:29 +0100 [thread overview]
Message-ID: <20070215213729.GA27689@outback.rfc2324.org> (raw)
Hi!
While hacking on alff [42] I asked myself what would be more wise to
use for matching multiple ports on multiple servers/ips
a) on rule for every ip/port combination
b) two rules for every server, one for tcp and one for udp
(assumend I only have to match for udp and tcp stuff).
(The whole scenario is the following:
I generate rules to regulate access to different services.
Every service is transalted into an own chain.
Therein I generate a matrix of host running this service and port
related to it - like a))
As there are some services with ~ 20 ports (think: Windows(r) DC)
there might be some advantage in choosing the faster way.
Is there any "benchmark" which might enligthen me which way to use?
Any comments?
Thanks in advance
Ciao
Max
--
Follow the white penguin.
next reply other threads:[~2007-02-15 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 21:37 Maximilian Wilhelm [this message]
2007-02-17 13:55 ` Whats faster? multiple rules vs. multiport match Jan Engelhardt
2007-02-17 14:24 ` Pascal Hambourg
2007-02-17 15:33 ` Jan Engelhardt
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=20070215213729.GA27689@outback.rfc2324.org \
--to=max@rfc2324.org \
--cc=netfilter@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.