Linux Netfilter discussions
 help / color / mirror / Atom feed
From: hewa0000@student.mh.se
To: netfilter@lists.netfilter.org
Subject: Rule matching question [iptables code structure]
Date: Tue, 06 May 2003 14:56:45 +0200	[thread overview]
Message-ID: <df0d10589.10589df0d@student.mh.se> (raw)

[Please mail us personally (oan@itm.mh.se) as well
as mailing the list since we are not members of this
mail-list]

We have a quite difficult question for all you elite
people.... =)
 
When we add a rule to iptables that filter on
MAC-address (or IP address and port for that
matter). Does iptables ONLY check for the
MAC-address option (alas in that case we filter on
MAC-address)?.

Based on a the report "Performance analysis of the
Linux firewall on a host" by James Harris and
Americo J. Melara. It is stated that for each check
if the MAC-address in the rule match the given
MAC-address, the Iptables-algorithm ALWAYS checks
all possibilities (MAC-address, IP, Port, Protocol,
Interface..). 
Does anyone know this to be the truth?

We are currently working on a big project where we
use big lists of rules that are based on MAC and
IP-addresses. And we are trying to understand why
these lists of rules crave so much computation power
to execute.

If Iptables always run a check for every possible
way to match our packet with a single rule
(ip,mac,protocol,interface...) it consumes alot more
(actually we belive it to be around 6 times as much
according to the nature of the algorithm) as necessary. 

Optimally the algorithm would ONLY check for a
MAC-Address match if that is what we are filtering
on. We truly hope this also is the case. But please,
someone who knows this :-) :
Answer us!

Sincerly,
Open Access Networks Project MidSweden University.
oan@itm.mh.se



             reply	other threads:[~2003-05-06 12:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06 12:56 hewa0000 [this message]
2003-05-10 10:54 ` Rule matching question [iptables code structure] Patrick Schaaf
2003-05-12  8:41 ` Harald Welte

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=df0d10589.10589df0d@student.mh.se \
    --to=hewa0000@student.mh.se \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox