From: Patrick McHardy <kaber@trash.net>
To: "S. Sakar" <serkan.sakar@gmx.net>
Cc: netfilter@vger.kernel.org,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: nfq_unbind_pf() fails with kernel 2.6.23
Date: Thu, 11 Oct 2007 10:27:30 +0200 [thread overview]
Message-ID: <470DDE72.507@trash.net> (raw)
In-Reply-To: <470DBFB0.1090600@gmx.net>
S. Sakar wrote:
> hi,
> I don't seem to be able to run the nfqnl_test code with kernel 2.6.23
> (amd64).
> It prints the following:
>
>> opening library handle
>> unbinding existing nf_queue handler for AF_INET (if any)
>> NFNETLINK answers: Invalid argument
>> error during nfq_unbind_pf()
Yeah, we've added a check to prohibit unregistering other handlers.
The entire unregistration stuff is a horrible hack, the only reason
why it (still) exists is because registration of the same handler
returns EEXIST instead of silently ignoring it. The best fix for
now is to ignore the return value of nfq_unbind_pf().
next prev parent reply other threads:[~2007-10-11 8:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 6:16 nfq_unbind_pf() fails with kernel 2.6.23 S. Sakar
2007-10-11 8:27 ` Patrick McHardy [this message]
2007-10-11 9:54 ` S. Sakar
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=470DDE72.507@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=netfilter@vger.kernel.org \
--cc=serkan.sakar@gmx.net \
/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