From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] dont know why htb is not working
Date: Sun, 18 May 2003 08:18:58 +0000 [thread overview]
Message-ID: <marc-lartc-105324606732482@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105324107830528@msgid-missing>
On Sunday 18 May 2003 08:53, Esteban wrote:
> Stef or any "qos" guru!!:
Hi.
> hi, im managing a 1 mega connection for a company...i use debian, kernel
> 2.4.20. my idea is to priorice all www traffic..but i dont know some stuff
> about matching with the u32 filter. can anyone give me some idea of what is
> goinng worng here?
Remove the burst and the prio parameters from your htb classes. The burst is
too low to get some good shaping. And different prio's can introduce high
delays.
> #this is not working!! he downloads at 32k all the time!!
> tc filter add dev $DEV parent 1: protocol ip prio 1 u32 match ip src
> 200.69.147.69 flowid 1:30
> tc filter add dev $DEV parent 1: protocol ip prio 1 u32 match ip dst
> 200.69.147.69 flowid 1:30
And why do you have the same filter for source and destination ????
> # the rest, if need must wait and be shaped
> tc filter add dev $DEV parent 1: protocol ip prio 18 u32 match ip dst
> 0.0.0.0/0 flowid 1:20
This is not needed because 1:20 is the default htb class.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
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-05-18 8:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-18 6:53 [LARTC] dont know why htb is not working Esteban
2003-05-18 8:18 ` Stef Coene [this message]
2003-05-18 8:30 ` Esteban
2003-05-18 8:42 ` Stef Coene
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-105324606732482@msgid-missing \
--to=stef.coene@docum.org \
--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.