All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: lartc@vger.kernel.org
Subject: [LARTC] HTB for multiple users, good or bad approach?
Date: Fri, 01 Aug 2003 14:41:33 +0000	[thread overview]
Message-ID: <marc-lartc-105974896414405@msgid-missing> (raw)

Hi,

I have to share my internet connection (DSL) with 
several other users and want to set up some kind of
traffic shaping, using HTB.

Some users do a lot of filesharing (which take almost
all available bandwith, leaving nothing for other users),
others do online gaming and therefore need guaranteed
fast interactive connections, normal traffic then is
somewhere in the middle and should be divided between
users.

The script I've come up with so far can be found there:
http://www.metamorpher.de/files/ipshape.sh

I tried to do the following classes setup:
(highest priority first)

# Class Layout:
#
# 1:1   - Line (DSL 768kbit down, 128kbit up)
#       |
# 1:10  \---- Interactive
#       |   |
# 1:101 |   \---- ping
# 1:102 |   \---- Gameserver
# 1:103 |   \---- MUDs
# 1:104 |   \---- ssh
# 1:105 |   \---- ...
#       |
# 1:20  \---- Users
#       |   |
# 1:201 |   \---- User A
# 1:2.. |   \---- User ...
# 1:2XX |   \---- User X
#       |
# 1:30  \---- Less Important Traffic
#           |
# 1:301     \---- Filesharing
# 1:302     \---- Local Traffic
# 1:303     \---- Unknown Traffic

I want any class to be able to take over the whole line if no other class
is active. Thus, I divided the rate values up (give every class some %
of bandwidth), but set all ceil values to maximum.

To shape incoming traffic, I attached these classes to the network
device through which packets are forwarded to the users.

Do you think that approach could work?
I don't quite know myself, because I can hardly find
any way to test it properly.

My script currently definitely does something,
as bandwith is limited. However, I still get
lots of (apparently) error messages I can't get rid of:

HTB: quantum of class 20101 is small. Consider r2q change.<4>HTB: quantum of class 20103 is small. Consider r2q change.<4>HTB: quantum of class 20104 is small. Consider r2q change.<4>HTB: quantum of class 20030 is small. Consider r2q change.<4>HTB: quantum of class 20002 is big. Consider r2q change.<7>htb*g jê219489
HTB: quantum of class 10101 is small. Consider r2q change.<4>HTB: quantum of class 10104 is small. Consider r2q change.<4>HTB: quantum of class 10030 is small. Consider r2q change.<6>HTB init, kernel part version 3.7

Are those critical? I tried a wide variety of values for r2q,
but it didn't help.

Any help, opinions and other comments highly appreciated.

-- 
Andreas Klauer <andreas.klauer@metamorpher.de>

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2003-08-01 14:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-01 14:41 Andreas Klauer [this message]
2003-08-01 15:39 ` [LARTC] HTB for multiple users, good or bad approach? Stef Coene
2003-08-01 17:28 ` Andreas Klauer
2003-08-02 20:52 ` 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-105974896414405@msgid-missing \
    --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.