Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] u32 and netfilter
Date: Thu, 05 Dec 2002 17:11:21 +0000	[thread overview]
Message-ID: <marc-lartc-103910841430992@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103902852419421@msgid-missing>

On Wednesday 04 December 2002 20:01, James Ma wrote:
> Hi, All,
>
> My understanding is u32 filter is very powerful filter and could do
> anything about IP header filtering, then why do we sometimes use
> netfilering in IPtables? One advantege I guess is in netfilering, there is
> usage counter? Are there other advantges using netfilter (such as delay,
> flexibility)? What is the disadvantages to us Netfilter?
>
> In summary, what are the considerations to select u32 or netfilter as
> classifier for QoS?
I'm not sure, but I think matching a u32 filter is based on a tree-like 
structure.  The fw filter can be faster on the filter part if you use the 
mark as minor number.  But you still have a lot of iptables rules to test.  
And I think you have to test them 1 by 1.
So I think the fw filter will be slower.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      reply	other threads:[~2002-12-05 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-04 19:01 [LARTC] u32 and netfilter James Ma
2002-12-05 17:11 ` Stef Coene [this message]

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=marc-lartc-103910841430992@msgid-missing \
    --to=stef.coene@docum.org \
    --cc=lartc@vger.kernel.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