Mihai Vlad wrote:
Thanks,
The only issue here is that for each service I need to create 200 child
classes if I have 200 clients...
Let me explain the problem better
I have the following connection from my ISP: (1024/1024) (rate/ceil)
1) First, I want to divide the 1024 into smaller pieces based on priority:
256/256 - P2P (I want to limit the P2P traffic as much as possible)
256/1024 - HTTP
256/1024 - FTP
256/1024 - SSH, Games, etc
(I do not say that this is the best approach but it does not matter - it is
just an example)
2) Second task: Suppose I have previously shaped the traffic the way I want,
I need 200 classes for 200 clients in which to tell the rate and ceil for
each of them
16/512 - Client 1
16/256 - Client 2, etc
If I would have 200 clients and 10 types of services and childs to service
classes, this means 2000 client classes...
I was thinking of a funny setup:
Route the traffic to 2 IMQ's
-> First: traffic passes imq0 - and is shaped based on services
-> Second: traffic from imq0 is routed to imq1 - where it is shaped
based on IP of the client.
What do you think about this?
I think you will need to use imq but I would just use 1 and do the
second level shaping on the real interface(s).
Andy.
_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
