All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Lots amounts of classes to solve the DAP problem
Date: Sat, 26 Apr 2003 08:01:01 +0000	[thread overview]
Message-ID: <marc-lartc-105134415425692@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105103510025149@msgid-missing>

On Saturday 26 April 2003 06:50, Paul Evans wrote:
> 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.
It works.  If you add that filter, packets with mark 11 will end in class 
1:11.  Actually you use a bery fast hash key so you don't need to check all 
the filters.
But be aware.  Mark and classid is in hex.  So somtimes 10 is translated in to 
A.  So it's better to specify 0x10 for the mark so you are sure it's in hex.

> Also, could I then add further filters *with* options and would they be
> honored? It'd be very cool if so.
Yes.  You can iuse the fw filter to put the packets in a class.  And you can 
add extra filters to that class to classify the packets in sub classes :
1:0
  1:1
    1:10
    1:11

$tc filter add dev $extif parent 1:0 protocol ip handle $var fw 
$tc filter add dev $extif parent 1:10 blabla flowid 1:10
$tc filter add dev $extif parent 1:11 blabla flowid 1:11


> I totally missed that info. Time to revisit ahu's doc I guess; I didn't see
> it on your site.
I know it can be done, but I never checked it my self.  So if it works, let me 
know :)  And if it works, I create an extra fas and update the howto.

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/

      parent reply	other threads:[~2003-04-26  8:01 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
2003-04-26  8:01 ` 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-105134415425692@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 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.