hi,
im having a problem using ettercap on slackware 11, when i run:
ettercap -T -M arp:remote -i ath0 -q /host/ /router/

and after that i start the check poisoning plugin (chk_poison)
it gives me

chk_poison: Checking poisoning status...

ERROR : 1, Operation not permitted
[ec_send.c:send_L3_icmp_echo:513]

libnet_write (-1): libnet_write_raw_ipv4(): -1 bytes written (Operation not permitted)


iptables v1.3.5: can't initialize iptables table `nat': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.3.5: can't initialize iptables table `nat': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.3.5: can't initialize iptables table `nat': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.3.5: can't initialize iptables table `nat': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.3.5: can't initialize iptables table `nat': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.3.5: can't initialize iptables table `nat': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.3.5: can't initialize iptables table `nat': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.3.5: can't initialize iptables table `nat': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.3.5: can't initialize iptables table `nat': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

ip_forwarding was disabled, but we cannot re-enable it now.
remember to re-enable it manually


and it crashes, i have libnet for slackware 11 installed from linuxpackages.net.
i have however another box running slack 10.2 which uses the same but 10.2 build and it is working nice.

EDIT: im running it as root

any help is appreciated
thank you

strace might help, or give an idea of what's going on. If iptables is being called (I'm not familiar with this plugin), you might move it aside and replace it with a shell script that dumps its command line to a file, so you can then read the file and see how iptables was trying to be called. Sometimes apps send the wrong parameters to other programs that makes the program behave odd.