Date: Fri, 8 Jun 2007 16:24:46 +0100 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-questions@freebsd.org Subject: Re: fbsd 6.2 pf starts -- but not on boot 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070608162446.4acdb0c0>