From: Piotrek Kaczmarek <kaczorek@k.daleka.net>
To: netfilter@lists.netfilter.org
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: accounting NAT-ed packets
Date: Sun, 19 Dec 2004 23:48:50 +0100 [thread overview]
Message-ID: <20041219224850.GA25652@daleka.net> (raw)
In-Reply-To: <20041219101257.GA16236@daleka.net>
On Sun, Dec 19, 2004 at 11:12:57AM +0100, Piotrek Kaczmarek 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?
I've found a solution. I've added POSTROUTING chain to the raw table but with
higher priority than a nat table, so it is now possible to intercept
packets with nat-ed source addresses. You can download patch from
http://k.daleka.net/iptable_raw.patch
Could you consider applying this? I couldn't find other solution to do this.
--
Piotrek Kaczmarek
prev parent reply other threads:[~2004-12-19 22:48 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
2004-12-19 22:48 ` Piotrek Kaczmarek [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=20041219224850.GA25652@daleka.net \
--to=kaczorek@k.daleka.net \
--cc=netfilter-devel@lists.netfilter.org \
--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 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.