From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Italo Valcy <italo@dcc.ufba.br>, netfilter@vger.kernel.org
Subject: Re: How to log NAT translations
Date: Tue, 21 Sep 2010 11:45:22 +0200 [thread overview]
Message-ID: <4C987EB2.4000001@netfilter.org> (raw)
In-Reply-To: <alpine.LNX.2.01.1009211125320.30840@obet.zrqbmnf.qr>
On 21/09/10 11:26, Jan Engelhardt wrote:
> On Tuesday 2010-09-21 04:25, Italo Valcy wrote:
>
>> Actually, I wanna something more simple and specific than the command
>> above. Using 'conntrack -E', I still have to parse the package events
>> NEW, UPDATE and DESTROY if I wanna know the of a NAT
>
> So use `conntrack -Ee NEW` to limit the output :)
> If that is still too much overhead, I'm sure you can directly use
> libnetfilter_conntrack's library interface to get at these events.
You can refine this a bit more with:
`conntrack -Ee NEW --any-nat'
It was introduced in conntrack-tools-0.9.15.
next prev parent reply other threads:[~2010-09-21 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 17:24 How to log NAT translations Italo Valcy
2010-09-14 17:54 ` Jan Engelhardt
2010-09-21 2:25 ` Italo Valcy
2010-09-21 9:26 ` Jan Engelhardt
2010-09-21 9:45 ` Pablo Neira Ayuso [this message]
2010-09-21 10:22 ` Jozsef Kadlecsik
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=4C987EB2.4000001@netfilter.org \
--to=pablo@netfilter.org \
--cc=italo@dcc.ufba.br \
--cc=jengelh@medozas.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox