* [LARTC] Traffic Shaping QoS and rate-limiting clients
@ 2004-01-21 22:12 Michael S. Kazmier
0 siblings, 0 replies; only message in thread
From: Michael S. Kazmier @ 2004-01-21 22:12 UTC (permalink / raw)
To: lartc
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/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-01-21 22:12 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-01-21 22:12 [LARTC] Traffic Shaping QoS and rate-limiting clients Michael S. Kazmier
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox