From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Marek Kierdelewicz <marek@piasta.pl>,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: xtables-addons - problem including nf_nat.h in userspace plugin
Date: Mon, 22 Nov 2010 16:11:37 +0100 [thread overview]
Message-ID: <4CEA8829.1080106@trash.net> (raw)
In-Reply-To: <alpine.LNX.2.01.1011221447001.18089@obet.zrqbmnf.qr>
On 22.11.2010 14:52, Jan Engelhardt wrote:
>
> On Sunday 2010-11-21 22:47, Marek Kierdelewicz wrote:
>>
>> I'm writing a new netfilter module and I'm using xtables-addons[...]
>> Iptables userspace plugin for the module needs definition of "struct
>> nf_nat_multi_range", so I added following line to libxt_xxxx.c:
>> #include <net/netfilter/nf_nat.h>
>> Unfortunately I get following message during make:
>> warning: net/netfilter/nf_nat.h: No such file or directory
>> ... and compilation fails.
>> I was able to make it work by copying nf_nat.h and nf_conntrack_tuple.h
>> to extension directory in xtables-addons tree and by modifying include
>> in libxt_xxxx.c to "nf_nat.h", but this doesn't seem to be the proper
>> way of doing things.
>
> Well, iptables also copies them rather than properly relying on
> something from <linux/*>. Yes, it's not proper. Patrick should know
> the details about the what and why.
Mainly to allow to compile new extensions before the kernel headers
are updated. Including files from include/net is wrong though, they
should be moved to include/linux instead.
next prev parent reply other threads:[~2010-11-22 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-21 21:47 xtables-addons - problem including nf_nat.h in userspace plugin Marek Kierdelewicz
2010-11-22 13:52 ` Jan Engelhardt
2010-11-22 15:11 ` Patrick McHardy [this message]
2010-11-22 21:52 ` Marek Kierdelewicz
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=4CEA8829.1080106@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--cc=marek@piasta.pl \
--cc=netfilter-devel@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.