From: "Paul P. Pongco" <paulp@mozcom.com>
To: lartc@vger.kernel.org
Subject: [LARTC] no default leaf on HTB
Date: Mon, 24 Mar 2003 09:06:22 +0000 [thread overview]
Message-ID: <marc-lartc-104849688909764@msgid-missing> (raw)
Hello,
I have a linux bridge setup and am using HTB to bandwidth manage traffic
passing through the bridge.
I want to manage "some" of the traffic passing through the bridge. I
figured I can do this if I dont define a "default" class on the qdisc.
I will only config classes for traffic I want to manage.
Assume that i Have traffic for network 10.0.0.0/24 passing through the
bridge.
I only want to manage traffic for network 10.0.0.0/29 and 10.0.0.8/29 and
not manage the rest of the traffic for the /24
Here is my script:
###START OF SCRIPT###
#create the qdisc
tc qdisc add dev eth1 root handle 1: htb default 30
tc class add dev eth1 parent 1: classid 1:1 htb rate 608kbit ceil 608kbit prio 1
#create class for 10.0.0.0/29
tc class add dev eth1 parent 1:1 classid 1:10 htb rate 256kbit ceil \
608kbit prio 3
tc filter add dev eth1 protocol ip parent 1:0 prio 1 u32 match ip \
dst 10.0.0.0/29 flowid 1:10
tc qdisc add dev eth1 parent 1:10 handle 10: sfq perturb 10
#create class for 10.0.0.8/29
tc class add dev eth1 parent 1:1 classid 1:20 htb rate 352kbit ceil \
608kbit prio 3
tc filter add dev eth1 protocol ip parent 1:0 prio 1 u32 match ip \
dst 10.0.0.8/29 flowid 1:20
tc qdisc add dev eth1 parent 1:20 handle 20: sfq perturb 10
##Default class is commented
#Create default class
#$CLASS 1:30 htb rate 300kbit ceil 300kbit prio 1
#$QUEUE 1:30 handle 30: sfq perturb 10
##END of SCRIPT##
Ran the script with no errors. Will i be able to achieve setup that I
want? How will htb traffic no being classified since there is no default
class?
Thanks.
Paul P.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2003-03-24 9:06 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-104849688909764@msgid-missing \
--to=paulp@mozcom.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.