From owner-freebsd-bugs@FreeBSD.ORG Sun Feb 23 13:40:02 2014 Return-Path: Delivered-To: freebsd-bugs@smarthost.ysv.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 D4DEF32C for ; Sun, 23 Feb 2014 13:40:02 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (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 C13C31D26 for ; Sun, 23 Feb 2014 13:40:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s1NDe29Y091176 for ; Sun, 23 Feb 2014 13:40:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1NDe28t091175; Sun, 23 Feb 2014 13:40:02 GMT (envelope-from gnats) Date: Sun, 23 Feb 2014 13:40:02 GMT Message-Id: <201402231340.s1NDe28t091175@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Nicolas DEFFAYET Subject: Re: kern/186755: ipsec tunnels don't work with pf or ipfw X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Nicolas DEFFAYET List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Feb 2014 13:40:02 -0000 The following reply was made to PR kern/186755; it has been noted by GNATS. From: Nicolas DEFFAYET To: bug-followup@FreeBSD.org, ben@desync.com, andre@freebsd.org Cc: Subject: Re: kern/186755: ipsec tunnels don't work with pf or ipfw Date: Sun, 23 Feb 2014 14:34:00 +0100 After very long testing, i have discovered the route cause. The revision 254519 break the firewall with IPsec. http://svnweb.freebsd.org/base?view=revision&revision=254519 "Move the global M_SKIP_FIREWALL mbuf flags to a protocol layer specific flag instead. The flag is only used within the IP and IPv6 layer 3 protocols. Because some firewall packages treat IPv4 and IPv6 packets the same the flag should have the same value for both." It seem that some code doesn't have been updated for allow firewall to work with IPsec. -- Nicolas DEFFAYET