Found dozens of monitors that are IP based...but that does me no good really, because then I have to keep track of which user belongs to which IP, and that changes all the time.
It amazes me that there isn't an easy way to do this. Users need to log in and I can measure every other resource imaginable... why not bandwidth?
It must be on a per-user basis, not IP.
In case there is confusion.... these are users belonging to this local machine... not just random unknown hits from throughout the world (like a website). Each user has an account on the server and logs in via openssh.
Main Topics
Browse All Topics





by: macker-Posted on 2005-04-22 at 14:28:22ID: 13846853
I would say you'll either need to break things down by source/destination IP address (e.g. iptables rules which match specific IP's, just to take advantage of packet counters), or use a proxy that can monitor bandwidth.
In the case of the proxy, I'd suggest looking on freshmeat.net for something that does bandwidth shaping/limiting, as it will probably include abilities for accounting. The other approach would be a SOCKS proxy, as you can usually use a wrapper library on the client side for applications that don't support SOCKS by default.
Unique (and static) source IP's are going to be the best bet, for iptables-based accounting.