From: Andrew Beverley <andy@andybev.com>
To: Alex Bligh <alex@alex.org.uk>
Cc: netfilter@vger.kernel.org
Subject: Re: libnfcontrack weirdness
Date: Mon, 02 Aug 2010 19:10:23 +0100 [thread overview]
Message-ID: <1280772623.1349.3.camel@andybev> (raw)
In-Reply-To: <59381F8FA203F4555FD43BB0@Ximines.local>
On Mon, 2010-08-02 at 17:20 +0100, Alex Bligh wrote:
> I may be doing something stupid here, but I can't seem to get information
> on an existing connection through libnfconntrack.
>
> Code extract below. When passed a 4-tuple describing an existing connection,
> it prints "Found connection", when passed other stuff, it does not. So
> that much is working.
>
> However, no ATTR_ stuff relating to the connection is printed out
> except for ATTR_ORIG_PORT_* which are synonyms of what has been
> set with nfct_set_attr.
You have to use a callback function to read any information back. Before
your nfct_query you should use nfct_callback_register to register a
callback function, which should contain your get_attr calls.
> I am having difficulty finding documentation for this,
>
The documentation is sparse, but there are some good examples in the
utils folder of the source code. Also, api.c is well commented for each
of the functions.
Regards,
Andy
next prev parent reply other threads:[~2010-08-02 18:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 16:20 libnfcontrack weirdness Alex Bligh
2010-08-02 18:10 ` Andrew Beverley [this message]
2010-08-02 18:45 ` Pablo Neira Ayuso
2010-08-02 19:10 ` Jan Engelhardt
2010-08-03 12:43 ` Pablo Neira Ayuso
2010-08-03 14:12 ` Jan Engelhardt
2010-08-02 19:14 ` Andrew Beverley
2010-08-02 22:29 ` Alex Bligh
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=1280772623.1349.3.camel@andybev \
--to=andy@andybev.com \
--cc=alex@alex.org.uk \
--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 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.