N2+ Impervious to Timekeeping Applications

[Quantum]

Armbian current:

 

It seems that the N2+ is [i]immune[/i] to Chrony and systemd-timesyncd.  The only way I can set the date/time is manually through date -s.

 

# systemctl status systemd-timesyncd
● systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; preset: enabled)
     Active: active (running) since Mon 2025-11-24 13:06:59 PST; 31min ago
 Invocation: 50da85c1116348dbbd83cca270da6ff8
       Docs: man:systemd-timesyncd.service(8)
   Main PID: 1185 (systemd-timesyn)
     Status: "Idle."
      Tasks: 2 (limit: 4227)
     Memory: 1.6M (peak: 2.3M)
        CPU: 79ms
     CGroup: /system.slice/systemd-timesyncd.service
             └─1185 /usr/lib/systemd/systemd-timesyncd

Nov 24 13:06:59 lab systemd-timesyncd[1185]: System clock time advanced to recorded timestamp: Mon 2025-11-24 13:06:59 PST
Nov 24 13:06:57 lab systemd-timesyncd[1185]: Network configuration changed, trying to establish connection.
Nov 24 13:06:57 lab systemd-timesyncd[1185]: Network configuration changed, trying to establish connection.
Nov 24 13:06:57 lab systemd-timesyncd[1185]: Network configuration changed, trying to establish connection.
Nov 24 13:07:01 lab systemd-timesyncd[1185]: Network configuration changed, trying to establish connection.
Nov 24 13:07:11 lab systemd-timesyncd[1185]: Timed out waiting for reply from 10.2.1.10:123 (10.2.1.10).

 

No, the network configuration has na-ha-hot, changed, Spastic.  I see via tcpdump, the request going out 123/udp and the response, coming back.  The information arrives at the destination.  But it hits a hard rock head and disintegrates.  Of course if it can't set the system clock, there's no sense trying to make it set the RTC.

 

How is this possible in the 21st Century?  Does time, no longer matter to Gen Z?  Is this the precursor to the Apocalypse?  Should I convert to religion and start praying?

Edited 1 hour ago by Quantum