From owner-freebsd-questions@FreeBSD.ORG  Fri Jun  8 15:24:51 2007
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
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 2D90616A500
	for <freebsd-questions@freebsd.org>;
	Fri,  8 Jun 2007 15:24:51 +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 BF98913C44C
	for <freebsd-questions@freebsd.org>;
	Fri,  8 Jun 2007 15:24:50 +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 8E48151937
	for <freebsd-questions@freebsd.org>;
	Fri,  8 Jun 2007 11:24:49 -0400 (EDT)
Date: Fri, 8 Jun 2007 16:24:46 +0100
From: RW <fbsd06@mlists.homeunix.com>
To: freebsd-questions@freebsd.org
Message-ID: <20070608162446.4acdb0c0@gumby.homeunix.com.>
In-Reply-To: <70f41ba20706052031q10aff72cy93a8e2e14728d945@mail.gmail.com>
References: <70f41ba20706041403q1d51ac75jee625130ea4ed10@mail.gmail.com>
	<46648172.3060307@vwsoft.com>
	<70f41ba20706041537laba6223v8c879e344d799052@mail.gmail.com>
	<4665C091.90808@vwsoft.com>
	<20070606003143.6087bdfa@gumby.homeunix.com.>
	<70f41ba20706052031q10aff72cy93a8e2e14728d945@mail.gmail.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 <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2007 15:24:51 -0000

On Tue, 5 Jun 2007 20:31:59 -0700
snowcrash+freebsd <schneecrash+freebsd@gmail.com> wrote:

> hi,
> 
> > 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.
> 
> though the prob's been fixed, just to ack/comment ... the issue 4 me
> was that pf itself was not starting, not that it had started but the
> rules were not loaded, or some such ...

Reloading the rules is supposed to allow pf to pick-up new interfaces,
which is why it's done after ppp is started. I was wondering if Volker
had a valid reason for thinking there is a problem, or whether he
was speculating from incomplete knowledge.

As regards pf not starting, in another sub-thread you seem to be
saying that the underlying problem was an irregularity in ppp.conf.
ppp.conf is not read until *after* pf starts-up, so can't explain
pf's not starting.