Systemd-timesyncd "time out waiting for reply" Topic is solved

[SimonFili]

@trendy Thanks for the tips for tcpdump... been a decade since I used that!

It showed

1) that my local router does not respond to NTP, like I thought it would
2) Going by to north-america.pool.ntp.org it worked! Never did before?

07:38:23.343061 IP 192.168.10.3.42408 > paladin.latt.net.123: NTPv4, Client, length 48
07:38:23.429515 IP paladin.latt.net.123 > 192.168.10.3.42408: NTPv4, Server, length 48

So unsure why it did not work before.

Then I did a restart of network time sync:

root@DietPi:~# /boot/dietpi/func/run_ntpd
[ OK ] Network time sync | Completed

But tcpdump did not show any traffic after this

Then tried systemctl restart systemd-timesyncd.service
tcpdump showed traffic and good connection:

07:44:34.299059 IP 192.168.10.3.60448 > titan.crash-override.org.123: NTPv4, Client, length 48
07:44:34.352816 IP titan.crash-override.org.123 > 192.168.10.3.60448: NTPv4, Server, length 48

[trendy]

1) that my local router does not respond to NTP, like I thought it would

Maybe the ntp is down or listening to another port? There are different time servers available listening to different ports.

[Joulinar]

On some router NTP server functionality needs to be activated explicitly.

But as I understood, NTP time sync is working with global NTP server now.

[WarHawk]

Hi

did you tried to change NTP server to the Global one pool.ntp.org? do you know if your internet router is providing NTP functionality as well? If yes, you could set NTP server to your Gateway.

I always change my NTP servers to pool.ntp.org, it automatically finds servers...good call on this!

[Joulinar]

Personally I'm using my internet router. Much faster