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

    Pfsense Date & Time

    Scheduled Pinned Locked Moved Captive Portal
    55 Posts 9 Posters 44.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.
    • A
      Ashutosh Jain
      last edited by

      @cmb:

      Configure a NTP server under System>General Setup.

      Already configure NTP server.

      1 Reply Last reply Reply Quote 0
      • A
        Ashutosh Jain
        last edited by

        @muswellhillbilly:

        @ashi_220:

        how it is changed & getting six year old date/time when i was not change any date/time settings??

        My guess is that your CMOS battery may be running low generally, though maybe not enough to bomb out completely. Might be worth replacing it in the long run, and also do what cmb suggests and set an NTP server in your settings.

        I think their may be issue of CMOS battery. I had already configure NTP server.

        1 Reply Last reply Reply Quote 0
        • S Samuel BF referenced this topic on
        • C
          Cleetus Antony @Iahmad
          last edited by

          @Iahmad
          I have the same issue. My BIOS time is correct.
          Is there anyway I can set time by command prompt.

          E GertjanG 2 Replies Last reply Reply Quote 0
          • E
            elvisimprsntr @Cleetus Antony
            last edited by

            @Cleetus-Antony said in Pfsense Date & Time:

            I have the same issue. My BIOS time is correct.

            Is your BIOS time UTC or local?

            Linux/FreeBSD requires it to be UTC time

            Then make sure to configure the correct timezone for your location.

            C 1 Reply Last reply Reply Quote 0
            • GertjanG
              Gertjan @Cleetus Antony
              last edited by

              @Cleetus-Antony

              And why wouldn't the pfSense build in NTP client work for you ?
              Or isn't your pfSense connected to the Internet ?

              No "help me" PM's please. Use the forum, the community will thank you.
              Edit : and where are the logs ??

              C 1 Reply Last reply Reply Quote 0
              • C
                Cleetus Antony @Gertjan
                last edited by

                @Gertjan PFSENSE connected to internet and everything is working. Clients r getting internet thru pfsense. When I want to create rules with scheduler, due to time wrong time, the rule doesnt work as indented for clients. Any clue ?

                1 Reply Last reply Reply Quote 0
                • C
                  Cleetus Antony @elvisimprsntr
                  last edited by

                  @elvisimprsntr
                  I set the correct time zone in pfsense. Date is correct. but the time is few hours difference. Looks like the time in BIOS is local. there is no option I can see in BIOS to change to UTC. What am I missing ?

                  E 2 Replies Last reply Reply Quote 0
                  • E
                    elvisimprsntr @Cleetus Antony
                    last edited by

                    This post is deleted!
                    1 Reply Last reply Reply Quote 0
                    • E
                      elvisimprsntr @Cleetus Antony
                      last edited by

                      @Cleetus-Antony

                      simply set the BIOS time to UTC HH:MM:SS

                      https://www.timeanddate.com/worldclock/timezone/utc

                      C 2 Replies Last reply Reply Quote 1
                      • C
                        Cleetus Antony @elvisimprsntr
                        last edited by

                        @elvisimprsntr
                        Time in BIOS is correct and its in UTC format. Still I installed new battery in motherboard.
                        But even after setting correct time zone in pfsense, time is 7 Hours ahead.

                        E 1 Reply Last reply Reply Quote 0
                        • E
                          elvisimprsntr @Cleetus Antony
                          last edited by

                          @Cleetus-Antony

                          1. GUI: stop NTP service
                          2. CLI: ntpdate time.nist.gov
                          3. GUI: restart NTP service
                          C 3 Replies Last reply Reply Quote 0
                          • C
                            Cleetus Antony @elvisimprsntr
                            last edited by

                            This post is deleted!
                            1 Reply Last reply Reply Quote 0
                            • C
                              Cleetus Antony @elvisimprsntr
                              last edited by

                              @elvisimprsntr

                              Did the same. I got below msg on output.
                              Still the time is wrong.. Now 4 Hours 30 min difference.

                              14 Jun 19:03:04 ntpdate[63408]: the NTP socket is in use, exiting

                              1 Reply Last reply Reply Quote 0
                              • C
                                Cleetus Antony @elvisimprsntr
                                last edited by

                                @elvisimprsntr
                                14 Jun 19:14:57 ntpdate[69805]: no server suitable for synchronization found

                                this is the result of second try

                                1 Reply Last reply Reply Quote 0
                                • C
                                  Cleetus Antony @elvisimprsntr
                                  last edited by

                                  @elvisimprsntr
                                  "DNS Resolver is stopped or Disabled" when we chk the tatus of DNS Resolver.
                                  In the DNS Resolver page, the Enable DNS Resolver tick mark is ON
                                  May be NTP server setting is not resolving ??????
                                  DNS Resolution behavior is set as Default.(First use local and fall back to remote)

                                  DNS forwarder is ON and working.

                                  GertjanG 1 Reply Last reply Reply Quote 0
                                  • GertjanG
                                    Gertjan @Cleetus Antony
                                    last edited by

                                    @Cleetus-Antony said in Pfsense Date & Time:

                                    DNS forwarder is ON and working.

                                    Then the NTP client can resolve.

                                    No "help me" PM's please. Use the forum, the community will thank you.
                                    Edit : and where are the logs ??

                                    C 2 Replies Last reply Reply Quote 0
                                    • C
                                      Cleetus Antony @Gertjan
                                      last edited by

                                      @Gertjan But no effect. Tried all the ways . Time is still 4 and half hour ahead.

                                      1 Reply Last reply Reply Quote 0
                                      • C
                                        Cleetus Antony @Gertjan
                                        last edited by

                                        @Gertjan
                                        14 Jun 19:14:57 ntpdate[69805]: no server suitable for synchronization found

                                        This response means any issue with DNS ?

                                        GertjanG 1 Reply Last reply Reply Quote 0
                                        • GertjanG
                                          Gertjan @Cleetus Antony
                                          last edited by

                                          @Cleetus-Antony

                                          Noop.
                                          A (the pfSense) NTP client syncs with an NTP server, typically an IP (and in that case : no DNS needed ;) ), a host name or even a pool.
                                          It tells you it wasn't able to do so.

                                          Example :
                                          I'm in France, so I used a local NTP server pool :

                                          6e2fe29c-1c5e-4541-8535-11ca27baa4a0-image.png

                                          Because you should never 'type in stuff without checking, I've checked this "2.fr.pool.ntp.org" :

                                          [24.03-RELEASE][root@pfSense.bhf.tld]/root: dig @127.0.0.1 2.fr.pool.ntp.org +short
                                          195.154.226.102
                                          149.91.80.92
                                          91.224.149.41
                                          82.64.81.218
                                          

                                          This tells me 3 things :
                                          The pool is a pool, there are several IPs.
                                          The 'host name' resolves to IPs.
                                          And, bonus : my DNS works.

                                          My 'NTP' is happy of course :

                                          7952f4c1-cfca-44de-8da2-a7297897a01d-image.png

                                          Hummm : the status told me my check was wrong ....
                                          Ok, again :

                                          [24.03-RELEASE][root@pfSense.bhf.tld]/root: dig @127.0.0.1 2.fr.pool.ntp.org AAAA +short
                                          2001:41d0:801:2000::acb
                                          2001:41d0:304:200::6803
                                          2603:1020:802:3::a8
                                          2001:861:4080:81b1::3
                                          

                                          Also fine.

                                          No "help me" PM's please. Use the forum, the community will thank you.
                                          Edit : and where are the logs ??

                                          C 1 Reply Last reply Reply Quote 0
                                          • C
                                            Cleetus Antony @Gertjan
                                            last edited by

                                            @Gertjan said in Pfsense Date & Time:

                                            dig @127.0.0.1 2.fr.pool.ntp.org +short

                                            Thank u for the info.
                                            My NTP is sad.

                                            dd0a9615-488e-4df0-aa7f-469b0b58118a-image.png

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