From: Ken-ichirou MATSUZAWA <chamaken@gmail.com>
To: Gadre Nayan <gadrenayan@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Confusion regarding nfct_query and nfct_callback_register
Date: Fri, 12 Feb 2016 16:30:32 +0900 [thread overview]
Message-ID: <20160212073032.GA320@gmail.com> (raw)
In-Reply-To: <CAKJ7aR5QqKWJadptNGrUruWX9JQm3C97bhHqvHY3AR11HXXHyQ@mail.gmail.com>
Hi,
On Fri, Feb 12, 2016 at 09:40:49AM +0530, Gadre Nayan wrote:
> Who is providing both these structures (struct nf_conntrack *ct, void
struct nf_conntrack is allocated by nfct_new(). You would find this
function called in __callback() in src/callback.c. Then it parses
nlmsg and updates nf_conntrack, calls callback function you
registered.
The __callback() is registerd as callback of which libnfnetlink will
call when conntrack nlmsg has received, at nfct_callback_register()
in src/conntrack/api.c.
# it seems that using nfct_callback_register, functions related to
# libnfnetlink, is discouraged for me.
I hope this is an answer you are looking for.
Thanks,
next prev parent reply other threads:[~2016-02-12 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 4:10 Confusion regarding nfct_query and nfct_callback_register Gadre Nayan
2016-02-12 7:30 ` Ken-ichirou MATSUZAWA [this message]
2016-02-23 4:16 ` Gadre Nayan
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=20160212073032.GA320@gmail.com \
--to=chamaken@gmail.com \
--cc=gadrenayan@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