From owner-freebsd-stable@FreeBSD.ORG Mon Apr 23 09:45:16 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5421416A400; Mon, 23 Apr 2007 09:45:16 +0000 (UTC) (envelope-from zen@tk-pttuntex.com) Received: from matrix.tk-pttuntex.com (matrix.tk-pttuntex.com [203.77.209.162]) by mx1.freebsd.org (Postfix) with ESMTP id ED28513C448; Mon, 23 Apr 2007 09:45:15 +0000 (UTC) (envelope-from zen@tk-pttuntex.com) Received: from [172.64.14.3] (core.bps.co.id [202.57.0.93]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: zen) by matrix.tk-pttuntex.com (Postfix) with ESMTP id 5D60940B50A; Mon, 23 Apr 2007 16:45:14 +0700 (WIT) Message-ID: <462C80F8.8070708@tk-pttuntex.com> Date: Mon, 23 Apr 2007 16:48:40 +0700 From: zen User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: zen References: <46247471.9030503@tk-pttuntex.com> <200704172129.22275.sanya-spb@list.ru> <20070418095903.12432@caamora.com.au> <462575D4.2010801@tk-pttuntex.com> <20070418115654.30422@caamora.com.au> <46257D1A.7050808@tk-pttuntex.com> <4626CA4C.7000104@tk-pttuntex.com> <462C7896.9040805@tk-pttuntex.com> In-Reply-To: <462C7896.9040805@tk-pttuntex.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Adrian Chadd , freebsd-stable@freebsd.org Subject: Re: tproxy on freebsd X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Apr 2007 09:45:16 -0000 zen wrote: > Adrian Chadd wrote: > >> I'm talking to someone about it who has some patches against -current. >> We'll see what can be done. >> >> Thankfully! The solution for FreeBSD looks doable without having to >> keep NAT state like TPROXY does.. >> >> >> >> Adrian >> > sorry double post just want to _Know_ how's the progress regarding this issue. TIA Zen