Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Michael S. Kazmier" <mkazmier@sofast.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Traffic Shaping QoS and rate-limiting clients
Date: Wed, 21 Jan 2004 22:12:29 +0000	[thread overview]
Message-ID: <00a701c3e06b$a8fa3c00$b53afea9@kazvx88> (raw)

Hello all,

I am trying to figure out a way to traffic shape for QoS (ie, prioritize
different types of traffic) for an entire network and ALSO rate limit /
shape individual users on this network.  

Now, I understand it all for rate control on users - what I can't figure out
is how we can shape / prioritize by protocol (ie, treat ssh / telnet higher
than www which is higher than ftp, etc).  I suppose we could use the "split"
command (9.5.4.5. Other CBQ parameters: split & defmap) but we would still
require a separate rule for each user.  

What does that mean -> well, we have one rule for each interface (minimum 2)
- one rule for each customer for each interface - AND one rule for each
traffic filter for each customer for each interface!!!  Obviously with
several hundred users and 4 or 5 or 10 or 20 traffic prioritizations, we are
looking at an unmanageable situation.

For those that are graphically inclined, here is what I am wanting to do
utilizing CBQ:

             ROOT 1:
             /   \
Business(1:1)     Residential(1:2)    <-- Each PRIO Business 3, Residential
4, possible rate limit
        /              \
(Traffic Flow)      (Traffic Flow)    <-- PRIO and rate limit web, ftp, ssh,
etc.
      /                  \
(Individual Cust) (Individual Cust)   <-- Individual rate limit per customer




Please -  Any thoughts on achieving the above would be greatly appreciated!

Thanks in advance! 

--Mike

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

                 reply	other threads:[~2004-01-21 22:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='00a701c3e06b$a8fa3c00$b53afea9@kazvx88' \
    --to=mkazmier@sofast.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox