All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vieri Di Paola <vieridipaola@gmail.com>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter@vger.kernel.org
Subject: Re: NFQUEUE/iptables and kernel warning messages for net/ipv4/tcp_output.c
Date: Wed, 19 Feb 2020 20:37:47 +0100	[thread overview]
Message-ID: <CABLYT9iGmGJCmaJn5epgtGr+35Z3CMECut=dHjBcKBe5OkeqDQ@mail.gmail.com> (raw)
In-Reply-To: <20200218132107.GK19559@breakpoint.cc>

On Tue, Feb 18, 2020 at 2:21 PM Florian Westphal <fw@strlen.de> wrote:
>
>
> This means your kernel headers are older than 3.10.
> It should be part of /usr/include/linux/netfilter/nfnetlink_queue.h .

Actually I have 4.19. I also had to define another constant.
In any case, it compiled OK, and the problem was not seen again for a
test period of at least 15 hours (I usually had several of these
kernel warnings almost each hour, so 15 hours in a weekday is
significant).
I then removed your patch, recompiled and ran suricata in nfq "accept"
mode (default). It was set as "repeat mode" before. It hasn't been
running long enough yet (7 hours), but for now I haven't seen any
kernel warnings in "accept mode".

So all I can say for now is that it seems I'm getting these kernel
warnings when using Suricata in nfq repeat mode.

I'll ask the Suricata ML what they think about that.

Thanks,

Vieri

      reply	other threads:[~2020-02-19 19:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17 17:30 NFQUEUE/iptables and kernel warning messages for net/ipv4/tcp_output.c Vieri Di Paola
2020-02-18 12:39 ` Florian Westphal
2020-02-18 12:59   ` Vieri Di Paola
2020-02-18 13:21     ` Florian Westphal
2020-02-19 19:37       ` Vieri Di Paola [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='CABLYT9iGmGJCmaJn5epgtGr+35Z3CMECut=dHjBcKBe5OkeqDQ@mail.gmail.com' \
    --to=vieridipaola@gmail.com \
    --cc=fw@strlen.de \
    --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.