From owner-freebsd-questions@FreeBSD.ORG Tue Jun 5 23:31:54 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4E34A16A400 for ; Tue, 5 Jun 2007 23:31:54 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by mx1.freebsd.org (Postfix) with ESMTP id 2F0EC13C44B for ; Tue, 5 Jun 2007 23:31:54 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 458105193D for ; Tue, 5 Jun 2007 19:31:50 -0400 (EDT) Date: Wed, 6 Jun 2007 00:31:43 +0100 From: RW To: freebsd-questions@freebsd.org Message-ID: <20070606003143.6087bdfa@gumby.homeunix.com.> In-Reply-To: <4665C091.90808@vwsoft.com> References: <70f41ba20706041403q1d51ac75jee625130ea4ed10@mail.gmail.com> <46648172.3060307@vwsoft.com> <70f41ba20706041537laba6223v8c879e344d799052@mail.gmail.com> <4665C091.90808@vwsoft.com> X-Mailer: Claws Mail 2.9.2 (GTK+ 2.10.12; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: fbsd 6.2 pf starts -- but not on boot X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2007 23:31:54 -0000 On Tue, 05 Jun 2007 21:59:13 +0200 Volker wrote: > Hi snow, > > aha. does that suggest that i'm simply not waiting long enough? > > your following comments suggest otherwise, iiuc, that i need to > > proactively _do_ something different ... > > It's not _you_ aren't waiting too long. It's at the time pf is being > loaded, the interface pf want's to filter on does not yet exist. See > it as a wrong load order. Have you any particular reason to think that this is really a problem? Given that /etc/rc.d/ppp automatically reloads the pf rules after the tun device is created.