From: Mark Moseley <moseleymark@gmail.com>
To: "netfilter@lists.netfilter.org" <netfilter@lists.netfilter.org>
Subject: ipset issue
Date: Mon, 6 Dec 2004 13:27:34 -0800 [thread overview]
Message-ID: <294d5daa0412061327651c1648@mail.gmail.com> (raw)
I decided to play with ipset (2.0), but I seem to be running into an
issue with creating rules. I wonder if I'm missing something silly or
not.
When I issue the command:
ipset -N foo iphash --resize 0 (straight from the Tips page)
I get the error:
ipset v2.0: Error from kernel: Protocol not available
I get this on a box running a 2.6.10-rc3 kernel and the kernel has
most definitely been patched with the POM with the set stuff in it, as
well as the iptables 1.3.0 (POM and iptables source were downloaded
from the ipset page,
http://people.netfilter.org/kadlec/ipset/install.html). The kernel was
compiled with gcc 3.2.2 (RH9 rpm).
Here's a snippet from the end of strace. Let me know if more
strace'ing would be helpful. This is the last chunk, running strace
with -f and -s:
socket(PF_INET, SOCK_RAW, IPPROTO_RAW) = 3
setsockopt(3, SOL_IP, 0x53 /* IP_??? */,
"\1\0\0\0\2\0\0\0foo\0T\277\4@Xn\4@8\344\3@\350u\1@\4\0\0\0\264x\1@\224\207\4\10iphash\0\10\270i\1@\264m\1@\0\0\0\0\200\364\377\277\\~\0@<\364\377\277\0\4\0\0\10\0\0\0\377\377\377\377",
84) = -1 ENOPROTOOPT (Protocol not available)
write(2, "ipset v2.0: ", 12ipset v2.0: ) = 12
write(2, "Error from kernel: Protocol not available", 41Error from
kernel: Protocol not available) = 41
write(2, "\n", 1) = 1
exit_group(1)
I imagine I'm missing something when I configure the kernel but I'm
not sure what. Anybody know what botched? Thanks!
next reply other threads:[~2004-12-06 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 21:27 Mark Moseley [this message]
2004-12-07 7:22 ` ipset issue 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=294d5daa0412061327651c1648@mail.gmail.com \
--to=moseleymark@gmail.com \
--cc=netfilter@lists.netfilter.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.