From mboxrd@z Thu Jan 1 00:00:00 1970 From: KOVACS Krisztian Subject: Re: Request: including tproxy patch to official iptables/kernel. Date: Tue, 17 Oct 2006 16:38:24 +0200 Message-ID: <200610171638.25425@nienna> References: <20061016114331.AF36.TSUNEO.YOSHIOKA@f-secure.com> <45331D32.5070209@trash.net> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Cc: Yoshioka Tsuneo , Patrick McHardy , tproxy@lists.balabit.hu Return-path: To: netfilter-devel@lists.netfilter.org In-Reply-To: <45331D32.5070209@trash.net> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-devel-bounces@lists.netfilter.org Errors-To: netfilter-devel-bounces@lists.netfilter.org List-Id: netfilter-devel.vger.kernel.org Hi, On Monday 16 October 2006 07:48, Patrick McHardy wrote: > > So, I would like to suggest to include tproxy patch to official > > iptables/kernel release. > > These look quite old (2.4). The TPROXY developers were working on > a new approach last year at the netfilter workshop, but I don't > know if there was any further progress. Please talk to them directly > and ask them if they want to merge it upstream, and if so to submit > patches. Yes, there was significant progress since then, we're testing the patches at the moment. There still are a couple of problems with the new approach, but it certainly looks promising. I'll post the patches on netfilter-devel for review and comments as soon as things have settled down a bit. Instead of trying to get the 2.0 branch of tproxy merged into mainline we're concentrating our efforts on getting the new code working. As the maintainer of the current tproxy patchset, I do not consider it clean and safe enough to have it merged upstream. Moreover, I think there's no general consensus between networking maintainers whether or not the features tproxy provides are worth the hassles. Transparent proxying features have been removed during the 2.3 development as there seemed little interest in those. Of course there are a handful of companies interested in having the feature in mainline, but let's face the facts: the majority of users do not care about tproxy. That's why I don't even try to get it merged. -- Regards, Krisztian Kovacs