Mar 4 06:15:11 sole kernel: Setting hostname: sole.domain.com
Mar 4 06:15:11 sole kernel: bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
Mar 4 06:15:11 sole kernel: options=1a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
Mar 4 06:15:11 sole kernel: inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255
Mar 4 06:15:11 sole kernel: media: Ethernet autoselect (none)
Mar 4 06:15:11 sole kernel: status: no carrier
Mar 4 06:15:11 sole kernel: lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
Mar 4 06:15:11 sole kernel: inet 127.0.0.1 netmask 0xff000000
Mar 4 06:15:11 sole kernel: Starting ppp as "root"
Mar 4 06:15:11 sole kernel: Working in ddial mode
Mar 4 06:15:11 sole kernel: Using interface: tun0
Mar 4 06:15:11 sole kernel: Starting dhclient.
Mar 4 06:15:11 sole kernel: bge1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
Mar 4 06:15:11 sole kernel: options=1a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
Mar 4 06:15:11 sole kernel: inet 65.12.14.18 netmask 0xfffff000 broadcast 255.255.255.255
Mar 4 06:15:11 sole kernel: media: Ethernet autoselect (100baseTX <full-duplex>)
Mar 4 06:15:11 sole kernel: status: active
Mar 4 06:15:11 sole kernel: Additional routing options:
Mar 4 06:15:11 sole kernel: IP gateway=YES
Mar 4 06:15:11 sole kernel: .
Mar 4 06:15:11 sole kernel: Starting devd.
Mar 4 06:15:11 sole kernel: Mounting NFS file systems:
Mar 4 06:15:11 sole kernel: .
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


..shouldnt PF start right after the interfaces come up?
The interface comes up and then NTP/NTPD start...and duing this time for 5secs or more there seems to be no pf running....why is this and why doesnt NTP/NTPD start AFTER pf is loaded up?


I think under OpenBSD...pf loads before anything else network related to at least offer minimum protection.

Am i missing something?
Ideally, I think pf should launch immediately after the ppp kernel fires.




-- J.D. Bronson Aurora Health Care // Information Services // Milwaukee, WI USA Office: 414.978.8282 // Email: [EMAIL PROTECTED] // Pager: 414.314.8282

_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to