Thanks Jan! I have added the env variable, but saw no change. My libxt_TAP.so is getting found as it is checking my parameter. I have tried a different xtables_addons target such as TEE, and the rule gets inserted fine. I had SELinux block my libxt_TAP.so and had added it to the SELinux rules, so that shouldn't be a problem. Any other idea what might be going on? I know my module is calling xt_register_targets(), is there a way for me to check the contents of its tables? Thanks for looking at my code! I'll switch my mutex to a spinlock - I'd be wasting a lot of time once I get running with this without your help. Yossi Weihs -----Original Message----- From: Jan Engelhardt [mailto:jengelh@xxxxxxxxxx] Sent: Sunday, August 08, 2010 4:29 PM To: Yossi Weihs Cc: netfilter-devel@xxxxxxxxxxxxxxx Subject: Re: newbie: writing custom target, need help with getting it to work On Sunday 2010-08-08 22:20, Yossi Weihs wrote: >Hi List, > >I have been working on a custom netfilter target to help with some in-house >testing. I?m running Fedora 13 and building within xtables-addons v 1.2.6 ; >I have gotten both the kernel module and library to build correctly within >the xtables-addons build enviroment, and am inserting the kernel module with >no errors. When trying to create a rule with my target, I get the cryptic >error: > >iptables --verbose --table filter --insert INPUT --protocol TCP -m state >--state ESTABLISHED --jump TAP --device TAPPY >TAP tcp opt -- in * out * 0.0.0.0/0 -> 0.0.0.0/0 state ESTABLISHED TAP >dev:TAPPY >iptables: No chain/target/match by that name. When you want iptables to recognize (the user portion) of Xt-a's extra modules, you need to point to it via the XTABLES_LIBDIR environment variable. XTABLES_LIBDIR=$HOME/xta/extensions:/usr/lib(64)/xtables iptables -S Don't forget usr/lib/xtables otherwise it won't find the tcp match and all the ones that already ship with iptables. -- 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
