From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: ipset-4.4 on 2.6.16.60 kernel
Date: Sat, 06 Nov 2010 22:58:34 +0000 [thread overview]
Message-ID: <4CD5DD9A.8000608@googlemail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1011062230030.31105@blackhole.kfki.hu>
>> =================
>> CC [M] /root/ipset-4.4/kernel/ipt_set.o
>> /root/ipset-4.4/kernel/ipt_set.c: In function `ipt_ipset_init':
>> /root/ipset-4.4/kernel/ipt_set.c:244: warning: implicit declaration of
>> function `ipt_register_match'
>> /root/ipset-4.4/kernel/ipt_set.c: In function `ipt_ipset_fini':
>> /root/ipset-4.4/kernel/ipt_set.c:249: warning: implicit declaration of
>> function `ipt_unregister_match'
>> ================
>>
>
> No, you cannot solve the compatibility that way. Please write back the
> kernel version check to KERNEL_VERSION(2,6,16) and manually modify all
> xt_register_match|target, xt_unregister_match|target calls in ipt_set.c
> and ipt_SET.c speficying two arguments, the first one filled out as
> AF_INET, eg:
>
> static int __init ipt_ipset_init(void)
> {
> return xt_register_match(AF_INET, &set_match);
> }
>
That is exactly what I did, and it compiled without error. After that I
did KERNEL_DIR=... make install and installed the whole thing.
HOWEVER, it still does not work!
After reboot, when I try 'ipset --version' it tells me it does not know
the kernel version, so I looked at /lib/modules/2.6.16.60/ and saw that
in a directory called 'extra' there were all the ipset modules sitting.
So what I did is modprobe all .ko files to load them into the memory.
lsmod confirmed it that they are loaded without errors.
So, hopeful that I finally cracked it I executed 'iptables -I blacklist
1 -m set --match-set test dst -j DROP' (I created the treemap called
'test' prior to that) and got this message:
iptables v1.3.7: Unknown arg `--match-set'
Try `iptables -h' or 'iptables --help' for more information.
Looked in /usr/lib/iptables/ and there are two additional files
libipt_set.so and libipt_SET.so, which were installed by the newly
compiled version of iptables so don't know why it does not work!
next prev parent reply other threads:[~2010-11-06 22:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 21:02 [ANNOUNCE] ipset-4.4 released Jozsef Kadlecsik
2010-11-06 20:19 ` ipset-4.4 on 2.6.16.60 kernel Mr Dash Four
2010-11-06 21:48 ` Jozsef Kadlecsik
2010-11-06 22:58 ` Mr Dash Four [this message]
2010-11-07 0:12 ` [SOLVED] " 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=4CD5DD9A.8000608@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@vger.kernel.org \
--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 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).