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

    Two pfSense boxes and NTP

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 2 Posters 2.8k 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.
    • E
      Eugene
      last edited by

      Trying to make pfSense-nano to get time from pfSense-1.2.3
      On client I see
      21 May 09:58:09 ntpdate[46964]: no server suitable for synchronization found
      21 May 09:58:14 ntpdate[46967]: no server suitable for synchronization found

      On the server I see
      09:59:04.710161 IP 192.168.81.251.123 > 192.168.81.252.123: NTPv4, Client, length 48
      09:59:04.710527 IP 192.168.81.252.123 > 192.168.81.251.123: NTPv4, Server, length 48
      09:59:04.711410 IP 192.168.81.251.123 > 192.168.81.252.123: NTPv4, Client, length 48
      09:59:04.711455 IP 192.168.81.252.123 > 192.168.81.251.123: NTPv4, Server, length 48
      09:59:04.712534 IP 192.168.81.251.123 > 192.168.81.252.123: NTPv4, Client, length 48
      09:59:04.712588 IP 192.168.81.252.123 > 192.168.81.251.123: NTPv4, Server, length 48
      09:59:04.713534 IP 192.168.81.251.123 > 192.168.81.252.123: NTPv4, Client, length 48
      09:59:04.713577 IP 192.168.81.252.123 > 192.168.81.251.123: NTPv4, Server, length 48
      09:59:09.820997 IP 192.168.81.251.123 > 192.168.81.252.123: NTPv4, Client, length 48
      09:59:09.821065 IP 192.168.81.252.123 > 192.168.81.251.123: NTPv4, Server, length 48
      09:59:09.822234 IP 192.168.81.251.123 > 192.168.81.252.123: NTPv4, Client, length 48
      09:59:09.822277 IP 192.168.81.252.123 > 192.168.81.251.123: NTPv4, Server, length 48
      09:59:09.823233 IP 192.168.81.251.123 > 192.168.81.252.123: NTPv4, Client, length 48
      09:59:09.823281 IP 192.168.81.252.123 > 192.168.81.251.123: NTPv4, Server, length 48
      09:59:09.824357 IP 192.168.81.251.123 > 192.168.81.252.123: NTPv4, Client, length 48
      09:59:09.824403 IP 192.168.81.252.123 > 192.168.81.251.123: NTPv4, Server, length 48

      Can somebody explain why it is not working?
      Thanks.
      Evgeny.

      http://ru.doc.pfsense.org

      1 Reply Last reply Reply Quote 0
      • Cry HavokC
        Cry Havok
        last edited by

        Have you started the NTP server on pfSense?

        Have you searched the forum?  It's a known and much discussed issue that OpenNTPd takes some time (tens of minutes, maybe longer) to sync, unlike the ISC implementation.

        1 Reply Last reply Reply Quote 0
        • E
          Eugene
          last edited by

          Yes, I am sorry for posting. After an hour or so it is ok now.

          http://ru.doc.pfsense.org

          1 Reply Last reply Reply Quote 0
          • Cry HavokC
            Cry Havok
            last edited by

            No problem.  It wouldn't happen if pfSense used ISC's version ;)

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