From: Mart Frauenlob <mart.frauenlob@chello.at>
To: netfilter@vger.kernel.org
Subject: Re: iptables for bandwidth tracking
Date: Wed, 06 Jan 2010 14:34:05 +0100 [thread overview]
Message-ID: <4B44914D.4060300@chello.at> (raw)
In-Reply-To: <4B44078D.4000103@twentyten.org>
On 06.01.2010 05:16, netfilter-owner@vger.kernel.org wrote:
> Hey guys,
>
> Our servers are in a managed hosting solution where we do not have
> access to our switch. We have a lot of users that use our VPN solution
> and I'd like to better track their bandwidth usage. I'm considering two
> options for this:
>
> - Using one of the many libpcap daemons to monitor and record traffic
> patterns
> - Use iptables
>
> Each VPN node has the possibility of 64,000 IP addresses so if I used
> iptables, I'd need to create iptables rules for each of those IP
> addresses. That seems silly to me, but am I better off doing that than
> running a daemon that at the end of the day will basically do the same
> thing? Thanks in advance.
>
>
You might take a look at the ACCOUNT target from xtables-addons.
http://xtables-addons.sourceforge.net/
regards
Mart
prev parent reply other threads:[~2010-01-06 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 3:46 iptables for bandwidth tracking Michael Nguyen
2010-01-06 12:13 ` John Haxby
2010-01-06 13:34 ` Mart Frauenlob [this message]
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=4B44914D.4060300@chello.at \
--to=mart.frauenlob@chello.at \
--cc=netfilter@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.