All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corey Hickey <bugfood-ml@fatooh.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] wondershaper question
Date: Fri, 02 Apr 2004 04:38:40 +0000	[thread overview]
Message-ID: <406CEE50.4070508@fatooh.org> (raw)
In-Reply-To: <9911B83A96D5CF44B5F326FF60E6EB690AD14F@mailsvr.leadingside.com.my>

Chris Winfield-Blum wrote:
> Maybe there is another solution to this problem?
> 
> The problem is that I have had a couple of users on the network hogging
> the bandwidth and while we do have a policy implemented sometimes the
> downloads are genuinely work related (eg downloaded a new version of an
> application we use for development)
> 
> Sooo what I NEED is
> 
> A script that will ensure that ports 80, 25, 110, 443, etc are priority
> Then that these are then are then "shaped" to not allow one person to
> hog it all.
> 
> In an IDEAL situation I would like to break it up into classes
> 
> Server Class: that has access to ALL ports and are priority for any
> traffic (maybe I can set them a guaranteed 100Kb/s) 
> 
> User Class: that has priority access (that doesn't override the server
> class) to ports 80, 25, 110 etc. Perhaps the remaining 156Kb/s is
> divided evenly?
> 
> Any suggestions? Im really NEW to this and would love some example
> scripts (preferably commently highly :P hehe)
> 
> This was the address of the other script that I found:
> http://www.surestorm.com/qos/
> 
> I am not "set" on using wondershaper..
> 
> Thanks for all your help
> 
> Chris
> 

Wondershaper and other such scripts are good examples, but if you want
very fine-grained control of your traffic shaping, you'll probably want
to write your own script (or at least tweak one). Don't be intimidated
by the apparent complexity of the examples you see -- although the
commands for shaping traffic are probably unlike anything you've seen
before, they're not hard to understand after reading the available
documentation.

Of course, www.lartc.org is a good place to start. Look through chapter
9, but don't worry if you don't understand everything the first time.
The qdisc you want to use is htb (as you can see, that's the heart of
wondershaper), and there's a good in-depth description at:
http://luxik.cdi.cz/~devik/qos/htb/
(follow the link for "user guide").

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

  parent reply	other threads:[~2004-04-02  4:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-02  2:03 [LARTC] wondershaper question Chris Winfield-Blum
2004-04-02  2:54 ` Jason Boxman
2004-04-02  3:29 ` Chris Winfield-Blum
2004-04-02  4:38 ` Corey Hickey [this message]
2004-04-02 15:03 ` gypsy
2004-04-02 15:44 ` gypsy
2004-04-02 16:40 ` Corey Hickey

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=406CEE50.4070508@fatooh.org \
    --to=bugfood-ml@fatooh.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.