From: Akshat Kakkar <akshat.1984@gmail.com>
To: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: Ipset Error : ipset v6.25.1: Kernel error received: set type not supported (on Kernel 4.1.4)
Date: Tue, 11 Aug 2015 12:02:59 +0530 [thread overview]
Message-ID: <CAA5aLPjJsA0Lc+wLjHTk3Bj4vtnLAOzfbVBvpsquMZTcA+hBpA@mail.gmail.com> (raw)
In-Reply-To: <CAA5aLPh-_ySu=PFqkyyG+AzTWQo_cUc35ZcnH3W5ojQPeJeG4g@mail.gmail.com>
o/p of ipset help
is
ipset v6.25.1
Usage: ipset [options] COMMAND
Commands:
create SETNAME TYPENAME [type-specific-options]
Create a new set
add SETNAME ENTRY
Add entry to the named set
del SETNAME ENTRY
Delete entry from the named set
test SETNAME ENTRY
Test entry in the named set
destroy [SETNAME]
Destroy a named set or all sets
list [SETNAME]
List the entries of a named set or all sets
save [SETNAME]
Save the named set or all sets to stdout
restore
Restore a saved state
flush [SETNAME]
Flush a named set or all sets
rename FROM-SETNAME TO-SETNAME
Rename two sets
swap FROM-SETNAME TO-SETNAME
Swap the contect of two existing sets
help [TYPENAME]
Print help, and settype specific help
version
Print version information
quit
Quit interactive mode
Options:
-o plain|save|xml
Specify output mode for listing sets.
Default value for "list" command is mode "plain"
and for "save" command is mode "save".
-s
Print elements sorted (if supported by the set type).
-q
Suppress any notice or warning message.
-r
Try to resolve IP addresses in the output (slow!)
-!
Ignore errors when creating or adding sets or
elements that do exist or when deleting elements
that don't exist.
-n
When listing, just list setnames from the kernel.
-t
When listing, list setnames and set headers
from kernel only.
-f
Read from the given file instead of standard
input (restore) or write to given file instead
of standard output (list/save).
Supported set types:
list:set 3 skbinfo support
list:set 2 comment support
list:set 1 counters support
list:set 0 Initial revision
hash:mac 0 Initial revision
hash:net,iface 6 skbinfo support
hash:net,iface 5 forceadd support
hash:net,iface 4 comment support
hash:net,iface 3 counters support
hash:net,iface 2 /0 network support
hash:net,iface 1 nomatch flag support
hash:net,iface 0 Initial revision
hash:net,port 7 skbinfo support
hash:net,port 6 forceadd support
hash:net,port 5 comment support
hash:net,port 4 counters support
hash:net,port 3 nomatch flag support
hash:net,port 2 Add/del range support
hash:net,port 1 SCTP and UDPLITE support
hash:net,port,net 2 skbinfo support
hash:net,port,net 1 forceadd support
hash:net,port,net 0 initial revision
hash:net,net 2 skbinfo support
hash:net,net 1 forceadd support
hash:net,net 0 initial revision
hash:net 6 skbinfo support
hash:net 5 forceadd support
hash:net 4 comment support
hash:net 3 counters support
hash:net 2 nomatch flag support
hash:net 1 Add/del range support
hash:net 0 Initial revision
hash:ip,port,net 7 skbinfo support
hash:ip,port,net 6 forceadd support
hash:ip,port,net 5 comment support
hash:ip,port,net 4 counters support
hash:ip,port,net 3 nomatch flag support
hash:ip,port,net 2 Add/del range support
hash:ip,port,net 1 SCTP and UDPLITE support
hash:ip,port,ip 5 skbinfo support
hash:ip,port,ip 4 forceadd support
hash:ip,port,ip 3 comment support
hash:ip,port,ip 2 counters support
hash:ip,port,ip 1 SCTP and UDPLITE support
hash:ip,mark 2 sbkinfo support
hash:ip,mark 1 forceadd support
hash:ip,mark 0 initial revision
hash:ip,port 5 skbinfo support
hash:ip,port 4 forceadd support
hash:ip,port 3 comment support
hash:ip,port 2 counters support
hash:ip,port 1 SCTP and UDPLITE support
hash:ip 4 skbinfo support
hash:ip 3 forceadd support
hash:ip 2 comment support
hash:ip 1 counters support
hash:ip 0 Initial revision
bitmap:port 3 skbinfo support
bitmap:port 2 comment support
bitmap:port 1 counters support
bitmap:port 0 Initial revision
bitmap:ip,mac 3 skbinfo support
bitmap:ip,mac 2 comment support
bitmap:ip,mac 1 counters support
bitmap:ip,mac 0 Initial revision
bitmap:ip 3 skbinfo support
bitmap:ip 2 comment support
bitmap:ip 1 counters support
bitmap:ip 0 Initial revision
On Tue, Aug 11, 2015 at 12:01 PM, Akshat Kakkar <akshat.1984@gmail.com> wrote:
> Hi!
> I am running sl6.3 (i.e. kernel 2.6.32-279). I upgraded the kernel
> using elrepo to kernel 4.1.4.
> Then I downloaded ipset 6.25.
> I executed follwing commands
> ./autogen.sh
> ./configure
> make
> make modules
> make install
> make modules_install
>
> No error is generated at any step
>
> Now when I want to creat an uipset using command
> ipset -N foo hash:ip
>
> I get error
> ""
> ipset v6.25.1: Kernel error received: set type not supported
> ""
>
> output of uname -r
>
> 4.1.4-1.el6.elrepo.x86_64
>
>
>
>
> o/p of " find /lib/modules/4.1.4-1.el6.elrepo.x86_64 -name ip_set.ko"
>
> /lib/modules/4.1.4-1.el6.elrepo.x86_64/extra/netfilter/ipset/ip_set.ko
> /lib/modules/4.1.4-1.el6.elrepo.x86_64/kernel/net/netfilter/ipset/ip_set.ko
>
>
>
> o/p of "find /lib/modules -name ip_set.ko"
>
> /lib/modules/2.6.32-279.el6.x86_64/extra/ip_set.ko
> /lib/modules/2.6.32-279.el6.x86_64/kernel/net/netfilter/ipset/ip_set.ko
> /lib/modules/4.1.4-1.el6.elrepo.x86_64/extra/netfilter/ipset/ip_set.ko
> /lib/modules/4.1.4-1.el6.elrepo.x86_64/kernel/net/netfilter/ipset/ip_set.ko
>
>
> please help....
next prev parent reply other threads:[~2015-08-11 6:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 6:31 Ipset Error : ipset v6.25.1: Kernel error received: set type not supported (on Kernel 4.1.4) Akshat Kakkar
2015-08-11 6:32 ` Akshat Kakkar [this message]
2015-08-11 6:49 ` Akshat Kakkar
2015-08-11 10:13 ` Jozsef Kadlecsik
[not found] ` <CAA5aLPj7LA3bN4NBCTvQ=FjDMy-8GZqh9nWk3groyMYOj5nQUQ@mail.gmail.com>
[not found] ` <alpine.DEB.2.10.1508111320400.9289@blackhole.kfki.hu>
[not found] ` <CAA5aLPhO7643BnLNNe4Kp+h6Nivvn_jtgVdRXBfWGPPPLf_kXA@mail.gmail.com>
[not found] ` <alpine.DEB.2.10.1508111416010.9289@blackhole.kfki.hu>
[not found] ` <CAA5aLPiNcE51=3UYfuRa8U_ueq6U7cJJPR0Tyd2cqH143vd9wg@mail.gmail.com>
2015-08-11 13:46 ` Akshat Kakkar
2015-08-12 6:50 ` Akshat Kakkar
2015-08-12 9:26 ` Jozsef Kadlecsik
2015-08-12 9:43 ` Akshat Kakkar
2015-08-12 9:48 ` Jozsef Kadlecsik
[not found] ` <CAA5aLPg2xNZMw2xRirj5pBnEort-K4sHesYfnVL+CD9D2V97jQ@mail.gmail.com>
[not found] ` <alpine.DEB.2.10.1508121210280.15443@blackhole.kfki.hu>
2015-08-12 10:42 ` Akshat Kakkar
2015-08-14 7:34 ` Akshat Kakkar
2015-08-14 8:32 ` Jozsef Kadlecsik
2015-08-17 20:08 ` Jozsef Kadlecsik
2015-08-17 22:27 ` Jozsef Kadlecsik
2015-08-18 7:16 ` Akshat Kakkar
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=CAA5aLPjJsA0Lc+wLjHTk3Bj4vtnLAOzfbVBvpsquMZTcA+hBpA@mail.gmail.com \
--to=akshat.1984@gmail.com \
--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).