From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] What is the reccomended minimum rate for leaf htb classfor
Date: Wed, 06 Oct 2004 10:00:34 +0000 [thread overview]
Message-ID: <4163C242.7040704@metamorpher.de> (raw)
In-Reply-To: <20041006073827.5C1826CB7C7@mail.caucasus.net>
Zviad O. Giorgadze wrote:
> My ISP provides guarantied 115kbit bandwidth for GLOBAL TRAFFIC. During the low load period (early morning, evening, night) customers can get up to 1mbit traffic.
That's download traffic we're talking about, since you seem to be
shaping on your local LAN interface? Variable rate ISPs are tough
to shape right, I guess...
Does this 115kbit vs. 1mbit thing solely depend on ISP load, or does it
depend on day of time? In the latter case, I'd let a cron job replace
the HTB class structure, so that you have 115kbit ceil during the day
when you really only get 115kbit and 1mbit ceil during the night when
you actually get 1mbit.
But I guess it's not that easy, huh?
> According to PRIO settings I try to give all available bandwidth (above the guarantied rate) to IP address. I think that all other IP-s get it's guarantied rate or may be I'm wrong?
You have a 100mbit line, of which you only allow 1mbit to be used (Why
make a 100mbit class then?). Unknown traffic (LAN, most likely) goes to
class 1:22 (Why? Shouldn't only ISP traffic go there?). There is no
distinction between ISP and LAN traffic at all... does that mean that
there is no other traffic than ISP from/to your HTB box?
Does anyone know how HTB performs on such a line? My guess would be that
HTB doesn't have a clue that there are actually only 115kbit, and thus
will allow classes to borrow too much, letting other classes starve.
Andreas
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-10-06 10:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 7:39 [LARTC] What is the reccomended minimum rate for leaf htb class for accurate operation? Zviad O. Giorgadze
2004-10-06 8:14 ` [LARTC] What is the reccomended minimum rate for leaf htb class Andreas Klauer
2004-10-06 8:47 ` [LARTC] What is the reccomended minimum rate for leaf htb class for accurate operation? mjoachimiak
2004-10-06 10:00 ` Andreas Klauer [this message]
2004-10-06 10:54 ` [LARTC] What is the reccomended minimum rate for leaf htb classfor " mjoachimiak
2004-10-06 11:01 ` [LARTC] What is the reccomended minimum rate for leaf htb classfor Andreas Klauer
2004-10-06 14:09 ` [LARTC] What is the reccomended minimum rate for leaf htb class for gypsy
2004-10-06 19:05 ` [LARTC] What is the reccomended minimum rate for leaf htb class for accurate operation? Stef Coene
2004-10-07 6:54 ` Re: [LARTC] What is the reccomended minimum rate for leaf htb class foraccurate operation? Zviad O. Giorgadze
2004-10-07 7:03 ` Re: [LARTC] What is the reccomended minimum rate for leaf htb class for accurate operation? Zviad O. Giorgadze
2004-10-07 7:53 ` [LARTC] What is the reccomended minimum rate for leaf htb classfor " mjoachimiak
2004-10-07 14:29 ` [LARTC] What is the reccomended minimum rate for leaf htb classfor Andy Furniss
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=4163C242.7040704@metamorpher.de \
--to=andreas.klauer@metamorpher.de \
--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.