From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>, netfilter@vger.kernel.org
Subject: Re: [ANNOUNCE] ipset 6.5 released
Date: Sat, 21 May 2011 22:51:29 +0100 [thread overview]
Message-ID: <4DD833E1.8050507@googlemail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1105212331570.16146@frira.zrqbmnf.qr>
> Nevertheless, I would recommend to mr-4 to have a ipset and libmnl
> compiled with debug info, point to it via LD_LIBRARY_PATH, and then feed
> it through valgrind with the same input. That may give some more
> insight.
>
Oh, by the way, forgot to add this - there is a bug in xtables-addon I
ran into while I was dealing with all this - if I have ipv6 compiled as
a *module* when I try to install xtables-addons (via kickstart) I get
these errors:
WARNING:
/lib/modules/2.6.35.13-91.fc13.i686/extra/xtables-addons/xt_RAWNAT.ko
needs unknown symbol ipv6_find_hdr
WARNING:
/lib/modules/2.6.35.13-91.fc13.i686/extra/xtables-addons/xt_SYSRQ.ko
needs unknown symbol ipv6_find_hdr
WARNING:
/lib/modules/2.6.35.13-91.fc13.i686/extra/xtables-addons/ip6table_rawpost.ko
needs unknown symbol ip6t_unregister_table
I managed to fix the "ip6table_rawpost.ko" error - the problem was with
the extensions/Kbuild file - it needed another "ifneq
(${CONFIG_IPV6_MODULE},)" "endif" block after "ifneq (${CONFIG_IPV6},)".
I saw in xt_RAWNAT.c that there is preprocessor directive which was like
"#if defined(CONFIG_IPV6) || defined(CONFIG_IPV6_MODULE)" to separate
the ipv6 code from the "normal" one, but it didn't work properly for
some reason. When I forcefully removed the ipv6 code blocks from both
xt_RAWNAT.c and xt_SYSRQ.c everything was fine, so I think you need to
look at this!
next prev parent reply other threads:[~2011-05-21 21:51 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-15 13:50 [ANNOUNCE] ipset 6.5 released Jozsef Kadlecsik
2011-05-16 15:41 ` Mr Dash Four
2011-05-17 7:42 ` Jozsef Kadlecsik
2011-05-17 11:03 ` Mr Dash Four
2011-05-17 11:51 ` Jozsef Kadlecsik
2011-05-17 15:23 ` Mr Dash Four
2011-05-17 18:36 ` Mr Dash Four
2011-05-18 7:54 ` Jozsef Kadlecsik
2011-05-18 10:59 ` Mr Dash Four
2011-05-18 11:22 ` Jozsef Kadlecsik
2011-05-21 19:42 ` Mr Dash Four
2011-05-21 19:45 ` Jozsef Kadlecsik
2011-05-21 19:58 ` Jozsef Kadlecsik
2011-05-21 20:11 ` Mr Dash Four
2011-05-21 21:31 ` Jozsef Kadlecsik
2011-05-21 21:33 ` Jan Engelhardt
2011-05-21 21:41 ` Mr Dash Four
2011-05-21 21:52 ` Jan Engelhardt
2011-05-21 23:08 ` Jozsef Kadlecsik
2011-05-22 1:01 ` Mr Dash Four
2011-05-22 10:05 ` Jozsef Kadlecsik
2011-05-22 10:36 ` Jozsef Kadlecsik
2011-05-22 11:44 ` Mr Dash Four
2011-05-22 11:44 ` Mr Dash Four
2011-05-22 21:21 ` Jozsef Kadlecsik
2011-05-22 21:32 ` Mr Dash Four
2011-05-22 15:00 ` Jan Engelhardt
2011-05-22 13:57 ` Mr Dash Four
2011-05-22 14:05 ` Mr Dash Four
2011-05-21 21:51 ` Mr Dash Four [this message]
2011-05-21 21:41 ` Mr Dash Four
2011-05-21 22:28 ` Jozsef Kadlecsik
2011-05-21 22:41 ` Jozsef Kadlecsik
2011-05-21 22:44 ` Mr Dash Four
2011-05-21 22:42 ` Mr Dash Four
2011-05-22 14:52 ` Mr Dash Four
2011-05-21 22:15 ` Mr Dash Four
2011-05-21 22:31 ` Jozsef Kadlecsik
2011-05-21 22:42 ` Mr Dash Four
2011-05-21 22:49 ` Jozsef Kadlecsik
2011-05-21 22:57 ` Mr Dash Four
2011-05-21 23:25 ` Jozsef Kadlecsik
2011-05-21 23:33 ` Mr Dash Four
2011-05-22 9:56 ` Jozsef Kadlecsik
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=4DD833E1.8050507@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=jengelh@medozas.de \
--cc=kadlec@blackhole.kfki.hu \
--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.