From: Alex Bligh <alex@alex.org.uk>
To: Andrew Beverley <andy@andybev.com>
Cc: netfilter@vger.kernel.org, Alex Bligh <alex@alex.org.uk>
Subject: Re: libnfcontrack weirdness
Date: Mon, 02 Aug 2010 23:29:42 +0100 [thread overview]
Message-ID: <BE4D961E8D8AD306DA51826B@nimrod.local> (raw)
In-Reply-To: <1280772623.1349.3.camel@andybev>
--On 2 August 2010 19:10:23 +0100 Andrew Beverley <andy@andybev.com> wrote:
> 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.
Thanks. I got this working in the end. However, somewhat bizarrely
the relevant information (the internal port number) in the callback is
returned in ATTR_ORIG_SRC_PORT (etc.), despite this being what is
searched on (the external port number). I am a bit confused by this,
but it seems to work.
>> 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.
Thanks. Just to give you a clueless newbie's point of view, I was trying
to find either a web page, or a manpage. Doxygen would clearly help
with the latter. Even a README file that explicitly pointed at api.c
if that's where to look (the current reference is somewhat cryptic -
I thought it was to the .h files) would be a lot better than a poke in
the eye.
--
Alex Bligh
prev parent reply other threads:[~2010-08-02 22:29 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
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 [this message]
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=BE4D961E8D8AD306DA51826B@nimrod.local \
--to=alex@alex.org.uk \
--cc=andy@andybev.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