From: Osama Abu Elsorour <osama@wayout.net>
To: lartc@vger.kernel.org
Subject: [LARTC] cascaded HTB urgent question
Date: Mon, 28 Apr 2003 08:50:46 +0000 [thread overview]
Message-ID: <marc-lartc-105151995702280@msgid-missing> (raw)
Hi there,
I have a question with regards to cascading multiple HTB qdiscs. Assume
that I want to build the following hierarchy:
(qdisc htb 1:0) -> (class htb 1:1) -> (qdisc htb 2:0) -> (class htb 2:1)
-> (class htb 2:2)
I want to attache aggregate u32 filters at 1:0 for supernets, then at
2:0 (and 3:0, 4:0, etc), I attach the more specific u32 filters for say
HTTP and SMPT shaping.
so I attach the following filters:
tc filter add dev eth0 parent 1:0 protocol ip u32 match ip dst
172.16.1.0/24 classid 1:1
so that all the class c traffic is directed to 1:1
then for that c class web traffic
tc filter add dev eth0 parent 2:0 protocol ip u32 match ip sport 80
0xffff classid 2:1
then for that c class smtp traffic
tc filter add dev eth0 parent 2:0 protocol ip u32 match ip sport 25
0xffff classid 2:2
and so on and so forth
however, when I build that setup, the c class traffic gets directed to
1:1 alright, but nothing goes nay further in 2:1 and 2:2
my reasoning could be one of the following:
1) you cannot cascade HTB qdiscs, which to me is illogical, it defies
the concept and adventages of having a hierarchical setup.
2) there is something wrong with the way I attached the filters.
3) I totally misunderstood HTB!
Please advise.
Thanks a million.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-04-28 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 8:50 Osama Abu Elsorour [this message]
2003-04-28 9:33 ` [LARTC] cascaded HTB urgent question Alexey Sheshka
2003-04-28 9:36 ` Rob Cresswell
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-105151995702280@msgid-missing \
--to=osama@wayout.net \
--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.