From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Ben Young <innrevival@gmail.com>, netfilter@vger.kernel.org
Subject: Re: conntrack-tools and kernel 2.6.22
Date: Tue, 27 Nov 2007 15:09:07 +0100 [thread overview]
Message-ID: <474C2503.6000102@trash.net> (raw)
In-Reply-To: <474C1DA5.6010900@netfilter.org>
Pablo Neira Ayuso wrote:
> Ben Young wrote:
>> I have been working on switching some systems over to kernel version
>> 2.6.22. In the transition, conntrack-tools has stopped working on
>> these systems. Depending on which commands I issue to conntrack, I
>> get one of the two errors below, neither of which is particularly
>> helpful in diagnosing the problem.
>>
>> Operation failed: Can't open handler
>> Operation failed: sorry, you must be root or get CAP_NET_ADMIN
>> capability to do this
>>
>> Does anyone know why conntrack wouldn't work on kernel 2.6.22 when it
>> works just fine when I'm running 2.6.17 or 2.6.18? Or have any
>> suggestions for how to go about determining the root cause of this
>> issue?
>>
>> FYI, I am currently using these versions of the conntrack tools:
>>
>> libnetfilter_conntrack: 0.0.81
>> libnfnetlink: 0.0.30
>> conntrack: 1.00beta2
> ^^^
> This is an old version of the conntrack userspace commandline tool, get
> conntrack-tools 0.9.5 that contains conntrack and conntrackd.
>
> http://people.netfilter.org/pablo/conntrack-tools/
Why doesn't it work on current kernels? Things shouldn't break
when updating the kernel.
next prev parent reply other threads:[~2007-11-27 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 20:04 conntrack-tools and kernel 2.6.22 Ben Young
2007-11-27 13:37 ` Pablo Neira Ayuso
2007-11-27 14:09 ` Patrick McHardy [this message]
2007-11-27 14:47 ` Pablo Neira Ayuso
2007-11-27 14:44 ` Patrick McHardy
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=474C2503.6000102@trash.net \
--to=kaber@trash.net \
--cc=innrevival@gmail.com \
--cc=netfilter@vger.kernel.org \
--cc=pablo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox