From: Pablo Neira Ayuso <pablo@netfilter.org>
To: "Blažej Krajňák" <blazej.krajnak@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: ulogd packet based logging with CT info
Date: Thu, 19 Aug 2021 12:16:28 +0200 [thread overview]
Message-ID: <20210819101628.GA2036@salvia> (raw)
In-Reply-To: <CAMEa=f=Z0Uh9jtLi_Le4pR9PSmoUxs71fb_73OHngSwXF4PTyA@mail.gmail.com>
On Wed, Aug 18, 2021 at 10:06:40PM +0200, Blažej Krajňák wrote:
> I'm really confused from searching a bug.
>
> Getting nf_conntrack via nflog_nlmsg_parse(ph, attrs); is (I think)
> bad because ph parameter must be nlmsghdr not nfulnl_msg_packet_hdr
Right, nflog_nlmsg_parse() should take the nlh parameter.
> So different way. I added new getters to libnetfilter_log.c:
>
> struct nf_conntrack *nflog_get_ct(struct nflog_data *nfad)
> {
> return nfnl_get_pointer_to_data(nfad->nfa, NFULA_CT, struct nf_conntrack);
> }
This will not work (as you noticed). The kernel does not store a
struct in the NFULA_CT attribute.
Better to stick to use nflog_nlmsg_parser(), my suggestion is:
#1 msg_cb() provides struct nfgenmsg *nfmsg, you could retrieve the nlmsg
from there since the nlmsghdr comes before nfgenmsg:
struct nlmsghdr *nlh;
nlh = (struct nlmsghdr *)((void *)nfg - sizeof(*nlh));
err = nflog_nlmsg_parse(nlh, attrs);
if (err < 0)
... error path
#2 once you have access to attrs[NFULA_CT], from there on:
struct nf_conntrack *ct;
ct = nfct_new();
if (!ct)
... error path
err = nfct_nlmsg_parse(nlh, ct);
if (err < 0)
... error path
Then, you get the pointer to conntrack object.
next prev parent reply other threads:[~2021-08-19 10:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-15 14:23 ulogd packet based logging with CT info Blažej Krajňák
2021-08-15 14:31 ` Pablo Neira Ayuso
2021-08-15 16:23 ` Blažej Krajňák
2021-08-17 14:42 ` Blažej Krajňák
2021-08-17 15:05 ` Fatih USTA
2021-08-17 15:06 ` Blažej Krajňák
2021-08-18 7:22 ` Pablo Neira Ayuso
2021-08-18 10:06 ` Blažej Krajňák
2021-08-18 11:52 ` Pablo Neira Ayuso
2021-08-18 20:06 ` Blažej Krajňák
2021-08-19 10:16 ` Pablo Neira Ayuso [this message]
2021-08-19 14:05 ` Blažej Krajňák
2021-08-19 17:03 ` Pablo Neira Ayuso
[not found] ` <CAMEa=f=wHTwJX6CjgOROcStTgDo-TdU6jb2xtpmNi=coHuPboA@mail.gmail.com>
2021-08-21 13:03 ` Blažej Krajňák
2021-08-21 16:21 ` Blažej Krajňák
2021-09-02 22:28 ` Ken-ichirou MATSUZAWA
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=20210819101628.GA2036@salvia \
--to=pablo@netfilter.org \
--cc=blazej.krajnak@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