From owner-freebsd-questions@FreeBSD.ORG Mon Jul 4 15:55:37 2005 Return-Path: X-Original-To: freebsd-questions@FreeBSD.ORG Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D27016A41C for ; Mon, 4 Jul 2005 15:55:37 +0000 (GMT) (envelope-from fbsd_user@a1poweruser.com) Received: from mta9.adelphia.net (mta9.adelphia.net [68.168.78.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id E921C43D48 for ; Mon, 4 Jul 2005 15:55:36 +0000 (GMT) (envelope-from fbsd_user@a1poweruser.com) Received: from barbish ([69.172.31.81]) by mta9.adelphia.net (InterMail vM.6.01.04.01 201-2131-118-101-20041129) with SMTP id <20050704155536.WJGL29002.mta9.adelphia.net@barbish> for ; Mon, 4 Jul 2005 11:55:36 -0400 From: "fbsd_user" To: "freebsd-questions@FreeBSD. ORG" Date: Mon, 4 Jul 2005 11:55:31 -0400 Message-ID: MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: PF firewall using anchors X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fbsd_user@a1poweruser.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jul 2005 15:55:37 -0000 I am running 5.4 using the run time loadable module for PF firewall. The PF rules load and work fine. The main rule set contains 2 anchor rules. I can add rules to the in core anchor name and then list the anchor and see the rules are really there. Problem is the anchor rules are never being executed by the main rule set. Is there anybody on this questions list who has PF working with anchors? Have read all the PF man pages 6-8 times and my config seems ok. Knowing that PF is new to FreeBSD base in 5.4 thinking this may be a bug.