Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Don Gould <don@bowenvale.co.nz>
To: netfilter@lists.netfilter.org
Subject: Re: Traffic Accounting on Small System and User Limits.
Date: Fri, 29 Sep 2006 19:34:33 +1200	[thread overview]
Message-ID: <451CCC89.4060203@bowenvale.co.nz> (raw)
In-Reply-To: <451C9633.1020805@bowenvale.co.nz>

http://translate.google.com/translate?u=http%3A%2F%2Fopenskills.info%2Finfobox.php%3FID%3D1157&langpair=it%7Cen&hl=en&ie=UTF-8&oe=UTF-8&prev=%2Flanguage_tools

Does this example mean that the limit is applied to just the one IP of 
10.0.0.5 ?



Don Gould wrote:
> This is a requirement for a small system I'm building for a local motel 
> to be able to give internet access away free to their customers.
> 
> I have looked in to a bunch of different stuff but don't know the best 
> way to go.  I know this might not even be the right list to ask on, so 
> please be kind. :)
> 
> OPEN SOURCE GPL PLEASE - I have already done some work on some systems 
> to get me what I want...  all the work I'm doing is on open source stuff 
> and is/will be made available back to the community, so, if you have a 
> need for this work as well but can't help, then please feel free to drop 
> me a line and I'll keep you informed.
> 
> 1. I want to keep a record of the amount of data each user uses over a 
> given amount of time.  I know the users IP number and their MAC address. 
>  I modified DNSMasq [1] to tell me this each time the user issues a DHCP 
> request.
> 
> 2.  It is proposed that each MAC will be given 50mb of data to use. 
> After this the user/MAC will have to be authorised to have more.
> 
> The servers I'm using will run Debian Saige and are only small - p2 or 3 
> with ~30 to 64mb ram and 2 - 3gb hard disk.  Each server only has to 
> look after < 50 clients and in most cases wouldn't get more than 10 
> using it at a time.
> 
> My problem is that I don't know how I should count the data used in a 
> light weight way.
> 
> I've read that packet counting programs can be CPU intensive.
> 
> vnstat looked good but doesn't count by IP or MAC (from what I can see).
> 
> 
> I read in some of the netfilter documentation (which is fantastic btw) 
> that iptables can place limits on accounts, but didn't fully understand it.
> 
> Can anyone make any recommendations?
> 
> TIA
> 
> Cheers Don
> 
> [1] The code is rough and still have debug statements in it, see: 
> http://www.tcn.bowenvale.co.nz/content/view/44/35/
> 
> I'm no C programmer so please don't flame me :)  Be kind :)
> 

-- 
Don Gould
www.thinkdesignprint.co.nz - www.tcn.bowenvale.co.nz - 
www.bowenvale.co.nz - www.hearingbooks.co.nz - SkypeMe: 
ThinkDesignPrint - Good ideas:  www.solarking.co.nz



  reply	other threads:[~2006-09-29  7:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-29  3:42 Traffic Accounting on Small System and User Limits Don Gould
2006-09-29  7:34 ` Don Gould [this message]
2006-09-29 10:06 ` Half the answer... " Don Gould
     [not found] <359501767.17840@mail.nankai.edu.cn>
     [not found] ` <451CA750.7050209@mail.nankai.edu.cn>
2006-09-29  4:55   ` Bo Yang
2006-09-29  6:55     ` Don Gould
2006-09-29  6:58     ` Don Gould
2006-09-29  7:35     ` Don Gould

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=451CCC89.4060203@bowenvale.co.nz \
    --to=don@bowenvale.co.nz \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox