no extension found for this protocol

no extension found for this protocol

[Aft nix]

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?

cheers.

-- 
-aft

Re: no extension found for this protocol

[Jan Engelhardt]

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...

Re: no extension found for this protocol

[Aft nix]

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...

Fair enough.

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)

kernel version is also misleading. Its modified with 3.5.0 taken as base.

Please help me out with which information you need to understand the phenomenon.

cheers.


-- 
-aft

Re: no extension found for this protocol

[Jan Engelhardt]

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.

Re: no extension found for this protocol

[Aft nix]

On Mon, Sep 24, 2012 at 7:07 PM, Jan Engelhardt <jengelh@inai.de> wrote:
>
> 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.
$iptables -t mangle -A PREROUTING -p udp --dport 9090 -j OBSF --key
"abc" --enc-type "arc4" --enc
$/usr/local/lib/xtables/libxt_OBSF.so : no "OBSF" extension found for
this protocol.
$iptables v1.4.15: unknown option "--key"



-- 
-aft

Re: no extension found for this protocol

[Jan Engelhardt]

On Monday 2012-09-24 15:14, Aft nix wrote:
>>
>> 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.
>$iptables -t mangle -A PREROUTING -p udp --dport 9090 -j OBSF --key
>"abc" --enc-type "arc4" --enc
>$/usr/local/lib/xtables/libxt_OBSF.so : no "OBSF" extension found for
>this protocol.
>$iptables v1.4.15: unknown option "--key"

(in libxt_OBSF.c): You do not have a _init function that actually
registers obsf_target.

Re: no extension found for this protocol

[Aft nix]

On Mon, Sep 24, 2012 at 7:28 PM, Jan Engelhardt <jengelh@inai.de> wrote:
>
> On Monday 2012-09-24 15:14, Aft nix wrote:
>>>
>>> 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.
>>$iptables -t mangle -A PREROUTING -p udp --dport 9090 -j OBSF --key
>>"abc" --enc-type "arc4" --enc
>>$/usr/local/lib/xtables/libxt_OBSF.so : no "OBSF" extension found for
>>this protocol.
>>$iptables v1.4.15: unknown option "--key"
>
> (in libxt_OBSF.c): You do not have a _init function that actually
> registers obsf_target.

libxt_OBSF.c :

static struct xtables_target obsf_target = {
				.family  = NFPROTO_UNSPEC,
				.name    = "OBSF",
				.version = XTABLES_VERSION,
				.size    = XT_ALIGN(sizeof(struct xt_OBSF_tginfo)),
				.userspacesize = XT_ALIGN(sizeof(struct xt_OBSF_tginfo) -
sizeof(struct xt_obsf_priv *)),
				.help = OBSF_help,
				.print = OBSF_print,
				.save = OBSF_save,
				.x6_options = OBSF_opts,
};

static void __init(void)
{
	xtables_register_target(&obsf_target);
}

I do have a __init function.
-- 
-aft

Re: no extension found for this protocol

[Jan Engelhardt]

On Monday 2012-09-24 15:49, Aft nix wrote:

>On Mon, Sep 24, 2012 at 7:28 PM, Jan Engelhardt <jengelh@inai.de> wrote:
>>
>> On Monday 2012-09-24 15:14, Aft nix wrote:
>>>>
>>>> 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.
>>>$iptables -t mangle -A PREROUTING -p udp --dport 9090 -j OBSF --key
>>>"abc" --enc-type "arc4" --enc
>>>$/usr/local/lib/xtables/libxt_OBSF.so : no "OBSF" extension found for
>>>this protocol.
>>>$iptables v1.4.15: unknown option "--key"
>>
>> (in libxt_OBSF.c): You do not have a _init function that actually
>> registers obsf_target.
>
>libxt_OBSF.c :
>
>static void __init(void)
>{
>	xtables_register_target(&obsf_target);
>}
>
>I do have a __init function.

And that's the problem. I said _init, not __init.