From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Netfilter Developer Mailing List <netfilter-devel@vger.kernel.org>
Subject: Re: xtables does not reconise ipportiphash/ipportnethash sets
Date: Thu, 23 Sep 2010 00:23:47 +0100 [thread overview]
Message-ID: <4C9A9003.7060103@googlemail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1009222226110.30669@obet.zrqbmnf.qr>
> Yes, it seems to be an unfortunate omission in the Kbuild file. A new
> release will be up shortly, since I have already been pointed towards
> 2.6.36 changes.
>
Oh, it's getting worse!
Because I use a custom-built kernel (built from source), every time a
new kernel version is released I go through a little ritual:
Since the 2 kmod-* and xtabbles-addons rpms do not recognise the
custom-built string after the kernel version - they moan (see the rpm
-post and -pre scripts to know what I mean), so I have to build xtables
from source. So, once I've compiled and installed my custom-built kernel
I do the same thing with the xtables addons because of the above
shortcoming.
As soon as the last kernel version was released (7-56 I think) I did
compile xtables and installed it properly (though I did not notice the
absence of these two ipsets). That was, by memory, last week.
A few days ago, I reinstalled a patched version of iptables (you know
that, don't you!) so that I get to see the secmarks in their full glory.
Earlier today, after I found out about the absence of the above two
modules, I decided to do 'make clean' on the whole xtables source
directory and compile it from scratch in the hope to trace back what is
wrong.
Guess what? I cannot compile xtables now. I am getting the following error:
CC libxt_CHAOS.oo
libxt_CHAOS.c:99: warning: implicit declaration of function ‘ALIGN’
libxt_CHAOS.c:99: error: initializer element is not constant
libxt_CHAOS.c:99: error: (near initialization for ‘chaos_tg_reg.size’)
libxt_CHAOS.c:100: error: initializer element is not constant
libxt_CHAOS.c:100: error: (near initialization for
‘chaos_tg_reg.userspacesize’)
make[3]: *** [libxt_CHAOS.oo] Error 1
I don't need to mention that I've never had this error before. At first
I thought it is Tom's patch which caused this (thanks, Tom!), so I did
download the iptables source and compiled it without the patch using
rpmbuld -bb etc, then installed it. Nope! Same error.
What I will try in the next half an hour or so is to install the rpm
which comes with F13 repos to see if that makes any difference because
if it doesn't I am stuck. If it does work that means the rpm built with
rpmbuild -bb from source is somewhat different from the one coming out
of FC13 repos, which, to me, is rather odd!
Will post again when I know the outcome.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-09-22 23:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 19:19 xtables does not reconise ipportiphash/ipportnethash sets Mr Dash Four
2010-09-22 20:27 ` Jan Engelhardt
2010-09-22 23:23 ` Mr Dash Four [this message]
2010-09-23 0:03 ` Mr Dash Four
2010-09-23 0:18 ` Jan Engelhardt
2010-09-23 0:30 ` Mr Dash Four
2010-09-23 0:55 ` Jan Engelhardt
2010-09-23 1:01 ` Mr Dash Four
2010-09-23 10:28 ` Jan Engelhardt
2010-09-23 10:48 ` Mr Dash Four
2010-09-23 10:57 ` Jan Engelhardt
2010-09-23 11:21 ` Mr Dash Four
2010-09-23 12:16 ` Jan Engelhardt
2010-09-23 12:21 ` Mr Dash Four
2010-09-23 12:24 ` Jan Engelhardt
2010-09-23 12:31 ` Mr Dash Four
2010-09-23 12:49 ` Mr Dash Four
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=4C9A9003.7060103@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=jengelh@medozas.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).