I'm pretty sure almost all of that is built into the kernel nowadays. Check under the networking section and read the documentation that comes with the kernel. I think even iptables can tag packets for accounting purposes and you could run against that.
You're probably going to need a good reporting system and, if you're not into doing it by hand, a set of configuration tools. Ahh, I remember the old days--- struggling with CBQs in linux, when they were still unofficial patches. Now I see it each time I compile and wonder how it must have changed for the better. Remember, you'll need to put that box somewhere in your point of egress so it will need to involve routing or perhaps bridging. William Diehl -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Roger E. Rustad, Jr. Sent: Thursday, February 15, 2007 10:34 AM To: 909linux.org general mailing list Subject: [909linux] IP / bandwidth accounting solution Anyone have any ideas for a bandwidth accounting/throttling solution? I don't have the requirements nailed down yet, but basically something that I could put up and figure out who is hitting which public IPs. (Sort of like MRTG, except with the ability to cut off or throttle if it people get too crazy). If this is too broad of a question, then I'll ask it again once I know more details. Roger _______________________________________________ 909linux mailing list [email protected] http://909linux.org/cgi-bin/mailman/listinfo/909linux
