From: Michael Fincham <michael@hotplate.co.nz>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] HTB and burst...
Date: Thu, 03 May 2007 20:44:17 +0000 [thread overview]
Message-ID: <1178225057.13679.0.camel@localhost> (raw)
In-Reply-To: <1178155372.3116.12.camel@michael-desktop>
It looks as though I may have had the hierarchy wrong... I had a class
with a qdisc as a child then all my classes as children of the qdisc...
now borrowing allowed as they're all root qdiscs.
-Michael
On Thu, 2007-05-03 at 08:53 -0700, Flechsenhaar, Jon J wrote:
> I would need to see your actual script to say for sure.
>
>
> Jon Flechsenhaar
> Boeing WNW Team
> Network Services
> (714)-762-1231
> 202-E7
>
> -----Original Message-----
> From: Michael Fincham [mailto:michael@hotplate.co.nz]
> Sent: Wednesday, May 02, 2007 6:23 PM
> To: lartc@mailman.ds9a.nl
> Subject: [LARTC] HTB and burst...
>
> Hey everyone,
>
> For some reason my htb configuration isn't allowing any class to burst
> up to its ceiling ever, even when the link is only being utilised by one
> class that class only ever gets its assigned rate and exactly that
> assigned rate...
>
> The hierarchy I have is 1: at the root with no default, then 1:2 and 1:3
> under that, both with assigned rates, then 2: and 3: under those
> respectively with defaults configured. Iptables marks the packets based
> on incoming interface which then get filtered to either 1:2 or 1:3 and
> filtered again, shaped accordingly etc... All classes and qdiscs are HTB
>
> Any ideas anyone?
>
> --
> Michael Fincham <michael@hotplate.co.nz>
>
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2007-05-03 20:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 1:22 [LARTC] HTB and burst Michael Fincham
2007-05-03 12:59 ` Andy Furniss
2007-05-03 20:44 ` Michael Fincham [this message]
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=1178225057.13679.0.camel@localhost \
--to=michael@hotplate.co.nz \
--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.