All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bridgett <adrian.bridgett@iname.com>
To: lartc@vger.kernel.org
Subject: [LARTC] wondershaper HTB thoughts
Date: Thu, 20 Jun 2002 21:54:44 +0000	[thread overview]
Message-ID: <marc-lartc-102461097702028@msgid-missing> (raw)

Hi, 

I've just started using wondershaper (HTB version) and I had a few thoughts
(probably mostly as I'm new to this):

a) there is a filter to add stuff into the 1:20 class, however that's the
default so surely this is pointless.

b) there is no ceil specified for the queues. According to the HTB
documentation, this will prevent the queues sharing bandwidth. Wouldn't
adding "ceil ${UPLINK}kbit" be a good idea?

c) an ingress filter is setup to drop packets arriving faster than "a bit
less than the max speed" in order to prevent large queues building up at the
ISP.  I don't see how this helps at all - surely this only slows traffic -
why would the queues get smaller?  Our ISP would (I'd have thought) buffer a
fixed amount - which will now take longer to get through.

Surely what we might want to do is to put an ingress limit on "bulk"
traffic. i.e. if our inbound is 30kbps max, have a root limit of 40kbps
(which we won't ever reach), then give bulk traffic a rate of 25kbps with a
ceil of 30kbps.

BTW I've just rolled iproute packages for debian with htb3.6 if anyone is
interested (just email me privately).

Adrian

Email: adrian.bridgett@iname.com
Windows NT - Unix in beta-testing. GPG/PGP keys available on public key servers
Debian GNU/Linux  -*-  By professionals for professionals  -*-  www.debian.org
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2002-06-20 21:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-20 21:54 Adrian Bridgett [this message]
2002-06-21  7:19 ` [LARTC] wondershaper HTB thoughts 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-102461097702028@msgid-missing \
    --to=adrian.bridgett@iname.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 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.