From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: "Gabor Z. Papp" <gzp@papp.hu>,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: iptables 1.4.0 and Linux 2.4
Date: Mon, 31 Dec 2007 15:20:21 +0100 [thread overview]
Message-ID: <4778FAA5.3030406@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0712310346070.2093@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Dec 30 2007 11:36, Gabor Z. Papp wrote:
>
>> In file included from include/linux/netfilter/nf_nat.h:4,
>> from extensions/libipt_DNAT.c:9:
>> include/linux/netfilter/nf_conntrack_tuple.h:29: error: syntax error before "__be32"
>>
>
> It is because nf_inet_addr is not known to iptables with your kernel.
>
>
> Question to Patrick: where is netfilter.h in the iptables
> source directory
> gone?
I don't think we ever had one.
next prev parent reply other threads:[~2007-12-31 14:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-30 10:36 iptables 1.4.0 and Linux 2.4 Gabor Z. Papp
2007-12-31 2:48 ` Jan Engelhardt
2007-12-31 14:20 ` Patrick McHardy [this message]
2007-12-31 15:51 ` Jan Engelhardt
2007-12-31 16:09 ` Patrick McHardy
2008-01-01 13:33 ` Jan Engelhardt
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=4778FAA5.3030406@trash.net \
--to=kaber@trash.net \
--cc=gzp@papp.hu \
--cc=jengelh@computergmbh.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).