pf seems to start late?

[Volodymyr Kostyrko]

Giorgos Keramidas wrote:
>>>Mar  4 06:15:11 sole kernel: Starting syslogd.
>>>Mar  4 06:15:11 sole kernel: Mar  4 06:15:11 sole syslogd: kernel boot file is /boot/kernel/kernel
>>>Mar  4 06:15:11 sole kernel: Starting named.
>>>Mar  4 06:15:12 sole kernel: Setting date via ntp.
>>>Mar  4 06:15:15 sole kernel: 4 Mar 06:15:15 ntpdate[345]: step time server x.x.x.x offset -0.534182 sec
>>>Mar  4 06:15:15 sole kernel: Clearing /tmp.
>>>Mar  4 06:15:16 sole kernel: ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib
>>>Mar  4 06:15:16 sole kernel: a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout
>>>Mar  4 06:15:16 sole kernel: Enabling pflogd
>>>Mar  4 06:15:16 sole kernel: .
>>>Mar  4 06:15:16 sole kernel: Mar  4 06:15:16 sole kernel: pflog0: promiscuous mode enabled
>>>Mar  4 06:15:16 sole kernel: Enabling pf.
>>>Mar  4 06:15:16 sole kernel: pf enabled
>>>
>>>Shouldn't PF start right after the interfaces come up? [...]
>>
>>[...]
>>Can you try the following patch to your /etc/rc.d/pf script and tell me
>>if it works for you or if it breaks anything important?

<skip />

> Just in case anyone else tries using this, please try a version that
> doesn't introduce a circular dependency of pf -> netif -> pf:

<skip />

   Guys, didn't you forgot that pf sometimes uses resolver to lookup 
hostnames present in pf.conf? What happens if it should resole hostnames 
with local named?

   PS: But the question seems intresting... i'll check the behavior...

-- 
[WBR], Arcade. [SAT Astronomy/Think to survive!]