netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rob Sterenborg (lists)" <lists@sterenborg.info>
To: netfilter-devel@vger.kernel.org, netfilter@vger.kernel.org
Subject: Re: [ANNOUNCE] ipset-5.0 released
Date: Tue, 21 Dec 2010 12:14:14 +0100	[thread overview]
Message-ID: <1292930054.3313.15.camel@ns014530.dcyb.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1012181149560.11002@blackhole.kfki.hu>

On Sat, 2010-12-18 at 12:13 +0100, Jozsef Kadlecsik wrote:

Hi Jozsef,

> > When running 'configure' I got this error:
> > 
> > ./configure: line 11510: syntax error near unexpected token `[libmnl],'
> > ./configure: line 11510: `PKG_CHECK_MODULES([libmnl], [libmnl >= 1])'
> > 
> > CentOS' pkg-config is installed, so, for reference: I copied
> > '/usr/share/aclocal/pkg.m4' into the 'm4' directory, ran 'autogen.sh'
> > again and after that 'configure' had no problems.
> 
> Autoconf has its own pitfalls... I can't reproduce it so I added
> 'aclocal -I m4' to autogen.sh. After checking out the git tree, could you 
> give it a try whether it solves the issue?

Call me stupid, but I couldn't figure out how to download the git branch
using git (when I did, I downloaded the 4.5 tree), but I did see it on
the web inferface. I downloaded today's snapshot from the git-5 branch;
I hope that's the same. I still get the same error however.

I've resolved the other issues I had: I should have thought of
installing the accompanying kernel header files.

> > Finally, when trying the new ipset it seems that except for 'version',
> > every command I tried returns 'Invalid argument':
> > 
> > (Yes I know this is incorrect syntax, but now I know it's trying to do
> > something besides giving me 'Invalid argument'.)
> > # ipset create TEST hash   
> > ipset v5.0: Syntax error: typename 'hash' is unkown
> > 
> > (As per ipset.8 example.)
> > # ipset create foo bitmap:ip range 192.168.0.0/16
> > ipset v5.0: Kernel error received: Invalid argument
> > 
> > # ipset list               
> > ipset v5.0: Kernel error received: Invalid argument
> > 
> > # lsmod|grep set
> > ip_set                 16790  0 
> > nfnetlink               3179  2 ip_set,nf_conntrack_netlink
> > 
> > So, I guess something must have gone wrong when compiling ipset anyhow.
> 
> Please read the README file: you must patch your kernel source with 
> netlink.patch, compile and install it. Otherwise the new nfnetlink id 
> won't handled by the kernel and thus ipset can't work.

I did this. The patch succeeded and compilation went, except for pkg.m4
which is easily resolved, without errors that I can see. I still get the
above results however.

> Thanks for tests and the reporting!

NP. Thank you..


Rob



  parent reply	other threads:[~2010-12-21 11:14 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-17 22:26 [ANNOUNCE] ipset-5.0 released Jozsef Kadlecsik
2010-12-17 23:32 ` Jan Engelhardt
2010-12-18 10:40   ` Jozsef Kadlecsik
2010-12-18  7:29 ` Rob Sterenborg (lists)
2010-12-18 11:13   ` Jozsef Kadlecsik
2010-12-18 15:43     ` Jan Engelhardt
2010-12-18 19:50       ` Jozsef Kadlecsik
2010-12-18 21:49         ` Jan Engelhardt
2010-12-19  0:05           ` Jozsef Kadlecsik
2010-12-19  0:28             ` Jan Engelhardt
2010-12-19  5:56           ` Jan Engelhardt
2010-12-19 18:23     ` Rob Sterenborg (lists)
2010-12-21 11:14     ` Rob Sterenborg (lists) [this message]
2010-12-21 14:03       ` Jozsef Kadlecsik
2010-12-18 14:22 ` Mr Dash Four
2010-12-18 20:23   ` Jozsef Kadlecsik
2010-12-18 21:51     ` Mr Dash Four
2010-12-18 22:10       ` Jan Engelhardt
2010-12-18 22:23         ` Mr Dash Four
2010-12-19  0:34       ` Jozsef Kadlecsik
2010-12-19 13:52         ` Mr Dash Four
2010-12-19 15:20           ` Dennis Jacobfeuerborn
2010-12-19 17:04             ` Mr Dash Four
2010-12-22 10:59               ` Jozsef Kadlecsik
2010-12-22 12:48                 ` Mr Dash Four
2010-12-23 15:39                   ` Jozsef Kadlecsik
2010-12-23 17:50                     ` Mr Dash Four
2010-12-23 17:55                       ` David Miller
2010-12-23 18:00                         ` Mr Dash Four
2010-12-23 18:06                           ` David Miller
2010-12-23 18:10                             ` Mr Dash Four
2010-12-23 19:35                       ` Jozsef Kadlecsik
2010-12-23 22:23                         ` Mr Dash Four
2010-12-23 22:46                           ` Jozsef Kadlecsik
2010-12-23 22:56                             ` Jozsef Kadlecsik
2010-12-23 23:06                               ` Mr Dash Four
2010-12-26 10:30                                 ` Jozsef Kadlecsik
2010-12-26 13:47                                   ` Mr Dash Four
2010-12-26 20:09                                     ` Jozsef Kadlecsik
2010-12-26 21:44                                       ` Mr Dash Four
2010-12-27 14:49                                         ` Jozsef Kadlecsik
2010-12-27 16:23                                           ` Mr Dash Four
2010-12-27 18:20                                             ` Jozsef Kadlecsik
2010-12-27 18:52                                               ` Mr Dash Four
2010-12-28 19:26                                                 ` Jozsef Kadlecsik
2010-12-23 23:03                             ` Mr Dash Four
2010-12-26 10:32                               ` Jozsef Kadlecsik
2010-12-23 21:51                       ` 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=1292930054.3313.15.camel@ns014530.dcyb.net \
    --to=lists@sterenborg.info \
    --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).