From: Thomas Jarosch <thomas.jarosch@intra2net.com>
To: Thomas Jacob <jacob@internet24.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: ipt_ACCOUNT 1.15 released
Date: Mon, 20 Apr 2009 14:12:50 +0200 [thread overview]
Message-ID: <200904201412.51270.thomas.jarosch@intra2net.com> (raw)
In-Reply-To: <1240227092.27336.35.camel@enterprise.ims-firmen.de>
On Monday, 20. April 2009 13:31:32 Thomas Jacob wrote:
> > Well, for IPv4 you can alreay use "--src 172.16.0.0/16"
> > and then do "-j ACCOUNT --addr 0.0.0.0/0" to merge
> > the complete subnet into one single IP address.
>
> Hmm, then maybe haven't understood your module yet.
>
> If I specify "--src 172.16.0.0/16 -j ACCOUNT --addr 0.0.0.0/0 --tname
> X", I was under the impression that I will get entries for each single
> IP that somehow appears in packets that match --src 172.16.0.0/16
> in table X. Potentially a huge number (if you are getting DDOSed ;).
Yes, basically it works that way. The only exception is 0.0.0.0/0:
"A special subnet is "0.0.0.0/0": All data is stored in the src_bytes and
src_packets structure of slot "0". This is useful if you want to account the
overall traffic to/from your internet provider."
-> You can accumulate complete subnets on one entry if you like.
F.e. we use this to check for network activity
(=and decrase a timeout if not present).
Cheers,
Thomas
prev parent reply other threads:[~2009-04-20 12:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 15:44 ipt_ACCOUNT 1.15 released Thomas Jarosch
2009-04-14 16:10 ` Jan Engelhardt
2009-04-15 8:11 ` Thomas Jarosch
2009-04-15 8:55 ` Jan Engelhardt
2009-04-15 9:40 ` Thomas Jacob
2009-04-16 16:34 ` Thomas Jarosch
2009-04-16 18:29 ` Thomas Jacob
2009-04-16 21:19 ` Jozsef Kadlecsik
2009-04-20 10:19 ` Thomas Jarosch
2009-04-20 11:31 ` Thomas Jacob
2009-04-20 12:12 ` Thomas Jarosch [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=200904201412.51270.thomas.jarosch@intra2net.com \
--to=thomas.jarosch@intra2net.com \
--cc=jacob@internet24.de \
--cc=netfilter-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).