Traffic rate limiting per IP on CentOS 5.0?

Trionnis · 05-16-2007, 10:46 AM

Hello all,

I've been searching for the past couple of days for a solution to a problem, and I'm hoping the gurus around here can help

What I need to accomplish is to be able to set a rate limit on a per-ip basis, on aliased ips. Something that works simply is the best. I've found a few things that would work like I'd want, such as http://lwn.net/1998/1119/shaper.html , however that seems to be extremely outdated.

I don't need all the extra features that tc provides, and frankly, the person that's asking me to help them with this likely wouldn't have the time or the patience to mess with such a complex setup. Something like "./ratelimit 10.0.0.1 10" to limit the IP 10.0.0.1 to 10mbps (both ways would be ideal), is just the ticket. I have no problems building a small script to handle some of the setup, but I would *really* rather avoid having to muck with tc configs for so simple a task.

Any suggestions or pointers?

Thanks

acid_kewpie · 05-17-2007, 04:15 AM

well often you don't really want to limit anything, just shape. it's a sad state if you arbitrarily carve up bandwidth that could be amicably used between processes. try the wondershaper script... http://lartc.org/wondershaper/

Trionnis · 05-17-2007, 07:54 AM

Well, it actually *is* a need to carve up bandwidth (metaphorically speaking), as this is for customers that are going to be buying a preset Mbps on their IP, and I need to limit it to what they've bought. Let me give you a bit of an explanation and maybe that will help.

I'm setting this up for a client than plans to sell shoutcast hosting to his customers on a base per-mbps cost. So if one of his customers buys 8Mbps, he needs to be able to set it up so their IP can't exceed 8Mbps. This is kind of for his protection to prevent massive overuse and costs.

edit: I forgot to mention that this will be used on virtual interfaces (e.g. eth0:1, eth0:2, etc), which seems to rule out a few of the things I've found as they're designed to work on physical interfaces only.

I'll certainly take a look at that script though, if it can do what I need, that's great. Thanks for the pointer!