From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "Carlos Sülz" <csulz@cmet.net>
Cc: Eric Leblond <eric@inl.fr>, netfilter@vger.kernel.org
Subject: Re: Logging nat translations
Date: Fri, 29 Aug 2008 12:50:29 +0200 [thread overview]
Message-ID: <48B7D475.4010100@netfilter.org> (raw)
In-Reply-To: <20080828171740.GB19634@khasse.inl.fr>
Eric Leblond wrote:
> Hello,
>
> On Thursday, 2008 August 28 at 10:10:20 -0400, Carlos Sülz wrote:
>> Hi NF people, I've a question related a Logging issue.-
>>
>> I'm already making a log with my conntrack session, but I need to log
>> the "nated-IP" because auditoring.-
>>
>> I mean...
>> the "-j LOG" parameter log the SRC-IP and the DST-IP (src is the IP
>> before nat and the dst is... well, U know it.)
>> I need something like SRC= 10.x.x.x, NAT=200.x.x.x , DST=201.x.x.x
>> If there is a way to get this, please let me know.
>
> Have a look at ulogd2 which is able to log every connection tracking
> event in a file or in a database.
>
> Some links:
> http://netfilter.org/projects/ulogd/index.html
> http://software.inl.fr/trac/wiki/ulogd2/user
You can also get them via the command line tool `conntrack':
# conntrack -E --src-nat
or
# conntrack -E --dst-nat
or even:
# conntrack -E --dst-nat 1.2.3.4
to filter only destination NAT to 1.2.3.4.
--
"Los honestos son inadaptados sociales" -- Les Luthiers
next prev parent reply other threads:[~2008-08-29 10:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 14:10 Logging nat translations Carlos Sülz
2008-08-28 17:17 ` Eric Leblond
2008-08-29 10:50 ` Pablo Neira Ayuso [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-19 3:15 Logging NAT Translations Craig Bernstein
2007-05-20 19:23 ` Petr Pisar
2007-05-22 20:09 ` Jan Engelhardt
2007-06-06 2:10 ` Craig Bernstein
2007-06-06 6:01 ` Jan Engelhardt
2007-06-06 7:15 ` Craig Bernstein
2007-06-07 8:09 ` Jan Engelhardt
2007-06-07 22:36 ` Pascal Hambourg
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=48B7D475.4010100@netfilter.org \
--to=pablo@netfilter.org \
--cc=csulz@cmet.net \
--cc=eric@inl.fr \
--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