NTP configuration

NTP provides time synchronization based on a network of reference clocks located around the world. LEDE support both NTP client protocol (to synchronize local time with a distant clock) and NTP server protocol (to deliver time to your local network).

The ntp configuration is located in system uci subsystem, and found in file /etc/config/system.

Timeserver section

The NTP configuration is found in timeserver section of system uci subsystem.

root@lede:/# uci show system
system.ntp.server='0.lede.pool.ntp.org' '1.lede.pool.ntp.org' '2.lede.pool.ntp.org' '3.lede.pool.ntp.org'

By default, NTP client is enabled and NTP server is disabled:

root@lede:/# cat /etc/config/system
config timeserver 'ntp'
        option enabled '1'
        option enable_server '0'
        list server '0.lede.pool.ntp.org'
        list server '1.lede.pool.ntp.org'
        list server '2.lede.pool.ntp.org'
        list server '3.lede.pool.ntp.org'

To enable server mode, switch enable_server to '1':

        option enable_server '1'

And restart NTP daemon:

root@lede:/# /etc/init.d/sysntp restart

Timeserver section options

These are the options defined for the timeserver ntp section:

Name Type RequiredDefault Description
server list of hostnamesno (lede ntp servers)Pool of NTP servers to poll the time from.
If empty, ntpd disables client mode, and system time won't be set automatically.
enable_serverboolean no 0 setting this to 1 enables the time server on this device, ntpd will answer with the time of the router.
(busybox-ntpd listens to UDP 123 by default)

Legacy information

In /etc/config/system busybox-rdate (was invoked by scripts) has been replaced with busybox-nptd (can run as a daemon) to avoid race condition and also to use current NTP.
The remote time is since configured in /etc/config/system and not in /etc/config/timeserver any longer.

  • WARNING: Old scripts first checked if a lease time server is defined for the interface in the network config.
  • WARNING: If not available or syncing fails, then it searches for time servers in the timeserver config that are either explicitly defined for that interface or via the global setting in the system config.

Regional pull zones

In theory, LEDE pull zone provide the closest available servers. Practically, this may result in distant connections. To make sure to use NTP servers located in your country, it is possible to use regional pull zone. For example, in France, here is a sample configuration (notice the 'fr' for France and adapt it):

root@lede:/# cat /etc/config/system
config timeserver 'ntp'
        option enabled '1'
        option enable_server '0'
        list server '0.fr.pool.ntp.org'
        list server '1.fr.pool.ntp.org'
        list server '2.fr.pool.ntp.org'
        list server '3.fr.pool.ntp.org'

NTP tools

By default, NTP server analysis tools are not installed (and not needed). You may want to install ntp-utils package, which is a collection of tools used to synchronize the system clock with remote NTP time servers and run/monitor local NTP servers. This package contains ntpdc, ntpq and ntptime.

root@lede:/# opkg install ntp-utils

Enter 'ntpq' to query the NTP subsystem and 'peers' to display NTP peers used by your LEDE appliance:

ntpq> peer
     remote           refid      st t when poll reach   delay   offset  jitter
 0.fr.pool.ntp.o .POOL.          16 p    -   64    0    0.000    0.000   0.000
 1.fr.pool.ntp.o .POOL.          16 p    -   64    0    0.000    0.000   0.000
 2.fr.pool.ntp.o .POOL.          16 p    -   64    0    0.000    0.000   0.000
 3.fr.pool.ntp.o .POOL.          16 p    -   64    0    0.000    0.000   0.000
+ntp-3.arkena.ne     2 u  134  256  375   11.838   -1.119   1.194
 nsr2.neoserveur      2 u 1520  512    2   17.462   -0.064   2.688
+ (    4 u  222  256  377   12.241    1.094   1.620
-time1.agiri.nin   3 u   28  256  377   12.385    2.388   0.767
*ns3.stoneartpro   2 u  107  256  377   11.448    0.467   1.243

Type 'q' to exit this display.