Firmware v4.9 Preview: What to Expect

Hi,

Thanks for following up. We have now reproduced the configuration overwrite through the same WAN-online startup path on a GL-X3000 running v4.10.0 Beta 2.

The issue is caused by the firmware’s kmwan time-sync handler. Before time synchronization is marked as valid, it checks the first Chrony pool. If that pool is not time.cloudflare.com , the handler replaces it and adds the five default NTS servers again. The changes are then committed to /etc/config/chrony .

As a temporary workaround, you can keep a disabled Cloudflare pool as the first entry and add your preferred pool as a separate entry:

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 set chrony.@pool[0].hostname='time.cloudflare.com'
uci set chrony.@pool[0].disabled='1'

uci set chrony.custom_pool='pool'
uci set chrony.custom_pool.hostname='2.us.pool.ntp.org'
uci set chrony.custom_pool.maxpoll='12'
uci set chrony.custom_pool.iburst='yes'

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

Please note that 2.us.pool.ntp.org is a regular NTP pool, not an NTS server, so here we don't set nts='yes'.

We will check with the team to see how this type of behavior can be improved in future firmware.