Custom builds of ddwrt on a router can do it. One commercial (subscription) example of this is webgauge.co.nz, who give you a reflashed and branded asus router and a monthly fee to manage your users, their devices, and traffic allowances/restrictions. On 24 Jul 2011 15:31, "Volker Kuhlmann" <[email protected]> wrote: > On Sun 24 Jul 2011 13:30:43 NZST +1200, Christopher Sawtell wrote: > >> > Does anyone have a solution for managing a family's data cap btw >> > family members? > >> http://doc.pfsense.org/index.php/How_can_I_monitor_bandwidth_usage%3F#pftop > > Nope. > > First make up your minds about terminology. > > Bandwidth: throughput, or data transfer rate, in bytes per time. > > Traffic volume: total amount of bytes transferred. > > A lot of software can't get that right. Unless you're an ISP you're not > likely to care about bandwidth, unless you want to find out who is > saturating your pipe right now with pr0n downloads while you're trying > to have a VoIP conversation. The question was about who is using up the > data cap, so is about volume, not bandwidth. > > pftop only gives you a current snapshot, like ps, top or ntop. For a > cumulative traffic sum it's pretty useless. > > I had reason to investigate this problem too, but so far have come up > blank. The problem is "which internal IP address is using up the > Internet traffic". Of all the solutions on the pfsense wiki all are > useless for this problem. (Must be made by Americans - they don't have > data caps ;-) ) Some of those suggestions are not too bad if you only > have 1 LAN and no DMZ or OPT interfaces. Another (bandwidthd) will tell > you with which internet hosts your traffic limit has been evaporated, > but doesn't tell which LAN IP did it (d'oh). All those monitors are made > for different purposes. > > The only suitable solution seems to me to be using pfsense to collect > netflow data, and then find some way to collect and display it. It's > what your ISP would do, way over the top for home, but there's no useful > home solution that I could see. I'd be very interested to hear I've been > wrong! > > Of course that might or might not be relevant to the original question, > which didn't say whether the sought after solution was LAN IP-based, > based on user-logins to a proxy, or something else altogether. > > Volker > > -- > Volker Kuhlmann > http://volker.dnsalias.net/ Please do not CC list postings to me. > > _______________________________________________ > Linux-users mailing list > [email protected] > http://lists.canterbury.ac.nz/mailman/listinfo/linux-users
_______________________________________________ Linux-users mailing list [email protected] http://lists.canterbury.ac.nz/mailman/listinfo/linux-users
