Rate Limiting w/ Class Based Queuing?
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."
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.
I see even classic Slashdot is now pretty much unusable on dial up anymore.
Unless you're running fiber to each user you probably aren't going to be able to exceed 100Mbps anyway. If I were you I'd just install 100BT switches and then you're problem is completely taken care of.
_____________
I don't want free as in beer. I just want free beer.
I'm sorry, I didn't understand the question, but I might as well share what I know. Are we talking about an internet or regular network connection? If you want each person to be limited to 128Mbps, isn't that 128 * 600 = 76Gbps? That's a little more than Internet2 has to offer, isn't it?
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).
Daniel