From owner-freebsd-questions@FreeBSD.ORG Tue Mar 1 15:45:21 2005 Return-Path: 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 4410216A4CE for ; Tue, 1 Mar 2005 15:45:21 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF17443D46 for ; Tue, 1 Mar 2005 15:45:20 +0000 (GMT) (envelope-from freebsd.ml@gmail.com) Received: by wproxy.gmail.com with SMTP id 36so56018wri for ; Tue, 01 Mar 2005 07:45:20 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=lc+MSNZKJizxrGB6YK5Y6654KMvSOEOd7BtzajuZ44H7oFq7JLE0SgLBb+qoHXVXhTzim71JKI/2CZlE169MFQz8E/gYwvL3oOMXci1Mt3II3AxelXftYuvMI5l930+hHpLJEt/Dp+mBK6Ae94F41uedkrYnhOpqGhM+M+wqyPk= Received: by 10.54.9.63 with SMTP id 63mr114613wri; Tue, 01 Mar 2005 07:45:19 -0800 (PST) Received: by 10.54.20.64 with HTTP; Tue, 1 Mar 2005 07:45:19 -0800 (PST) Message-ID: Date: Tue, 1 Mar 2005 23:45:19 +0800 From: FreeBSD MailingLists To: questions In-Reply-To: <86r7izr22a.fsf@amidala.datadok.no> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <86r7izr22a.fsf@amidala.datadok.no> Subject: Re: pf issues with anchor X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: FreeBSD MailingLists List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Mar 2005 15:45:21 -0000 After sending off the question I did a little more digging and I think I figured it out. I was reading the current pf faq on the openbsd website, which turns out to be based on OpenBSd 3.6 version of pf. FreeBSD 5.3 has OpenBSD 3.5 version of pf. Turns out in the version 3.5 when loading an anchor file you HAD to specify it as... load anchor anchor-name:ruleset-name from "file-path" The version the current faq was written for seems to have made the ruleset-name an optional value, so it wasn't listed in the code example. I found an older version for the faq written for verion 3.5 at. http://openbsd.automagic.org/faq/pf/index.html On 01 Mar 2005 13:19:25 +0100, Peter N. M. Hansteen wrote: > FreeBSD MailingLists writes: > > > when I start pf I get: > > > > Enabling pf. > > /etc/pf.conf:4: anchor '(null)' invalid > > Just to eliminate the obvious - the file you want to pull in exists, is > readable and contains what appears at first glance to be valid pf rules? > > Does including the anchor in the main pf.conf file produce different results? > > -- > Peter N. M. Hansteen, member of the first RFC 1149 implementation team > http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/ > "First, we kill all the spammers" The Usenet Bard, "Twice-forwarded tales" > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >