Great! Will do the tests again! Btw, while trying to use 2.6.25 kernel, TPROXY patched, I'm experiencing a _silent_ system hang (no any kernel msg, just hang) after a while of operation - 3~4 hours. I have no idea, if this HW dependant, since it's a regular good P4 PC, but which work reliably (last uptime until kernel change reboot was 180 days, with cttproxy2). It may behave the same even with unpatched 2.6.25 - but since it's a production PC - I can't just experiment on it. 2.6.24 - works with no such issues on the same PC On Tuesday 03 June 2008 11:14, Laszlo Attila Toth wrote:
Anton VG wrote:
Any thoughts?
I fixed it. The getsockopt() wasn't implemented for IP_TRANSPARENT socket option and you used more verbose debug messages in squid, this is why I didn't understand it. Sorry.
You can download it:
http://www.balabit.com/downloads/files/tproxy/tproxy-kern el-2.6.24-20080602-165651-1212418611.tar.bz2
The last, 17th patch is enough to be applied to your last kernel source.
2008/5/21 Anton <anton.vazir@gmail.com>:
But it's a 4.1 patch for 2.6.24 kernel and the installation partially working and I'm getting this complain once in a dosen of requests. - maybe once in 20, sometimes 50 or 100 requests. - the rest are ok and transparently handled by TPROXY and SQUID.