From owner-freebsd-stable@FreeBSD.ORG  Wed Jan 15 10:36:11 2014
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 6A2A65F3
 for <freebsd-stable@freebsd.org>; Wed, 15 Jan 2014 10:36:11 +0000 (UTC)
Received: from cell.glebius.int.ru (glebius.int.ru [81.19.69.10])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id E2A4B12E8
 for <freebsd-stable@freebsd.org>; Wed, 15 Jan 2014 10:36:09 +0000 (UTC)
Received: from cell.glebius.int.ru (localhost [127.0.0.1])
 by cell.glebius.int.ru (8.14.7/8.14.7) with ESMTP id s0FAa10S031920
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Wed, 15 Jan 2014 14:36:01 +0400 (MSK)
 (envelope-from glebius@FreeBSD.org)
Received: (from glebius@localhost)
 by cell.glebius.int.ru (8.14.7/8.14.7/Submit) id s0FAa1pl031919;
 Wed, 15 Jan 2014 14:36:01 +0400 (MSK)
 (envelope-from glebius@FreeBSD.org)
X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to
 glebius@FreeBSD.org using -f
Date: Wed, 15 Jan 2014 14:36:01 +0400
From: Gleb Smirnoff <glebius@FreeBSD.org>
To: Nat Howard <freebsd-stable@track.pupworks.com>
Subject: Re: IPSEC/PF (particularly NAT) problem? RC5,4,3
Message-ID: <20140115103601.GJ26504@FreeBSD.org>
References: <CEB744A7-A970-4836-9C4B-B42D6F2B0B60@track.pupworks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CEB744A7-A970-4836-9C4B-B42D6F2B0B60@track.pupworks.com>
User-Agent: Mutt/1.5.22 (2013-10-16)
Cc: freebsd-stable@freebsd.org
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 10:36:11 -0000

  Nat,

On Tue, Jan 14, 2014 at 06:54:09PM -0500, Nat Howard wrote:
N> I'm encountering a problem in updating to 10.0, and wonder if
N> anything has changed with respect to the way in which you tell (the
N> new!) PF code to process stuff coming in via IPSEC -- if, for
N> example, there's a knob somewhere that say "yes, really, really,
N> do the NATing on incoming packets that came in on IPSEC and 
N> are going out (decrypted) in the clear." that wasn't required
N> in previous versions (up to 9.1) of FreeBSD.

AFAIR, nothing has changed in pf in regards to its ipsec handling.
The new part is only finer locking. Well, I could have broken
ipsec. But more probable is that problems lives somewhere out of
pf.

Can you please provide a minimal reproduction case, that does work
on 9.1, and doesn't work on 10.0? You can file it in GNATS as PR.
That would help.

-- 
Totus tuus, Glebius.