Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Vieri Di Paola <vieridipaola@gmail.com>
Cc: Florian Westphal <fw@strlen.de>, netfilter@vger.kernel.org
Subject: Re: NFQUEUE/iptables and kernel warning messages for net/ipv4/tcp_output.c
Date: Tue, 18 Feb 2020 14:21:07 +0100	[thread overview]
Message-ID: <20200218132107.GK19559@breakpoint.cc> (raw)
In-Reply-To: <CABLYT9j6a+QT=7BdeSbJY2AnbHhKz72OQTJ8x5nL6_4TBeZT3Q@mail.gmail.com>

Vieri Di Paola <vieridipaola@gmail.com> wrote:
> On Tue, Feb 18, 2020 at 1:39 PM Florian Westphal <fw@strlen.de> wrote:
> >
> > get this patch working (untested)
> 
> > +static uint32_t nfq_get_pktinfo(struct nfq_data *nfad)
> > +{
> > +        return ntohl(nfnl_get_data(nfad->data, NFQA_SKB_INFO, uint32_t));
> 
> I applied the patch, but I get this compilation error:
> 
> In file included from suricata-common.h:180,
>                  from source-nfq.c:28:
> source-nfq.c: In function 'nfq_get_pktinfo':
> source-nfq.c:404:48: error: 'NFQA_SKB_INFO' undeclared (first use in
> this function)
>   404 |         return ntohl(nfnl_get_data(nfad->data, NFQA_SKB_INFO,
> uint32_t));
>       |                                                ^~~~~~~~~~~~~

This means your kernel headers are older than 3.10.
It should be part of /usr/include/linux/netfilter/nfnetlink_queue.h .


You can substitute 14 instead, or add

#define NFQA_SKB_INFO 14

> I'll post to the suricata ML asap.

Thanks.

  reply	other threads:[~2020-02-18 13:21 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 [this message]
2020-02-19 19:37       ` Vieri Di Paola

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=20200218132107.GK19559@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=netfilter@vger.kernel.org \
    --cc=vieridipaola@gmail.com \
    /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