fhartman@xxxxxx wrote:
Hello
I'm looking for a more efficient way to limit rates to different
clients.
Right now as I understand it, I have to make a class for every
customer/ip-address I'd like to limit bandwidth.
This is right.
This means lots of configuration if i had many customers to setup
traffic shaping for.
If you have a lot of customers and not a "automatic" process, yes.
I can filter for ip-ranges, but then all ip's of that range share the
set bandwidth of the class.
right
I'd like a fixed rate for every ip in a group without configuring
classes for each address! It's a lot of work to configure thousands
of ip addresses if I have make thousand classes for it. Adding,
Deleting and Processing won't be very efficient that way.
Add ok, but why you need to "delete" and "process" a lot of IP/customers?
Is there someone who had the same problems and got to a solution or
am I just asking too much?
Here we haven't thousand of ip, but I thinks it's the same because we
develop a simple, but working solution internally that talk with a db
and ip/mac/dhcp and do the work (create class with its speed).
Just done a: cat firewall_* | wc -l and there is not so much lines:
about 1100 plus that for little internal site (where the user insert his
credential plus the admin part for add, delete, etc..) that are 2600.
I think that with a 4/5 day of work you can do your self the same.
I think, however, that if you need some advice for create the right
limiting policy and its implementation, this it the right place!
Michele
_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc