Network Time Protocol: Difference between revisions
Jump to navigation
Jump to search
(NTP) |
No edit summary |
||
| Line 3: | Line 3: | ||
== AREDN NTP Changes == |
== AREDN NTP Changes == |
||
From version 3.22.X.0 onwards, node 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. |
From version 3.22.X.0 onwards, node 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. |
||
| + | |||
| + | == Guides == |
||
| + | |||
| + | * [https://austinsnerdythings.com/2021/04/19/microsecond-accurate-ntp-with-a-raspberry-pi-and-pps-gps/ Microsecond accurate NTP with a Raspberry Pi and PPS GPS] ([https://www.youtube.com/watch?v=YfgX7qPeiqQ video]) |
||
== Available Local Time Servers == |
== Available Local Time Servers == |
||
Revision as of 13:46, 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.X.0 onwards, node 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.
Guides
Available Local Time Servers
- rpintp.local.mesh
- KN6PLV-ntp.local.mesh