From: Homer Parker <hparker@homershut.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multiple classes
Date: Wed, 04 Dec 2002 10:08:39 +0000 [thread overview]
Message-ID: <marc-lartc-103899701016552@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103889506715109@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 2065 bytes --]
On Tue, 3 Dec 2002 22:03:39 +0100 Stef Coene <stef.coene@docum.org>
wrote....
> It all depends on what you want to do. Have you read my docs on
> www.docum.org ?? But you are on the right track.
Ok, starting from scratch (again).. This loads and runs just fine:
tc qdisc del dev eth0 root
tc qdisc del dev eth1 root
tc qdisc add dev eth0 root handle 10: htb
tc class add dev eth0 parent 10: classid 10:1 htb rate 10mbit
# tc class add dev eth0 parent 10:1 classid 10:10 htb rate 256kbit
tc qdisc add dev eth0 parent 10:1 sfq perturb 10
tc filter add dev eth0 parent 10: protocol ip \
u32 match ip dst 208.191.32.254 flowid 10:1
# exit
tc qdisc add dev eth1 root handle 20: htb
tc class add dev eth1 parent 20: classid 20:1 htb rate 10mbit
# tc class add dev eth1 parent 20:1 classid 20:10 htb rate 256kbit
tc qdisc add dev eth1 parent 20:1 sfq perturb 10
tc filter add dev eth1 parent 20: protocol ip \
u32 match ip src 208.191.32.254 flowid 20:1
Whereas this doesn't...
tc qdisc del dev eth0 root
tc qdisc del dev eth1 root
tc qdisc add dev eth0 root handle 10: htb
tc class add dev eth0 parent 10: classid 10:1 htb rate 10mbit
tc class add dev eth0 parent 10:1 classid 10:10 htb rate 256kbit
tc qdisc add dev eth0 parent 10:10 sfq perturb 10
tc filter add dev eth0 parent 10: protocol ip \
u32 match ip dst 208.191.32.254 flowid 10:10
# exit
tc qdisc add dev eth1 root handle 20: htb
tc class add dev eth1 parent 20: classid 20:1 htb rate 10mbit
tc class add dev eth1 parent 20:1 classid 20:10 htb rate 256kbit
tc qdisc add dev eth1 parent 20:10 sfq perturb 10
tc filter add dev eth1 parent 20: protocol ip \
u32 match ip src 208.191.32.254 flowid 20:10
When i say does and doesn't work, the first on passes data, the second
one doesn't, and the pings I was testing with showed up as dropped packets
when I ran "tc -s class ls dev eth1", which I thought odd... Especially
since they showed up in the root class... Welp, it's 4am (again), time to
get a nap...
---
Homer Parker
http://www.homershut.net
telnet://bbs.homershut.net
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2002-12-04 10:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 5:49 [LARTC] Multiple classes Homer Parker
2002-12-03 10:29 ` Stef Coene
2002-12-03 17:39 ` Homer Parker
2002-12-03 21:03 ` Stef Coene
2002-12-04 10:08 ` Homer Parker [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-103899701016552@msgid-missing \
--to=hparker@homershut.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.