Rate Limiting w/ Class Based Queuing? 9
fwerked asks: "I have recently been commissioned by the uppers in my company to produce rate limiting system for a college apartment complex with 600 users. I am hoping to use a Linux system to limit each users rate to 128 Mb. using Class Based Queuing. In addition I will need to route, DHCP, and NAT. I was hoping there was someone out there in the Slashdot community that has implemented this on a large scale that might be able to recommend hardware specs (CPU, RAM, etc) and if these services should be divided among several boxes or dumped on one bad boy."
two suggestions (Score:1)
Secondly, as the queue discipline's application is connection based, your requirements are probably not that big. At a guess from experiance with a similar if far smaller job, I'd say you'll be fine with vanilla, mid-range hardware. I'd keep the DHCP and other "user" services on a different box, and dedicate one to being the router. I'd think 128MB of RAM would be overkill, but fast RAM and fast NIC won't hurt. CPU probably won't matter much; whatever's cheap will have gobs of spare time between packets anyway... A CPU with real cache would be preferred over a Celeron, though.
Re:You need to add in a cache server (Score:1)
You need to add in a cache server (Score:1)
Wow. That's some limit (Score:1)
I don't believe it. (Score:1)
Re:I don't believe it. (Score:1)
At least they have internet access piped into their dorms already.
---
A lesson in sharing (Score:2)
You should discretely inform select members of those 600 residents that this feature is available to them upon their activation of your custom-coded bribery module.
Just use the hardware (Score:2)
_____________
Sorry, I don't get it (Score:2)
Anyway, you could probably fine more info from: search for the following linux programs (some free, some commercial):
ipac
iog
ipa
ipaudit
pact
bandmin
ip accounting daemon
iplog
(obviously) the 2.4.x kernel.
These projects should have mailing lists where you could ask the question of "how much hardware do i need?". I would recommend getting 1 box to do the DNS, DHCP, NAT, firewall, etc. Then have 1 box upstream throttle the bandwidth (depending on how you do your NAT, you may need to do NAT from the same box).