Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Openntpd problem

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    2 Posts 2 Posters 3.7k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • savagoS
      savago
      last edited by

      
      8.1-RELEASE-p1 FreeBSD 8.1-RELEASE-p1 #1: Sun Nov 14 17:21:29 EST 2010     sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8  i386
      
      

      System: General Setup
      Time zone: Europe/Sofia
      NTP time server: bg.pool.ntp.org

      
      ps aux | grep ntp
      _ntp   63553  0.0  0.1  3316  1352  ??  I    11:15PM   0:00.01 ntpd: ntp engine (ntpd)
      root   63847  0.0  0.1  3316  1340  ??  Ss   11:15PM   0:00.00 ntpd: [priv] (ntpd)
      root   60299  0.0  0.1  3524  1252   0  S+   11:40PM   0:00.00 grep ntp
      
      
      
      sockstat -4 -p 123
      USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS      
      _ntp     ntpd       63553 8  udp4   87.120.x.y:50083  213.16.33.98:123
      _ntp     ntpd       63553 14 udp4   192.168.0.254:123     *:*
      _ntp     ntpd       63553 15 udp4   87.120.x.y:21596  109.160.96.3:123
      _ntp     ntpd       63553 16 udp4   87.120.x.y:41771  84.54.128.8:123
      
      

      request from client to local server

      
      rdate -ncv 192.168.0.254
      rdate: Ignoring NTP server with alarm flag set
      rdate: Unable to get a reasonable time estimate
      
      

      tcpdump on server

      
      tcpdump -vni re0 port 123
      tcpdump: listening on re0, link-type EN10MB (Ethernet), capture size 96 bytes
      23:46:17.678669 IP (tos 0x0, ttl 64, id 3027, offset 0, flags [DF], proto UDP (17), length 76)
          192.168.0.10.49930 > 192.168.0.254.123: NTPv4, length 48
      	Client, Leap indicator:  (0), Stratum 0, poll 0s, precision 0
      	Root Delay: 0.000000, Root dispersion: 0.000000, Reference-ID: (unspec)
      	  Reference Timestamp:  0.000000000
      	  Originator Timestamp: 0.000000000
      	  Receive Timestamp:    0.000000000
      	  Transmit Timestamp:   30099702.756250398 (2037/01/20 17:29:58)
      	    Originator - Receive Timestamp:  0.000000000
      	    Originator - Transmit Timestamp: 30099702.756250398 (2037/01/20 17:29:58)
      23:46:17.678829 IP (tos 0x10, ttl 64, id 16367, offset 0, flags [none], proto UDP (17), length 76, bad cksum 0 (->b849)!)
          192.168.0.254.123 > 192.168.0.10.49930: NTPv4, length 48
      	Server, Leap indicator: clock unsynchronized (192), Stratum 4, poll 0s, precision -21
      	Root Delay: 0.005401, Root dispersion: 0.000000, Reference-ID: 219.32.194.102
      	  Reference Timestamp:  3498846208.091878890 (2010/11/15 23:43:28)
      	  Originator Timestamp: 30099702.756250398 (2037/01/20 17:29:58)
      	  Receive Timestamp:    3498846377.678762912 (2010/11/15 23:46:17)
      	  Transmit Timestamp:   3498846377.678769111 (2010/11/15 23:46:17)
      	    Originator - Receive Timestamp:  -826220621.077487483
      	    Originator - Transmit Timestamp: -826220621.077481284
      
      

      request from client to some ntp pools, work

      
      rdate -ncv bg.pool.ntp.org
      Mon Nov 15 23:48:10 EET 2010
      rdate: adjust local clock by -0.072800 seconds
      
      

      Sys 2.0-RC1: Intel Atom N330 Dual Core @1.6 2048M Ram 40GHD

      1 Reply Last reply Reply Quote 0
      • M
        Michael Sh.
        last edited by

        ntpd need some time after start for synchronization. Before it ntpd ask to clients:”I am a bad clock”:)

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.