From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB --> fw and u32
Date: Wed, 12 Nov 2003 18:04:57 +0000 [thread overview]
Message-ID: <marc-lartc-106866041515527@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106862686807075@msgid-missing>
On Wednesday 12 November 2003 09:26, raptor wrote:
> hi,
>
> I have the following problem I have to classify packets based on
> iptables-mark and on u32 filter... My idea was to set
>
> root-------> classX
>
> |------------------> classY
>
> and then in the root to have a filter that on iptables-mark to direct it to
> classX, and then in classX to setup u32 filters that further classify the
> packets.
>
> Then in the root put the same u32 filters. So that (pseudo code):
> >root
>
> if fwmark = 2 then classid classX
> else
> u32 filter1 ..... flowid classY-child1
> u32 filter2 ..... flowid classY-child2
> u32 filter3 ..... flowid classY-child3
>
> >classX
>
> u32 filter1 ..... flowid classX-child1
> u32 filter2 ..... flowid classX-child2
> u32 filter3 ..... flowid classX-child3
>
> Now what I read in the LARTC docs :
>
> 9.6. Classifying packets with filters
> ................
> You can't filter a packet 'upwards', by the way. Also, with HTB, you should
> attach all filters to the root! ......
You don't have to attach the filters to the root qdisc with htb. So you can
implement your idea.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-11-12 18:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 8:26 [LARTC] HTB --> fw and u32 raptor
2003-11-12 18:04 ` Stef Coene [this message]
2003-11-12 21:56 ` raptor
2003-11-13 15:39 ` Jacek Bilski
2003-11-13 19:04 ` Stef Coene
2003-11-14 15:57 ` Chijioke Kalu
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-106866041515527@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.