From: Jan Engelhardt <jengelh@inai.de>
To: Aft nix <aftnix@gmail.com>
Cc: Netfilter Developer Mailing List <netfilter-devel@vger.kernel.org>
Subject: Re: no extension found for this protocol
Date: Mon, 24 Sep 2012 15:07:51 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.01.1209241506300.17187@nerf07.vanv.qr> (raw)
In-Reply-To: <CAGuaRCu2tFRhg2euL7UFKQmHzKAUFpZ90aa2nOs7niGeKJaMqg@mail.gmail.com>
On Monday 2012-09-24 15:03, Aft nix wrote:
>On Mon, Sep 24, 2012 at 6:32 PM, Jan Engelhardt <jengelh@inai.de> wrote:
>> On Monday 2012-09-24 13:12, Aft nix wrote:
>>
>>>Hi,
>>>
>>>I've added a target extension. The kernel module(xt_*.ko) and the
>>>userspace plugin(libxt_*.so) are there. But when
>>>i try to invoke the rule, it gives me "No extension found for this protocol".
>>>
>>>What am i doing wrong here?
>>
>> You forgot to FedEx a magic glass sphere to me...
>
>But i'm confused which debug information is useful here. Both *.ko and
>*.so files are in place. iptables --version states 1.4.15(Actually the
>libxt_*.c is included "in tree". i've just checked out v1.4.15 tag
>from git tree and added libxt_*.c and xt_*.h)
>
>Please help me out with which information you need to understand the
>phenomenon.
Specify the command you ran, and the _exact_ error message. There is
no "No extension found for this protocol" string anywhere in the code
to spot.
next prev parent reply other threads:[~2012-09-24 13:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 11:12 no extension found for this protocol Aft nix
2012-09-24 12:32 ` Jan Engelhardt
2012-09-24 13:03 ` Aft nix
2012-09-24 13:07 ` Jan Engelhardt [this message]
2012-09-24 13:14 ` Aft nix
2012-09-24 13:28 ` Jan Engelhardt
2012-09-24 13:49 ` Aft nix
2012-09-24 14:03 ` 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=alpine.LNX.2.01.1209241506300.17187@nerf07.vanv.qr \
--to=jengelh@inai.de \
--cc=aftnix@gmail.com \
--cc=netfilter-devel@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).