From owner-freebsd-pf@FreeBSD.ORG Sun Jan 2 20:16:06 2011 Return-Path: Delivered-To: freebsd-pf@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1239106564A for ; Sun, 2 Jan 2011 20:16:06 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8BEF58FC08 for ; Sun, 2 Jan 2011 20:16:06 +0000 (UTC) Received: by wyf19 with SMTP id 19so12772832wyf.13 for ; Sun, 02 Jan 2011 12:16:05 -0800 (PST) Received: by 10.227.168.79 with SMTP id t15mr11080767wby.200.1293999365385; Sun, 02 Jan 2011 12:16:05 -0800 (PST) Received: from dfleuriot.local (did75-17-88-165-130-96.fbx.proxad.net [88.165.130.96]) by mx.google.com with ESMTPS id f35sm13556796wbf.8.2011.01.02.12.16.03 (version=SSLv3 cipher=RC4-MD5); Sun, 02 Jan 2011 12:16:04 -0800 (PST) Message-ID: <4D20DD02.2090605@my.gd> Date: Sun, 02 Jan 2011 21:16:02 +0100 From: Damien Fleuriot User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: jay@experts-exchange.com References: <8fb3caa1300a9fcc5c2f23a70ade23a8.squirrel@mail.experts-exchange.com> <4D208AE2.6000402@my.gd> <3020c1e8b0ecb5e9bacb1033ddea2b3e.squirrel@mail.experts-exchange.com> <4D20BAEB.10101@my.gd> <5275a39aa1849d38d509a42b627dd4b0.squirrel@mail.experts-exchange.com> In-Reply-To: <5275a39aa1849d38d509a42b627dd4b0.squirrel@mail.experts-exchange.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-pf@freebsd.org Subject: Re: transparent proxy X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion and general questions about packet filter \(pf\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jan 2011 20:16:07 -0000 On 1/2/11 9:04 PM, jay@experts-exchange.com wrote: > Here I want : > > nn:nn:nn.nnnnnn IP 127.0.0.1.51791 > 192.168.103.2.80: Flags [S], ack ... > > int_if="lo0" > ext_if="ed0" > > pass in on $int_if route-to ($int_if 127.0.0.1) from 192.168.103.1 keep state > > But no good (it's not able to sync) : > How do things go when using synproxy in your pass rule ? Something like: pass in log on $int_if route-to ($int_if 127.0.0.1) from 192.168.103.1 synproxy state