All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Evans <pevans@catholic.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Lots amounts of classes to solve the DAP problem
Date: Sat, 26 Apr 2003 04:50:59 +0000	[thread overview]
Message-ID: <marc-lartc-105133276320904@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105103510025149@msgid-missing>

Hi Stef,

On April 25, 2003 13:53 pm, Stef Coene wrote:
> You can only solve that problem with the fw filter.  But you can use the fw
> filter in a special way.  If you add 1 fw filter with no options, the mark
> is used to classify the packets.  So if you have a packet with mark 10, it
> will placed in class x:10.  So you only have the 500 iptables rules and
> only 1 filter rule.

You mean instead of a zillion of these:
$tc filter add dev $extif parent 1:0 protocol ip handle $var fw flowid 1:$var

It's just one of:
$tc filter add dev $extif parent 1:0 protocol ip fw 
?

I see it doesn't error, but I haven't tried it on the real thing yet.

Also, could I then add further filters *with* options and would they be 
honored? It'd be very cool if so.

I totally missed that info. Time to revisit ahu's doc I guess; I didn't see it 
on your site.

-- 
Regards, Paul Evans


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

  parent reply	other threads:[~2003-04-26  4:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-22 18:10 [LARTC] Lots amounts of classes to solve the DAP problem GoMi
2003-04-22 18:52 ` Stef Coene
2003-04-22 18:58 ` GoMi
2003-04-22 19:06 ` Stef Coene
2003-04-23 12:45 ` GoMi
2003-04-23 20:28 ` Stef Coene
2003-04-23 21:05 ` GoMi
2003-04-24 14:12 ` GoMi
2003-04-25 20:53 ` Stef Coene
2003-04-26  3:39 ` Rio Martin.
2003-04-26  4:50 ` Paul Evans [this message]
2003-04-26  8:01 ` Stef Coene

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-105133276320904@msgid-missing \
    --to=pevans@catholic.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 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.