From: Darryl Cording <dcording@ascend.net.au>
To: lartc@vger.kernel.org
Subject: [LARTC] Bandwidth throttling/limiting for all traffic
Date: Thu, 18 Nov 2004 03:29:46 +0000 [thread overview]
Message-ID: <419C172A.2050009@ascend.net.au> (raw)
Hi,
I have a rather simple problem I have to solve, well I thought it would
be simple, I've run into a problem. I think I must be missing something
fundamental.
I am trying to build a Linux router that simply throttles everything
down to certain bandwidths. That is, no priority queuing ...etc, just
slow all traffic down to the specified rates, which are 64,128,256,512
kbit. We want to setup the bandwidth on the router, then pump a known
load from an application through the router and see how that behaves
over various link speeds. (we are in a lab environment)
Using kernel 2.6.5-1.358 I simply used these commands from Stef's
version of tc from docum.org, module sch_htb is loaded.
tc qdisc add dev eth0 root handle 10: htb
tc class add dev eth0 parent 10: classid 10:1 htb rate 64kbit ceil 64kit
I thought that would do the job, but my testing from uploading files via
ftp to another box, show nothing gets shaped.
I think I've missed something here and need a clue. Alternatively can
anyone suggest any programs that are designed for doing this type of work.
Thanks
Darryl
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2004-11-18 3:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 3:29 Darryl Cording [this message]
2004-11-18 5:09 ` [LARTC] Bandwidth throttling/limiting for all traffic Jason Boxman
2004-11-18 6:20 ` Darryl Cording
2004-11-18 13:22 ` Darryl Cording
2004-11-18 13:50 ` Darryl Cording
2004-11-18 14:15 ` Andy Furniss
2004-11-18 20:09 ` Darryl Cording
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=419C172A.2050009@ascend.net.au \
--to=dcording@ascend.net.au \
--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.