Network Time Protocol: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(ntp package) |
||
| Line 2: | Line 2: | ||
== AREDN NTP Changes == |
== AREDN NTP Changes == |
||
| − | From version 3.22.6.0 onwards, |
+ | From version 3.22.6.0 onwards (June 2022), nodes synchronize their time to an NTP server once per day. If the configured server is unreachable, the node automatically searches for a NTP server on the mesh. |
| + | |||
| + | For more accurate time, you can install the [https://github.com/kn6plv/meshntpd/raw/master/meshntpd_0.2_all.ipk meshntp package] which will continually synchronize the node's time with all available ntp servers on the mesh. |
||
== Guides == |
== Guides == |
||
| Line 12: | Line 14: | ||
* rpintp.local.mesh |
* rpintp.local.mesh |
||
* KN6PLV-ntp.local.mesh |
* KN6PLV-ntp.local.mesh |
||
| + | We need more servers! |
||
Latest revision as of 22:34, 7 June 2022
AREDN nodes use the Network Time Protocol (NTP) to synchronize their time. By default, nodes use the global us.pool.ntp.org server, but this can be changed to use a local mesh server.
AREDN NTP Changes
From version 3.22.6.0 onwards (June 2022), nodes synchronize their time to an NTP server once per day. If the configured server is unreachable, the node automatically searches for a NTP server on the mesh.
For more accurate time, you can install the meshntp package which will continually synchronize the node's time with all available ntp servers on the mesh.
Guides
Available Local Time Servers
- rpintp.local.mesh
- KN6PLV-ntp.local.mesh
We need more servers!