OpenNTPD



  • Running pfSense 1.2.3 and as an MS person all I can say is it just works - unlike a few MS packages.

    But I am confused about the simple(?) OpenNTPD service - thought I had pfSense set to sync its time from pool.ntp and OpenNtpd would serve the time to the internal network.  There seems to be no entries in the system log or OpenNTpd log to say anything is happening, a port scan of the pfsense box says that port 123 is closed but some clients say that they have syncronised.

    Unable to find /etc/ntpd.conf - should that have been created automatically?  TOP shows no time related entries

    Or am I looking for a problem that does not exist and this is exactly how OpenNTPD works - in which case why is there a tab for it under the system logs?

    Thanks

    Andrew



  • Did you enable OpenNTPD on needed interface(s) at Services->OpenNTPD ?



  • I've noticed the same behaviour, and yes, the LAN nic is enabled…



  • And you have a rule on LAN allowing NTP (udp:123)?
    Can you give here```
    netstat -an



  • Well netstat implies all is well

    udp4      0      0 192.168.5.11.42519    95.130.9.63.123       
    udp4      0      0 192.168.5.11.41648    85.31.187.67.123     
    udp4      0      0 192.168.5.11.56705    81.19.96.148.123

    Must just be that OpenNTPD has nothing worth logging?

    Regards

    Andrew



  • netstat says that ntpd is not working as server on any interface.


  • LAYER 8 Global Moderator

    Well I was seeing the same issue, never bothered to look into it before since I run a different ntp server that my clients sync with..  But did see same issue your seeing that openntpd was not listening with netstat

    So I restarted the service – and now show it listening.

    udp4      0      0 192.168.1.253.123      .

    And I can query it using ntpdate from another box.. but was getting some errors about leap not sync'd

    Well look at that nows it working... it was showing

    192.168.1.253: Server dropped: Leap not in sync

    Guess it need some time to sync -- since now it seems to be working.


    C:\NTP\bin>ntpdate -d 192.168.1.253
    12 Apr 16:51:45 ntpdate[5672]: ntpdate 4.2.4p7@copenhagen-o May 22 11:25:57 (UTC+02:00) 2009  (3)
    transmit(192.168.1.253)
    receive(192.168.1.253)
    transmit(192.168.1.253)
    receive(192.168.1.253)
    transmit(192.168.1.253)
    receive(192.168.1.253)
    transmit(192.168.1.253)
    receive(192.168.1.253)
    transmit(192.168.1.253)
    server 192.168.1.253, port 123
    stratum 3, precision -21, leap 00, trust 000
    refid [192.168.1.253], delay 0.02560, dispersion 0.00021
    transmitted 4, in filter 4
    reference time:    cf6e13bf.c4afe7ff  Mon, Apr 12 2010 16:48:47.768
    originate timestamp: cf6e1471.c07a37ff  Mon, Apr 12 2010 16:51:45.751
    transmit timestamp:  cf6e1472.13a860dc  Mon, Apr 12 2010 16:51:46.076
    filter delay:  0.02560  0.02560  0.02560  0.02560
            0.00000  0.00000  0.00000  0.00000
    filter offset: -0.32492 -0.32463 -0.32527 -0.32492
            0.000000 0.000000 0.000000 0.000000
    delay 0.02560, dispersion 0.00021
    offset -0.324926
    –-

    I like ntp better, much more functionality... but it sure looks like it working.
    C:\NTP\bin>ntpdate -b 192.168.1.253
    12 Apr 16:58:37 ntpdate[5636]: step time server 192.168.1.253 offset 0.089523 sec

    Is it easy to change over to ntp vs openntpd?



  • I use my box here to sync all my clients.

    The only way I know its working is that my clients dont error out on sync's.

    Nothing has ever showed in the logs.



  • @chpalmer:

    I use my box here to sync all my clients.

    The only way I know its working is that my clients dont error out on sync's.

    Nothing has ever showed in the logs.

    the same here



  • hallo,

    have you found any solution till now?


Log in to reply