Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    StarLink as source for NTP

    Scheduled Pinned Locked Moved General pfSense Questions
    175 Posts 15 Posters 46.7k Views 16 Watching
    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.
    • dennypageD
      dennypage @Ramosel
      last edited by

      @Ramosel said in StarLink as source for NTP:

      operating in "the new world of GPS time"

      I believe the ntpd issue has to do with nuances of newer versions of the NTP protocol rather than GPS.

      FWIW, the Galleon test app looks to be pretty broken. A precision of 2.26156424291633E+74 is clearly wrong.

      If you are running chrony, you can ask it directly what the advertised precision of a source is. Try chronyc ntpdata 192.168.100.1 and look for Precision. I would expect to see something in the range of -14 (61us) to -24 (61ns).

      johnpozJ M R 3 Replies Last reply
      Reply Quote 1
      • johnpozJ
        johnpoz LAYER 8 Global Moderator @dennypage
        last edited by

        @dennypage mine is

        Precision : -25 (0.000000030 seconds)

        Well shoot clearly my clocks are going to be way out ;)

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 26.07 | Lab VMs 2.9.0, 26.07

        dennypageD 1 Reply Last reply
        Reply Quote 2
        • M
          Mission-Ghost @dennypage
          last edited by

          @dennypage

          Not that amazing here; from my Starlink I get, via chronyc ntpdata using the command page on pfSense:

          Precision       : -9 (0.001953125 seconds)
          

          Interesting. I wonder why it's so different that what you expect or what Johnpoz reported.

          dennypageD 1 Reply Last reply
          Reply Quote 0
          • dennypageD
            dennypage @johnpoz
            last edited by

            @johnpoz said in StarLink as source for NTP:

            Precision : -25 (0.000000030 seconds)

            Interesting -- what is the source?

            Some people (companies) use -25 and justify it because the GNSS chip they are using says <= 30ns. However, the precision statement should be about the entire system rather than just the GNSS. To really be -25, you really need to have <= 20ns on the GNSS chip itself, and a very deterministic microcode implementation or high resolution hardware timestamping on each step of the process.

            I have a few real -24s and -25s, and one -26. I'd really like to have a -27, but am not sure I'll get there. I have a reference timing chip that is reliable <= 5ns, but don't have the hardware to put with it. Sad, sad, sad. ๐Ÿ™„

            johnpozJ 1 Reply Last reply
            Reply Quote 0
            • dennypageD
              dennypage @Mission-Ghost
              last edited by

              @Mission-Ghost said in StarLink as source for NTP:

              @dennypage
              Not that amazing here; from my Starlink I get, via chronyc ntpdata using the command page on pfSense:

              Precision       : -9 (0.001953125 seconds)
              

              Interesting. I wonder why it's so different that what you expect or what Johnpoz reported.

              To me that indicates unexpected honesty on the part of StarLink. Based on the number I'm guessing that they are using their carrier signal to communicate time rather than some form of embedded GNSS.

              And to be honest, I expect 2ms is sufficient for 99% of home users.

              chpalmerC M 2 Replies Last reply
              Reply Quote 0
              • chpalmerC
                chpalmer @dennypage
                last edited by chpalmer

                @dennypage said in StarLink as source for NTP:

                And to be honest, I expect 2ms is sufficient for 99% of home users.

                LOL.. most home user oven clocks are >5 minutes off.. ๐Ÿ˜

                Triggering snowflakes one by one..
                Primary- Intel(R) Pentium(R) CPU G4400 @ 3.30GHz on an M470 WG box. pfsense+ 26.07

                1 Reply Last reply
                Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  If they included ntp in the oven you wouldn't have these issues. Accuracy baked in. ๐Ÿ˜‰

                  dennypageD 1 Reply Last reply
                  Reply Quote 3
                  • M
                    Mission-Ghost @dennypage
                    last edited by Mission-Ghost

                    @dennypage the Starlink device knows where it is using GPS as the default locating technology, but there is a configuration item to use its own positioning system instead. I've always used the default GPS. It's NTP server reports it as stratum 1. Here's the rest of my pfSense's chronyc ntpdata from Starlink's (Gen 3 dish):

                    Remote address  : 192.168.100.1 (C0A86401)
                    Remote port     : 123
                    Local address   : 100.[redacted]
                    Leap status     : Normal
                    Version         : 4
                    Mode            : Server
                    Stratum         : 1
                    Poll interval   : 0 (1 seconds)
                    Precision       : -9 (0.001953125 seconds)
                    Root delay      : 0.000000 seconds
                    Root dispersion : 0.000000 seconds
                    Reference ID    : 00000000 ()
                    Reference time  : Sat Oct 03 22:35:19 2026
                    Offset          : -0.000059627 seconds
                    Peer delay      : 0.001953174 seconds
                    Peer dispersion : 0.001953174 seconds
                    Response time   : 0.000061035 seconds
                    Jitter asymmetry: -0.50
                    NTP tests       : 111 111 1111
                    Interleaved     : No
                    Authenticated   : No
                    TX timestamping : Daemon
                    RX timestamping : Kernel
                    Total TX        : 1735
                    Total RX        : 1735
                    Total valid RX  : 1735
                    Total good RX   : 1546
                    Total kernel TX : 0
                    Total kernel RX : 1735
                    Total HW TX     : 0
                    Total HW RX     : 0
                    

                    Starlink used to furnish access to the GPS location data, but they shut that feature down for reasons.

                    I'm not a time wonk like johnpoz or Jeff Geerling, but accurate time is fascinating and the Starlink GPS clock is good enough for my network.

                    dennypageD 1 Reply Last reply
                    Reply Quote 0
                    • johnpozJ
                      johnpoz LAYER 8 Global Moderator @dennypage
                      last edited by

                      @dennypage said in StarLink as source for NTP:

                      Interesting -- what is the source?

                      oh my bad that was my ntp server reporting on one of the ntp servers I use as alternate source to pps

                      When I look on one of my clients I get what my ntp server 192.168.3.32 reports

                      Remote address  : 192.168.3.32 (C0A80320)
                      Remote port     : 123
                      Local address   : 192.168.3.10 (C0A8030A)
                      Leap status     : Normal
                      Version         : 4
                      Mode            : Server
                      Stratum         : 1
                      Poll interval   : 8 (256 seconds)
                      Precision       : -24 (0.000000060 seconds)
                      Root delay      : 0.000015 seconds
                      Root dispersion : 0.000015 seconds
                      Reference ID    : 50505300 (PPS)
                      Reference time  : Sat Oct 03 22:56:58 2026
                      Offset          : +0.000042164 seconds
                      Peer delay      : 0.000732688 seconds
                      Peer dispersion : 0.000000112 seconds
                      Response time   : 0.000168404 seconds
                      Jitter asymmetry: +0.00
                      NTP tests       : 111 111 1111
                      Interleaved     : No
                      Authenticated   : No
                      TX timestamping : Kernel
                      RX timestamping : Kernel
                      Total TX        : 2121
                      Total RX        : 2121
                      Total valid RX  : 2121
                      Total good RX   : 2121
                      root@pihole:/home/pi# 
                      

                      An intelligent man is sometimes forced to be drunk to spend time with his fools
                      If you get confused: Listen to the Music Play
                      Please don't Chat/PM me for help, unless mod related
                      SG-4860 26.07 | Lab VMs 2.9.0, 26.07

                      1 Reply Last reply
                      Reply Quote 1
                      • R
                        Ramosel @dennypage
                        last edited by

                        @dennypage said in StarLink as source for NTP:

                        I believe the ntpd issue has to do with nuances of newer versions of the NTP protocol rather than GPS.

                        FWIW, the Galleon test app looks to be pretty broken. A precision of 2.26156424291633E+74 is clearly wrong.

                        Absolutely. Galleon is just an easy utility to check GPS function... it's old and there is probably an update I just haven't gone looking for. It was posted for function and NOT usability.

                        1 Reply Last reply
                        Reply Quote 0
                        • dennypageD
                          dennypage @stephenw10
                          last edited by

                          @stephenw10 said in StarLink as source for NTP:

                          If they included ntp in the oven you wouldn't have these issues

                          A dream of mine... ๐Ÿ˜Š

                          1 Reply Last reply
                          Reply Quote 0
                          • dennypageD
                            dennypage @Mission-Ghost
                            last edited by

                            @Mission-Ghost said in StarLink as source for NTP:

                            Starlink device knows where it is using GPS as the default locating technology, but there is a configuration item to use its own positioning system instead

                            Gross positioning for pointing a dish (very narrow band, narrow target area) is easy. Accurate timing isn't. Different kind of antenna to begin with... It's rather difficult in many situations.

                            T 1 Reply Last reply
                            Reply Quote 0
                            • T
                              tgl @dennypage
                              last edited by

                              @dennypage said in StarLink as source for NTP:

                              Gross positioning for pointing a dish (very narrow band, narrow target area) is easy. Accurate timing isn't. Different kind of antenna to begin with... It's rather difficult in many situations.

                              But IIUC, Starlink is a low-orbit-satellite-constellation system too. They're going to be using an omnidirectional-or-close-to-it antenna, which should be plenty serviceable for GPS. If they were using geosynchronous satellites I'd agree with you, not gonna be the right antenna configuration.

                              R dennypageD 2 Replies Last reply
                              Reply Quote 0
                              • R
                                Ramosel @tgl
                                last edited by

                                @tgl said in StarLink as source for NTP:

                                They're going to be using an omnidirectional-or-close-to-it antenna

                                Correct... it's phased array.

                                1 Reply Last reply
                                Reply Quote 0
                                • dennypageD
                                  dennypage @tgl
                                  last edited by

                                  @tgl said in StarLink as source for NTP:

                                  Starlink is a low-orbit-satellite-constellation system too. They're going to be using an omnidirectional-or-close-to-it antenna, which should be plenty serviceable for GPS. If they were using geosynchronous satellites I'd agree with you, not gonna be the right antenna configuration.

                                  FWIW, StarLink is a LEO constellation at around 500km, however the GNSS systems are MEO constellations. The lowest GNSS constellation (GLONAS) is around 19,000km, and the highest (Galileo) is around 23,000km. In addition to the MEO satellites, a few of them, BeiDou (China), QZSS (Japan) and NavIC (India) also have GEO components at 35,000km.

                                  A bit of quick research suggests that the StarLink units do indeed have a low end GPS receiver, but that GPS is only used for initial satellite acquisition. After that, they use their own position and timing capabilities. There is a lot of research speculation that if SpaceX would just "tighten up" their implementation, StarLink could be used as an alternative to existing GNSS systems.

                                  Your Research Results May Vary. ๐Ÿ˜Š

                                  1 Reply Last reply
                                  Reply Quote 0

                                  Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                                  Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                                  With your input, this post could be even better ๐Ÿ’—

                                  Register Login
                                  • First post
                                    Last post
                                  Copyright 2026 Rubicon Communications LLC (Netgate). All rights reserved.
                                  Privacy Policy · Cookie Policy