All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Blažej Krajňák" <blazej.krajnak@gmail.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter@vger.kernel.org
Subject: Re: ulogd packet based logging with CT info
Date: Tue, 17 Aug 2021 16:42:12 +0200	[thread overview]
Message-ID: <CAMEa=f=nzCzM-9a5B0VEkjN5zXgCTqobGe-sgN2K0G_5QgjdAQ@mail.gmail.com> (raw)
In-Reply-To: <CAMEa=fkU4sJjtPHkJ-ZvPOUtnZtOUJmfSqMy+Q4CKf4Lqdde4Q@mail.gmail.com>

Hello Pablo,

I'm just rewriting input plugin ulog_inppkt_NFLOG.c to include
conntrack params. I successfully included CT flags from enum
ip_conntrack_status (assured, reply seen, ...) and CT state and
direction from NFULA_CT_INFO.

However, in NFULA_CT few counters from enum nf_conntrack_attr are
still 0 value. For ex. ATTR_TIMESTAMP_START / STOP and
ATTR_ORIG/REPL_COUNTER_PACKETS/BYTES.
Is it normal, or am I missing some bug at parsing?

ne 15. 8. 2021 o 18:23 Blažej Krajňák <blazej.krajnak@gmail.com> napísal(a):
>
> ne 15. 8. 2021 o 16:31 Pablo Neira Ayuso <pablo@netfilter.org> wrote
> >
> > From the example ulogd2 configuration file in the tree:
> >
> > http://git.netfilter.org/ulogd2/tree/ulogd.conf.in#n77
> >
> > # this is a stack for flow-based logging via XML
> > #stack=ct1:NFCT,xml1:XML
>
> At first, thank you for fast response. Of course I saw this example,
> but I have situation, where I need to know packet details (pktlen,
> mac, ifindex) along with information of conntrack entry which this
> packet triggered.
> I modified one of the libnetfilter_log example utilities to print both
> (packet and conntrack) information together.
> https://drive.google.com/file/d/1wx_LAjH57czHyFwTBSUvSnOkMchWEiiq/view?usp=sharing
>
> Is there any way to do the same in ulogd?

  reply	other threads:[~2021-08-17 14:42 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 [this message]
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
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='CAMEa=f=nzCzM-9a5B0VEkjN5zXgCTqobGe-sgN2K0G_5QgjdAQ@mail.gmail.com' \
    --to=blazej.krajnak@gmail.com \
    --cc=netfilter@vger.kernel.org \
    --cc=pablo@netfilter.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.