From: "Leandro Stasi" <leanstasi@yahoo.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Flow direction?
Date: Fri, 24 Mar 2000 23:36:05 +0000 [thread overview]
Message-ID: <marc-lartc-101701282432026@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
I don't understand how the flow goes in the traffic control.
Please helpme to understand, this is what I know.
I made this example:
tc qdisc add dev eth0 root handle 10: cbq bandwidth 10mbit avpkt 1000
tc class add dev eth0 parent 10: classid 10:1 cbq bandwidth 10mbit rate
25kbit allot 1514 maxburst 20 avpkt 1000 bounded prio 3
tc filter add dev eth0 parent 10: protocol ip prio 3 handle 1 fw classid
10:1
ipchains -A output -d 192.168.1.4/32 -m 1
and from what I can see here, the traffic flows like this:
first from the firewall that mark the pakets (ipchains),
then to the filter that split traffic into clasess,
then to the cqb queue decipline,
and then out,
From what I understand the clasess have the rate limit, and the qdisc are
how the rate limit is acomplish.
I've attach an image from Werner Almesberger paper, and I mark what I don´t
understand.
Why there is a root qdisc?Why do I need it for?
What is the relationship with the inner qdisc?
Can I chose any qdisc for the inner qdisc?
[-- Attachment #2: queue.jpg --]
[-- Type: image/jpeg, Size: 20071 bytes --]
reply other threads:[~2000-03-24 23:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-101701282432026@msgid-missing \
--to=leanstasi@yahoo.com \
--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.