# How to configure Chrony time server in GL.iNet router and redirect LAN clients’ sync requests?

**URL:** <https://forum.gl-inet.com/t/how-to-configure-chrony-time-server-in-gl-inet-router-and-redirect-lan-clients-sync-requests/67821>\
**Category:** Router\
**Tags:** KB\
**Created:** [March 27, 2026, 6:48am UTC](https://forum.gl-inet.com/t/how-to-configure-chrony-time-server-in-gl-inet-router-and-redirect-lan-clients-sync-requests/67821 "2026-03-27T06:48:54Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![bruce](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bruce/32/35649_2.png) [@bruce](https://forum.gl-inet.com/u/bruce)\
**Post date:** [March 27, 2026, 6:48am UTC](https://forum.gl-inet.com/t/how-to-configure-chrony-time-server-in-gl-inet-router-and-redirect-lan-clients-sync-requests/67821/1 "2026-03-27T06:48:54Z")

</div>

Hello,

GL.iNet firmware has introduced Chrony (chronyd) as the system time-synchronization service, including support for **NTS** (Network Time Security).

Availability depends on the router model and firmware version.

> For example, Flint 2 uses sysntpd on v4.8.3 and requires v4.8.4 or later for this guide.

This guide explains how to allow LAN clients to synchronize time with the router and redirect their IPv4 and IPv6 NTP requests to the router’s Chrony service.

Before continuing, check whether your firmware includes Chrony:  
`ls /etc/init.d/chronyd`  
And please back up your current router configuration: [How to Export/Import Backup Configuration Files via LuCI](https://forum.gl-inet.com/t/how-to-export-import-backup-configuration-files-via-luci/68190)

If your firmware uses `sysntpd`, refer to the [previous NTP guide](https://forum.gl-inet.com/t/how-to-configure-the-gl-inet-router-as-an-ntp-server-and-redirect-all-lan-clients-ntp-request/64419/1).

### Tutorial:

1. [SSH to router](https://docs.gl-inet.com/router/en/4/faq/remote_ssh_to_router/)

2. Check whether the router system time is correct

3. Edit the Chrony configuration to enable the time server, please **modify [Router LAN IP] according to your LAN IP**

4. Restart Chrony to apply the above new configuration

5. Check the port 123 status

6. Configure the firewall to redirect time requests from LAN clients to the router's time server.  
There are two kinds of firewall implementations: some use `iptables`, some use `nft` (fw4).

7. Verify the redirection  
Run these tests from a computer connected to the router’s LAN or main Wi-Fi. Disconnect any client-side VPN first.

8. Remove the NTP redirection

-end

  

### Addition: Configure custom NTP servers

Chrony’s persistent configuration is stored in `/etc/config/chrony`.

Keep the first Cloudflare pool entry disabled:  
Some firmware versions have a kmwan time-sync handler that checks the first Chrony **pool** entry before time synchronization is marked as valid.  
If its hostname is not `time.cloudflare.com`, the handler may restore the default time sources.

As a temporary workaround:

1. Keep the original first pool entry with `hostname='time.cloudflare.com'`.
2. Disable that entry using `disabled='1'`.
3. Configure your preferred time sources separately.

See our [staff explanation and workaround](https://forum.gl-inet.com/t/firmware-v4-9-preview-what-to-expect/68088/697) for background.

The following commands assume that the original default pool entry is still present. Replace the three example hostnames with your actual NTP servers before running them:

```auto
# Preserve the original first pool, but disable it
uci set chrony.@pool[0].hostname='time.cloudflare.com'
uci set chrony.@pool[0].disabled='1'

# Remove the other default time sources
uci -q delete chrony.time_nl
uci -q delete chrony.netnod
uci -q delete chrony.ptb
uci -q delete chrony.dfm
uci -q delete chrony.cifelli

# Custom NTP server 1
uci set chrony.custom_ntp_1='server'
uci set chrony.custom_ntp_1.hostname='ntp1.example.net'
uci set chrony.custom_ntp_1.iburst='yes'
uci set chrony.custom_ntp_1.nts='yes'

# Custom NTP server 2
uci set chrony.custom_ntp_2='server'
uci set chrony.custom_ntp_2.hostname='ntp2.example.net'
uci set chrony.custom_ntp_2.iburst='yes'
uci set chrony.custom_ntp_2.nts='yes'

# Custom NTP server 3 (time.nl) as a sample
uci set chrony.time_nl='server'
uci set chrony.time_nl.hostname='ntppool1.time.nl'
uci set chrony.time_nl.iburst='yes'
uci set chrony.time_nl.nts='yes'

uci commit chrony
/etc/init.d/chronyd restart

```

To use NTS, choose endpoints that explicitly support it and set `nts='yes'` for those endpoints.  
Do not enable NTS for ordinary NTP servers or `pool.ntp.org` pools.

Verify the custom configuration:

```auto
chronyc sources -v

```

Once synchronized, one of the intended sources should be marked `^*`.

 ![Bruce_2026-07-07_10-50-30](https://forum-static.gl-inet.com/original/3X/9/1/913ed2889d2d88d3d1837b9236df79909ddcb91d.png)

-end

---

<div class="post-metadata">

**Author:** ![murky-rewrap](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/m/9de053/32.png) [@murky-rewrap](https://forum.gl-inet.com/u/murky-rewrap)\
**Post date:** [April 7, 2026, 6:05am UTC](https://forum.gl-inet.com/t/how-to-configure-chrony-time-server-in-gl-inet-router-and-redirect-lan-clients-sync-requests/67821/2 "2026-04-07T06:05:39Z")

</div>

Thanks for the tutorial, these are very helpful for setting up new features and local time serving is important when running an internal CCTV system with no internet access.

Setup went smoothly but I ran into a problem verifying, it was because I was trying to verify from a computer that was connected to a VPN and the router (unsurprisingly) cannot intercept VPN traffic. Leaving this comment here in case it helps someone in the future when they search and find this result.

---

<div class="post-metadata">

**Author:** ![bruce](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bruce/32/35649_2.png) [@bruce](https://forum.gl-inet.com/u/bruce)\
**Post date:** [April 9, 2026, 11:40am UTC](https://forum.gl-inet.com/t/how-to-configure-chrony-time-server-in-gl-inet-router-and-redirect-lan-clients-sync-requests/67821/3 "2026-04-09T11:40:51Z")

</div>

Glad to hear that works in your scenario!

And this will help other users check whether the clients are being run a VPN software.

> [@murky-rewrap](#):
>
> a computer that was connected to a VPN and the router (unsurprisingly) cannot intercept VPN traffic.

Many thanks!

---

<div class="post-metadata">

**Author:** ![alastor](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/a/f08c70/32.png) [@alastor](https://forum.gl-inet.com/u/alastor)\
**Post date:** [April 18, 2026, 1:13pm UTC](https://forum.gl-inet.com/t/how-to-configure-chrony-time-server-in-gl-inet-router-and-redirect-lan-clients-sync-requests/67821/4 "2026-04-18T13:13:11Z")

</div>

Hi, thanks for tutorial. Have several question:

> [@bruce](#):
>
> Beginning with firmware **v4.8.3** , we have made a major upgrade to the system time synchronization component:  
> **Chrony** (chronyd) is now officially introduced as the default time service, replacing the traditional ntp service (sysntpd), which has shown its limitations under modern security standards.

Flint 2 v4.8.3. Chrony was absent - installed manually. Does it depend on model which version supports chrony by default?

Having duplicates

```auto
iptables -t nat -L -v
Chain PREROUTING (policy ACCEPT 891 packets, 241K bytes)
 pkts bytes target prot opt in out source destination
   50 3800 DNAT udp -- br-lan any anywhere anywhere udp dpt:ntp to:192.168.x.1:123
    0 0 DNAT udp -- br-guest any anywhere anywhere udp dpt:ntp to:192.168.y.1:123
    0 0 DNAT udp -- br-lan any anywhere anywhere udp dpt:ntp to:192.168.x.1:123
    0 0 DNAT udp -- br-guest any anywhere anywhere udp dpt:ntp to:192.168.y.1:123

```

```auto
cat /etc/firewall.user
iptables -t nat -A PREROUTING -i br-lan -p udp --dport 123 -j DNAT --to-destination 192.168.x.1:123
iptables -t nat -A PREROUTING -i br-guest -p udp --dport 123 -j DNAT --to-destination 192.168.y.1:123

```

Can it be related to my configuration for guest network also?

```auto
cat /etc/chrony/chrony.conf
# Load UCI configuration
confdir /var/etc/chrony.d

# Load NTP servers from DHCP if enabled in UCI
sourcedir /var/run/chrony-dhcp

# Log clock errors above 0.5 seconds
logchange 0.5

# Don't log client accesses
noclientlog

# Mark the system clock as synchronized
rtcsync

# Record the clock's drift
driftfile /var/run/chrony/drift

Save NTS keys and cookies
ntsdumpdir /var/run/chrony
# allow 192.168.x.1
allow 192.168.x.0/24
# allow 192.168.y.1
allow 192.168.y.0/24

```

Thanks

---

<div class="post-metadata">

**Author:** ![bruce](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bruce/32/35649_2.png) [@bruce](https://forum.gl-inet.com/u/bruce)\
**Post date:** [April 20, 2026, 7:19am UTC](https://forum.gl-inet.com/t/how-to-configure-chrony-time-server-in-gl-inet-router-and-redirect-lan-clients-sync-requests/67821/5 "2026-04-20T07:19:54Z")

</div>

Truly sorry, the Flint2/MT6000 v4.8.3 does not yet support chronyd, but sysntpd.

Please first upgrade your Flint2 to the latest firmware v4.8.4, and configure it with this guide.

If you have to stay on v4.8.3, please refer to this guide:

> [@How to configure the GL.iNet router as an NTP server and redirect all LAN clients NTP request?](https://forum.gl-inet.com/t/how-to-configure-the-gl-inet-router-as-an-ntp-server-and-redirect-all-lan-clients-ntp-request/64419/1):
>
> Hello, This tutorial will guide you to set the router to NTP (network time synchronization) server and overwrite it to the LAN client's NTP service (Including the LAN port and WiFi clients) . There is no need to change the NTP server configuration on all clients. As long as the client is connected to the router LAN port or main WiFi, when it needs to sync time, it will be responded by the router's NTP server and provide the time sync service. [SSH to router](https://docs.gl-inet.com/router/en/4/faq/remote_ssh_to_router/) Check whether the router syste…

---

<div class="post-metadata">

**Author:** ![DifferentComputers](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/d/c57346/32.png) [@DifferentComputers](https://forum.gl-inet.com/u/DifferentComputers)\
**Post date:** [May 18, 2026, 6:34pm UTC](https://forum.gl-inet.com/t/how-to-configure-chrony-time-server-in-gl-inet-router-and-redirect-lan-clients-sync-requests/67821/6 "2026-05-18T18:34:34Z")

</div>

Some of us don’t have a Windows PC or Powershell.

Is there a bash or zsh command that will do `w32tm /stripchart /computer:123.123.123.123 /dataonly /samples:3`

?

---

<div class="post-metadata">

**Author:** ![bruce](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bruce/32/35649_2.png) [@bruce](https://forum.gl-inet.com/u/bruce)\
**Post date:** [May 21, 2026, 3:30am UTC](https://forum.gl-inet.com/t/how-to-configure-chrony-time-server-in-gl-inet-router-and-redirect-lan-clients-sync-requests/67821/7 "2026-05-21T03:30:37Z")

</div>

Since the time synchronization services of open source systems may be different, it may depend on what service is used in your system.

For example:

```auto
ntpdate -q 123.123.123.123
chronyd -Q 'server 123.123.123.123 iburst'

```

---

<div class="post-metadata">

**Author:** ![bobs](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bobs/32/35345_2.png) [@bobs](https://forum.gl-inet.com/u/bobs)\
**Post date:** [July 6, 2026, 8:13pm UTC](https://forum.gl-inet.com/t/how-to-configure-chrony-time-server-in-gl-inet-router-and-redirect-lan-clients-sync-requests/67821/8 "2026-07-06T20:13:17Z")

</div>

Unless you live in northern Europe, you’ll probably want to use time sources more nearby than those provided in the default configuration. Find those chimers geographically in [https://www.ntppool.org/](https://www.ntppool.org/). For worldwide distribution, I would suggest GLI provide the default configuration as `pool pool.ntp.org` or maybe get your own vendor zone.

For example, since I like to use both the general US pool and my ISP’s more local server, I said

> ```auto
> chronyc add pool us.pool.ntp.org iburst burst xleave
> chronyc add server ntp.hunterfiber.com iburst burst xleave
> chronyc delete nts.netnod.se
> chronyc delete ...
> 
> ```

I deleted the others I saw in `chronyc sources`

My question: After I `chronyd restart` I am back to the servers listed in `/var/etc/chronyd/10-uci.conf`. I tried editing that file and on restart it was replaced with the factory contents. How can I make my NTP source configuration persistent?

---

<div class="post-metadata">

**Author:** ![bruce](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bruce/32/35649_2.png) [@bruce](https://forum.gl-inet.com/u/bruce)\
**Post date:** [July 7, 2026, 2:53am UTC](https://forum.gl-inet.com/t/how-to-configure-chrony-time-server-in-gl-inet-router-and-redirect-lan-clients-sync-requests/67821/9 "2026-07-07T02:53:04Z")

</div>

You need to manually modify the `/etc/config/chrony` configuration file to make the chrony settings persistent.

Alternatively, you can configure it using the `uci` command:

```auto
uci -q delete chrony.@pool[0]
uci -q delete chrony.time_nl
uci -q delete chrony.netnod
uci -q delete chrony.ptb
uci -q delete chrony.dfm
uci -q delete chrony.cifelli

uci add chrony pool
uci set chrony.@pool[-1].maxpoll='12'
uci set chrony.@pool[-1].iburst='yes'
uci set chrony.@pool[-1].nts='yes'
uci set chrony.@pool[-1].hostname='us.pool.ntp.org'

uci set chrony.@dhcp_ntp_server[0]='dhcp_ntp_server'
uci set chrony.@dhcp_ntp_server[0].iburst='yes'
uci set chrony.@dhcp_ntp_server[0].disabled='no'

uci set chrony.@allow[0]='allow'
uci set chrony.@allow[0].interface='lan'

uci set chrony.@makestep[0]='makestep'
uci set chrony.@makestep[0].threshold='1.0'
uci set chrony.@makestep[0].limit='3'

uci set chrony.@nts[0]='nts'
uci set chrony.@nts[0].rtccheck='yes'
uci set chrony.@nts[0].systemcerts='yes'

uci set chrony.hunterfiber='server'
uci set chrony.hunterfiber.hostname='ntp.hunterfiber.com'
uci set chrony.hunterfiber.iburst='yes'
uci set chrony.hunterfiber.nts='yes'

uci commit chrony

/etc/init.d/chronyd restart 

```

You can verify if the NTS service is running and check the availability of the time servers by the command `chronyc sources -v`.

Since `ntp.hunterfiber.com` is unavailable in my location, I have added `ntppool1.time.nl` back to maintain NTS service availability.

 ![Bruce_2026-07-07_10-49-47](https://forum-static.gl-inet.com/original/3X/e/2/e21b875680cba6c6675d4c16778fe6dbe55c8e23.png)

```auto
uci set chrony.time_nl='server'
uci set chrony.time_nl.hostname='ntppool1.time.nl'
uci set chrony.time_nl.iburst='yes'
uci set chrony.time_nl.nts='yes'

uci commit chrony

/etc/init.d/chronyd restart 

```

 ![Bruce_2026-07-07_10-50-30](https://forum-static.gl-inet.com/original/3X/9/1/913ed2889d2d88d3d1837b9236df79909ddcb91d.png)

---

<div class="post-metadata">

**Author:** ![JimmyJoeBobAlooba](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/jimmyjoebobalooba/32/35133_2.png) [@JimmyJoeBobAlooba](https://forum.gl-inet.com/u/JimmyJoeBobAlooba)\
**Post date:** [July 7, 2026, 2:49pm UTC](https://forum.gl-inet.com/t/how-to-configure-chrony-time-server-in-gl-inet-router-and-redirect-lan-clients-sync-requests/67821/10 "2026-07-07T14:49:10Z")

</div>

`I was playing with this (uci command are definitely more reliable and consistent) and it's worth noting that unless you're a global traveler, you can set the sources to a single source as instructed in the`[`NTP.POOL usage instructions`](https://www.ntppool.org/use.html)`and leave it be. The DNS used by this service is built to resolve the names to the NTP service nearest you. You can also specify the continental or country sub-zones. Another special note: if you want to ensure the most availability, you can also use the "2" subdomain (i.e., 2.asia.pool.ntp.org) to include IPv6 addresses.`

---

<div class="post-metadata">

**Author:** ![JimmyJoeBobAlooba](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/jimmyjoebobalooba/32/35133_2.png) [@JimmyJoeBobAlooba](https://forum.gl-inet.com/u/JimmyJoeBobAlooba)\
**Post date:** [September 16, 2026, 2:42pm UTC](https://forum.gl-inet.com/t/how-to-configure-chrony-time-server-in-gl-inet-router-and-redirect-lan-clients-sync-requests/67821/11 "2026-09-16T14:42:59Z")

</div>

@will.qiu helped me sort out an oddity in this process. TLDR; you have to keep the [time.cloudflare.com](http://time.cloudflare.com) entry in the set or the kmwan startup will replace all your customizations with the defaults.  
The details are [here](https://forum.gl-inet.com/t/firmware-v4-9-preview-what-to-expect/68088/697).

---

<div class="post-metadata">

**Author:** ![riri0](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/r/aeb1de/32.png) [@riri0](https://forum.gl-inet.com/u/riri0)\
**Post date:** [October 5, 2026, 9:50pm UTC](https://forum.gl-inet.com/t/how-to-configure-chrony-time-server-in-gl-inet-router-and-redirect-lan-clients-sync-requests/67821/12 "2026-10-05T21:50:15Z")

</div>

Hi, I am trying this out with my newly received Flint 4 and I am getting an error while testing in my Powershell with `w32tm /stripchart /computer:www.google.com /dataonly /samples:3`

I think it is because I enabled ipv6. Does it not work with ipv6 enabled? How do i undo all this? I dont want my ntp requests from devices not work if they happen to use ipv6.

The `w32tm /stripchart /computer:123.123.123.123 /dataonly /samples:3` works fine. And confirmed in tcpdump.

---

<div class="post-metadata">

**Author:** ![AI\_bot](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/a/ecccb3/32.png) [@AI\_bot](https://forum.gl-inet.com/u/AI_bot)\
**Post date:** [October 5, 2026, 9:50pm UTC](https://forum.gl-inet.com/t/how-to-configure-chrony-time-server-in-gl-inet-router-and-redirect-lan-clients-sync-requests/67821/13 "2026-10-05T21:50:53Z")

</div>

The redirect in this guide targets **IPv4 UDP port 123 only**. Enabling IPv6 does not disable it, but an NTP request sent over IPv6 will bypass the IPv4 redirect and continue to its original destination. First test with the literal IPv4 address to remove DNS/IPv6 from the test:

```powershell
w32tm /stripchart /computer:123.123.123.123 /dataonly /samples:3

```

If that works while `www.google.com` fails, IPv6 or name resolution is the relevant difference—not a failure of the IPv4 redirect. To undo the configuration:

1. In LuCI, open **Network → Firewall → Port Forwards** , delete **Redirect-LAN-NTP** , then save and apply.
2. Remove the `allow <your-LAN-subnet>` line that you added to `/etc/chrony/chrony.conf`.
3. Restart Chrony:

```sh
/etc/init.d/chronyd restart

```

You should not uninstall Chrony because it is the router’s normal time-synchronization service. After removing the redirect, each device will contact its configured NTP server normally over either IPv4 or IPv6.

> **This reply was generated by AI. Please verify its accuracy.**
> 
> GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.

---

<div class="post-metadata">

**Author:** ![Swicked86](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/s/58f4c7/32.png) [@Swicked86](https://forum.gl-inet.com/u/Swicked86)\
**Post date:** [October 13, 2026, 4:58am UTC](https://forum.gl-inet.com/t/how-to-configure-chrony-time-server-in-gl-inet-router-and-redirect-lan-clients-sync-requests/67821/14 "2026-10-13T04:58:34Z")

</div>

Will this be in the GUI with the DHCP option 42 set sometime in the future?

---

<div class="post-metadata">

**Author:** ![packetmonkey](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/packetmonkey/32/16711_2.png) [@packetmonkey](https://forum.gl-inet.com/u/packetmonkey)\
**Post date:** [October 14, 2026, 2:52am UTC](https://forum.gl-inet.com/t/how-to-configure-chrony-time-server-in-gl-inet-router-and-redirect-lan-clients-sync-requests/67821/15 "2026-10-14T02:52:30Z")

</div>

Do you actually have clients that support this? 😉

---

<div class="post-metadata">

**Author:** ![bruce](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bruce/32/35649_2.png) [@bruce](https://forum.gl-inet.com/u/bruce)\
**Post date:** [October 14, 2026, 11:46am UTC](https://forum.gl-inet.com/t/how-to-configure-chrony-time-server-in-gl-inet-router-and-redirect-lan-clients-sync-requests/67821/16 "2026-10-14T11:46:36Z")

</div>

DHCP option in Ethernet (WAN) configuration, or in the DHCP server?
