You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that the address shown by timedatectl is different from the one reported in the journal by systemd-timesyncd, but appears to be the correct one shifted right by 32 bits:
NB: I have only tested this against the Debian version of systemd: I haven't attempted to rebuild systemd from upstream sources. I originally reported the problem to Debian, but a Debian developer suggested that I should report it upstream.
The text was updated successfully, but these errors were encountered:
bjh21
changed the title
timedatectl mangles displayed IPv6 address of NTP server
timedatesyncd mangles reported IPv6 address of NTP server
Dec 16, 2018
bjh21
changed the title
timedatesyncd mangles reported IPv6 address of NTP server
timesyncd mangles reported IPv6 address of NTP server
Dec 16, 2018
systemd version the issue has been seen with
Used distribution
Expected behaviour you didn't see
Unexpected behaviour you saw
Steps to reproduce the problem
1: Configure timesyncd to use an IPv6-capable NTP server. For instance, in
/etc/systemd/timesyncd.conf
write:2: Start or restart systemd-timesyncd:
3: Check that this has worked:
4: Ask timedatectl what it thinks the server IP address is:
Note that the address shown by timedatectl is different from the one reported in the journal by systemd-timesyncd, but appears to be the correct one shifted right by 32 bits:
NB: I have only tested this against the Debian version of systemd: I haven't attempted to rebuild systemd from upstream sources. I originally reported the problem to Debian, but a Debian developer suggested that I should report it upstream.
The text was updated successfully, but these errors were encountered: