On 11/2/06, Jeroen <[EMAIL PROTECTED]> wrote:
On 11/1/06, Holger Bauer <[EMAIL PROTECTED]> wrote:
> Is your WAN connection up and you can access the internet right on bootup?
DNS working fine at the pfSense? openntpd has a problem when it can't resolve the
ntp server via dns when it is started. What kind of WAN are you using?
Yup, WAN is up, i'm using DSL. DNS is working fine also.s
Some more info:
After booting the openntpd log shows lines like this:
Nov 2 11:23:52 ntpd[1517]: Lost child: child exited
Nov 2 11:23:52 ntpd[1517]: dispatch_imsg in main: pipe closed
Nov 2 11:23:52 ntpd[1522]: ntp engine exiting
Nov 2 11:23:40 ntpd[1522]: ntp engine ready
Nov 2 11:23:40 ntpd[1522]: listening on 192.168.10.254
Nov 2 11:23:27 ntpd[1152]: Terminating
Nov 2 11:23:27 ntpd[1153]: ntp engine exiting
Nov 2 11:23:27 ntpd[1153]: ntp engine ready
Nov 2 11:23:27 ntpd[1153]: listening on 192.168.10.254
Nov 2 11:23:25 ntpd[965]: Terminating
Only after i manually start openntpd from the services webgui, it starts:
<SNIP>
Nov 2 13:34:47 ntpd[15399]: peer 85.196.2.102 now valid
Nov 2 13:34:47 ntpd[15399]: peer 213.186.56.126 now valid
Nov 2 13:34:27 ntpd[15399]: ntp engine ready
Nov 2 13:34:27 ntpd[15399]: listening on 192.168.10.254
As for the DNS question, pool.ntp.org resolves like a charm so i don't
think that could
be a problem. The config file for OpenNTPD reads:
listen on 192.168.10.254
servers pool.ntp.org
--
Jeroen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
