On Mon, Sep 24, 2012 at 7:07 PM, Jan Engelhardt <jengelh@xxxxxxx> wrote: > > On Monday 2012-09-24 15:03, Aft nix wrote: >>On Mon, Sep 24, 2012 at 6:32 PM, Jan Engelhardt <jengelh@xxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
