it's a linux module and you should first check if it exists or loaded.
use:
lsmod |grep -i tproxy
to see if it's loaded
to check if the kernel has a built module you should run:
modprobe -l |egrep -i "tproxy|socket"
you should have 2 modules for tproxy and also some iptable socket moduels.
if you didnt did any of the above before running the iptables command
these should give you the answer if you have tproxy support as a kernel
module.
Regrads,
Eliezer
On 02/03/2012 19:33, David Touzeau wrote:
There is bad news, backports did not change something according Tproxy
Only kernel 3.2x is available on backports repository.
apt-get install -t squeeze-backports linux-image-3.2.0-0.bpo.1-686-pae
apt-get install -t squeeze-backports upgrade
reboot
my kernel is now
Linux squid32.localhost.localdomain 3.2.0-0.bpo.1-686-pae #1 SMP Sat Feb
11 14:57:20 UTC 2012 i686 GNU/Linux
iptables -t tproxy -A PREROUTING -i eth0 -p tcp -m tcp --dport 80 -j
TPROXY --on-port 80
WARNING: All config files need .conf: /etc/modprobe.d/fuse, it will be
ignored in a future release.
iptables v1.4.8: can't initialize iptables table `tproxy': Table does
not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded
grep -i iptables /boot/config-`uname -r`
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP6_NF_IPTABLES=m
# iptables trigger is under Netfilter config (LED target)
SNIF, SNIF
Le 02/03/2012 17:03, David Touzeau a écrit :
iptables -t tproxy -A PREROUTING -i eth0 -p tcp -m tcp --dport 80 -j
TPROXY --on-port 80
