2 Jan
2007
2 Jan
'07
4:16 p.m.
Hi, On Saturday 30 December 2006 22:47, KOVACS Krisztian wrote:
Is this a known issue with TPROXY 2.0.5?
No, it isn't. I've looked into the problem and it seems to be a locking problem involving expectation removal code paths being called with the NAT lock held from ip_nat_used_tuple()...
Unfortunately I do not have a correct fix yet, but two possible workarounds are:
Ok, I've uploaded a new snapshot of tproxy which supposedly fixes this problem. Could you try whether or not it solves your deadlock problem? http://people.balabit.hu/hidden/tproxy2-2.4.33_20070102.tar.bz2 http://people.balabit.hu/hidden/tproxy2-2.4.33_20070102.tar.bz2.asc -- Regards, Krisztian Kovacs