From: "Jay Wineinger" <shad@wnoc.com>
To: lartc@vger.kernel.org
Subject: [LARTC] HTB problem
Date: Thu, 23 Jan 2003 22:47:52 +0000 [thread overview]
Message-ID: <marc-lartc-104336247516241@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100803866815679@msgid-missing>
Hi,
Ive been looking at tinkering with the linux traffic control stuff
lately and decided to try out the htb qdisc. My setup is as follows:
2 interfaces: eth0 goes to internet, and eth1 goes to a NAT'd subnet. eth0
has a 7mbit link, but only a 4.5 mbit link to the internet while eth1 is a
100 mbit link to the internal subnet. The box that is doing the routing
(and tc soon, hopefully) acts as webserver,dhcp,firewall,NAT,and fileserver
for the internal subnet. The internal network (at a college) has heavy
kazaa and other filesharing usage over the internet. I want to use the
lartc utilities to make the bulk traffic from filesharing,etc to be the
lowest priority and have interactive (ssh), mail, and http be higher prios
(in that order).
Anyway, I dont want to limit the traffic that is going TO the server only,
ie. people taking files off my server, and I dont really care who is
creating the traffic, I just want priorities on types of traffic. That
being the case, I decided to do the shaping on the eth0 interface. Ive
setup rules in iptables to mark the different kinds of traffic.
With that done, I created the root htb qdisc with the following:
$TC qdisc add dev eth0 root handle 1: htb default 20
However, I get an error about illegal rate when I try to create a class
with:
$TC class add dev eth0 parent 1:1 classid 1:10 htb rate 30kpbs burst 2k
prio 1 ceil 100kbps
I wondered if my tc version wasnt up-to date enough to work with htb, but it
was the one downloaded from the htb homepage at
http://luxik.cdi.cz/~devik/qos/htb/v3/htb3.6-020525.tgz
# ./tc -V
tc utility, iproute2-ss991023
is there anything else that might need updating, or is my syntax wrong? any
suggestions about my setup would be welcome as well, since this is my first
attempt at this
thanks,
jay
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-01-23 22:47 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 2:46 [LARTC] HTB problem yangrunhua
2001-12-11 9:21 ` bert hubert
2001-12-11 9:34 ` yangrunhua
2001-12-11 9:35 ` yangrunhua
2001-12-11 11:10 ` bert hubert
2001-12-12 5:47 ` yangrunhua
2001-12-12 10:02 ` yangrunhua
2001-12-12 11:40 ` Martin Devera
2001-12-12 13:50 ` bert hubert
2001-12-12 23:48 ` yangrunhua
2001-12-13 10:07 ` bert hubert
2002-06-26 0:22 ` [LARTC] htb problem Omar Armas
2002-06-26 0:32 ` Tomasz Wrona
2002-12-09 18:19 ` [LARTC] HTB Problem lartc
2002-12-09 18:57 ` Stef Coene
2003-01-23 22:47 ` Jay Wineinger [this message]
2003-01-24 2:15 ` [LARTC] HTB problem mingching.tiew
2003-01-24 2:39 ` Jay Wineinger
2003-06-12 19:21 ` [LARTC] htb problem Ratel
2003-06-12 19:23 ` Esteban
2003-06-12 19:35 ` Stef Coene
2003-06-12 20:04 ` Morten Isaksen
2003-06-12 20:51 ` Stef Coene
2003-06-12 20:54 ` Stef Coene
2003-06-12 21:15 ` Stef Coene
2003-06-14 21:46 ` terahz
2003-06-15 18:14 ` Stef Coene
2003-06-25 11:14 ` Ratel
2003-07-24 14:26 ` Delcho
2003-07-28 17:49 ` Stef Coene
2003-09-30 13:44 ` [LARTC] HTB Problem Guilherme Benkenstein
2003-09-30 19:59 ` Stef Coene
2003-12-02 23:08 ` [LARTC] HTB problem Mihai Tanasescu
2003-12-04 5:16 ` Mihai Tanasescu
2003-12-04 7:40 ` Catalin BOIE
-- strict thread matches above, loose matches on Subject: below --
2004-09-06 21:56 Cow
2004-09-07 11:08 ` zytek
2004-09-07 20:28 ` Cow
2004-09-07 21:16 ` [LARTC] HTB Problem Cow
2004-09-07 21:18 ` [LARTC] HTB problem Cow
2004-09-07 21:53 ` Andreas Klauer
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-104336247516241@msgid-missing \
--to=shad@wnoc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox