From: Patrick McHardy <kaber@trash.net>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] Add support to log original and NAT-ed IP addresses
Date: Tue, 21 Apr 2009 14:22:22 +0200 [thread overview]
Message-ID: <49EDBA7E.2040200@trash.net> (raw)
In-Reply-To: <alpine.DEB.2.00.0904201838090.11586@blackhole.kfki.hu>
Jozsef Kadlecsik wrote:
> On Mon, 20 Apr 2009, Patrick McHardy wrote:
>
>> Jozsef Kadlecsik wrote:
>>> On Mon, 20 Apr 2009, Pablo Neira Ayuso wrote:
>>>> I wasn't refering to any iptables target. New ulogd2 includes support
>>>> for ctnetlink, which can do this. I know, that means the extra libraries
>>>> dependencies.
>>> I see. Thanks the info, good to know that ulogd2 is capable of this.
>>> (Calling 'conntrack' for logging looked really ugly. :-)
>> In the kernel, we could log the information from the conntrack
>> entry, if any. That would allow to log the manips after they
>> have been set up.
>
> Yes, but I'd not want an unconditional logging.
I missed the point, you're already doing what I had in mind (use
ct->tuplehash->...) and the new hook is needed to even get a chance
to log the packet after SNAT.
>> Would Pablo's suggestion or the conntrack method work for you?
>
> Oh, it's not for me at all: at a workshop I was asked how to log the info
> (hint: conflicker ;-) and embarrased enough I had to admit there was no
> easy way. That's why I put together the patch, with all it's questionable
> details.
I can see that it has some informational value, but for things like
locating infected hosts, why not simply look at the traffic before
it is NATed? I currently can't come up with a real use case for
this ...
next prev parent reply other threads:[~2009-04-21 12:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 9:21 [PATCH] Add support to log original and NAT-ed IP addresses Jozsef Kadlecsik
2009-04-20 9:58 ` Pablo Neira Ayuso
2009-04-20 10:12 ` Jozsef Kadlecsik
2009-04-20 10:33 ` Jan Engelhardt
2009-04-20 10:49 ` Jozsef Kadlecsik
2009-04-20 11:08 ` Pablo Neira Ayuso
2009-04-20 11:23 ` Jozsef Kadlecsik
2009-04-20 14:40 ` Patrick McHardy
2009-04-20 16:47 ` Jozsef Kadlecsik
2009-04-21 12:22 ` Patrick McHardy [this message]
2009-04-21 18:18 ` Jozsef Kadlecsik
2009-04-22 15:59 ` Patrick McHardy
2009-04-22 20:39 ` Jozsef Kadlecsik
2009-04-23 12:12 ` Patrick McHardy
2009-04-24 8:06 ` 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=49EDBA7E.2040200@trash.net \
--to=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@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.