From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Clemens Eisserer <linuxhippy@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: [NFLOG] How to determine the connection a packet belongs to?
Date: Tue, 07 Jun 2011 01:39:36 +0200 [thread overview]
Message-ID: <4DED6538.3090404@netfilter.org> (raw)
In-Reply-To: <BANLkTimnO5UzNvq6SfuWc7osck=QL=HrMw@mail.gmail.com>
On 06/06/11 16:26, Clemens Eisserer wrote:
> Hi,
>
> We are using ulog2/nflog for logging packets and connections, which
> works quite well.
>
> However we haven't found a reliable way to determine which packets
> belong to which connection.
> There seem to be two distinct IDs for both packets (nflog) as well as
> connection IDs issued by conntrack,
> is there some correlation between the two IDs?
No.
> Or is there any other (maybe even better) way to determine which
> logged packet belongs to which connection?
You can build the tuple from the packet in user-space to look up the
conntrack via libnetfilter_conntrack.
next prev parent reply other threads:[~2011-06-06 23:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 14:26 [NFLOG] How to determine the connection a packet belongs to? Clemens Eisserer
2011-06-06 23:39 ` Pablo Neira Ayuso [this message]
2011-06-07 10:40 ` Clemens Eisserer
2011-06-07 11:59 ` Jan Engelhardt
2011-06-07 12:25 ` Srinivasa T N
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=4DED6538.3090404@netfilter.org \
--to=pablo@netfilter.org \
--cc=linuxhippy@gmail.com \
--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