On 3/03/2012 4:37 a.m., David Touzeau wrote:
> Thanks Amos
>
> So to be clear for me
>
> I need to enable backports in my sources.list and upgrade the kernel
> version to 2.6.37 or above in order to make TPROXY already compiled in
> the kernel ?
>
Probably. I dont know exactly what kernel is in backports.
All I know is that three of the five testers reporting issues in Ubuntu
LTS migrated to Debian and reported back immediately saying it was
working fine.
I assumed that meant they were running default Squeeze, but since you
got the TPROXY disabeled message I'm not sure about anything anymore.
Amos
>
>
> Le 02/03/2012 16:01, Amos Jeffries a écrit :
>> On 2/03/2012 11:03 p.m., David Touzeau wrote:
>>> Thanks Amos
>>>
>>> This is my debian kernel version
>>>
>>> Linux squid32.localhost.localdomain 2.6.32-5-686 #1 SMP Mon Jan 16
>>> 16:04:25 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.
>>>
>>> TProxy feature is not compiled..
>>>
>>
>> Darn. I thought they were at .37.
>>
>> It looks like there may be a backport. Otherwise it would be Wheezy
>> that you need then I'm afraid. 2.6.32 is not really even worth
>> re-building, what you get is a slightly buggy TPROXY.
>>
>> On the good side Wheezy works very well. I've been running with those
>> repositories on production servers quite happily.
>>
>> Amos
>>
>>
Received on Fri Mar 02 2012 - 15:55:26 MST
This archive was generated by hypermail 2.2.0 : Fri Mar 02 2012 - 12:00:02 MST