From: Michele Petrazzo - Unipex srl <michele.petrazzo@unipex.it>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Limit Rates in more scalable and efficient way
Date: Fri, 05 Oct 2007 16:42:18 +0000 [thread overview]
Message-ID: <4706696A.10004@unipex.it> (raw)
In-Reply-To: <08100C47CD5D9740B09C5CDD944B2A7417108CD5@sid00102.hsr.ch>
fhartman@hsr.ch 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@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2007-10-05 16:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 13:25 [LARTC] Limit Rates in more scalable and efficient way fhartman
2007-10-05 14:57 ` Salatiel Filho
2007-10-05 16:42 ` Michele Petrazzo - Unipex srl [this message]
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=4706696A.10004@unipex.it \
--to=michele.petrazzo@unipex.it \
--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