From: George Alexandru Dragoi <waruiinu@gmail.com>
To: Piotrek Kaczmarek <kaczorek@k.daleka.net>
Cc: netfilter@lists.netfilter.org
Subject: Re: accounting NAT-ed packets
Date: Sun, 19 Dec 2004 14:04:34 +0200 [thread overview]
Message-ID: <3063e50412190404c2625ca@mail.gmail.com> (raw)
In-Reply-To: <20041219101257.GA16236@daleka.net>
Yea, in mangle POSTROUTING, or in filter FORWARD the packets which are
going to be nat-ed. nat table counts only the first packet from a
stream
On Sun, 19 Dec 2004 11:12:57 +0100, Piotrek Kaczmarek
<kaczorek@k.daleka.net> wrote:
> Hello,
>
> I want to account all traffic from the address assigned to the linux box
> (including NAT, locally generated traffic), but i can't. The rule
> iptables -t mangle -A POSTROUTING -s 213.25.213.42
> seems not to ,,catch'' NAT-ed packets, only locally generated traffic.
>
> Is there any method to ,,catch'' packets after NAT with netfilter?
>
> Best Regards,
>
> --
> Piotr Kaczmarek
>
>
--
Bla bla
next prev parent reply other threads:[~2004-12-19 12:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-19 10:12 accounting NAT-ed packets Piotrek Kaczmarek
2004-12-19 12:04 ` George Alexandru Dragoi [this message]
2004-12-19 22:48 ` Piotrek Kaczmarek
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=3063e50412190404c2625ca@mail.gmail.com \
--to=waruiinu@gmail.com \
--cc=kaczorek@k.daleka.net \
--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