Bug#916516: systemd: timedatectl mangles IPv6 address of NTP server
Am 15.12.18 um 15:12 schrieb Ben Harris: > Control: forwarded -1 https://github.com/systemd/systemd/issues/11169 > > On Sat, 15 Dec 2018, Michael Biebl wrote: > >> Since this doesn't look like a Debian specific problem, would you mind >> filing this issue upstream at >> https://github.com/systemd/systemd/issues > > Done: https://github.com/systemd/systemd/issues/11169 > Perfect, thanks -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#916516: systemd: timedatectl mangles IPv6 address of NTP server
Control: forwarded -1 https://github.com/systemd/systemd/issues/11169 On Sat, 15 Dec 2018, Michael Biebl wrote: Since this doesn't look like a Debian specific problem, would you mind filing this issue upstream at https://github.com/systemd/systemd/issues Done: https://github.com/systemd/systemd/issues/11169 -- Ben Harris
Bug#916516: systemd: timedatectl mangles IPv6 address of NTP server
Hi Ben Am 15.12.18 um 13:22 schrieb Ben Harris: > Indeed, the same problem occurs if I explicitly specify the IPv6 address: > > wraith:~# grep ^NTP= /etc/systemd/timesyncd.conf > NTP=2001:630:212:8::123:20 > > wraith:~# timedatectl timesync-status | head -1 > Server: ::2001:630:212:8:0:0 (2001:630:212:8::123:20) > Might indeed be a presentation issue in timedatectl or more possibly a bug in the D-Bus interface. Since this doesn't look like a Debian specific problem, would you mind filing this issue upstream at https://github.com/systemd/systemd/issues Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#916516: systemd: timedatectl mangles IPv6 address of NTP server
On Sat, 15 Dec 2018, Michael Biebl wrote: Am 15.12.18 um 11:24 schrieb Ben Harris: Package: systemd Version: 239-13 Severity: minor Tags: ipv6 Dear Maintainer, I have configured timesyncd to use sntp.cam.ac.uk as an NTP server (see configuration below). That name resolves to 2001:630:212:8::123:20. It resolves to 131.111.8.28 here. Do you get no IPv4 address for sntp.cam.ac.uk? The name resolves to both an IPv4 and an IPv6 address. On my system, timesyncd prefers the IPv6 address, so I think the presence or otherwise of the IPv4 address is irrelevant to the display bug. Indeed, the same problem occurs if I explicitly specify the IPv6 address: wraith:~# grep ^NTP= /etc/systemd/timesyncd.conf NTP=2001:630:212:8::123:20 wraith:~# timedatectl timesync-status | head -1 Server: ::2001:630:212:8:0:0 (2001:630:212:8::123:20) -- Ben Harris
Bug#916516: systemd: timedatectl mangles IPv6 address of NTP server
Am 15.12.18 um 11:24 schrieb Ben Harris: > Package: systemd > Version: 239-13 > Severity: minor > Tags: ipv6 > > Dear Maintainer, > > I have configured timesyncd to use sntp.cam.ac.uk as an NTP server (see > configuration below). That name resolves to 2001:630:212:8::123:20. It resolves to 131.111.8.28 here. Do you get no IPv4 address for sntp.cam.ac.uk? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#916516: systemd: timedatectl mangles IPv6 address of NTP server
Package: systemd Version: 239-13 Severity: minor Tags: ipv6 Dear Maintainer, I have configured timesyncd to use sntp.cam.ac.uk as an NTP server (see configuration below). That name resolves to 2001:630:212:8::123:20. However, if I run "timedatectl timesync-status" I get a different address: wraith:~$ timedatectl timesync-status | head -1 Server: ::2001:630:212:8:0:0 (sntp.cam.ac.uk) Something similar happens if I run "timedatectl show-timesync": wraith:~$ timedatectl show-timesync | grep ^ServerAddress= ServerAddress=::2001:630:212:8:0:0 It looks like the NTP server address is being shifted right by 32 bits: right: 2001:0630:0212:0008:::0123:0020 wrong: ::2001:0630:0212:0008:: Since timesyncd is working (and ::2001:630:212:8:0:0 isn't a working NTP server), it seems that the problem is only in the display of IPv6 addresses in timedatectl. -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 4.18.0-1-686-pae (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemd depends on: ii adduser 3.118 ii libacl1 2.2.52-3+b1 ii libapparmor1 2.13.1-3+b1 ii libaudit11:2.8.4-2 ii libblkid12.32.1-0.1 ii libc62.27-8 ii libcap2 1:2.25-1.2 ii libcryptsetup12 2:2.0.5-2 ii libgcrypt20 1.8.4-4 ii libgnutls30 3.5.19-1+b1 ii libgpg-error01.32-3 ii libidn11 1.33-2.2 ii libip4tc01.8.2-2 ii libkmod2 25-2 ii liblz4-1 1.8.2-1 ii liblzma5 5.2.2-1.3 ii libmount12.32.1-0.1 ii libpam0g 1.1.8-3.8 ii libseccomp2 2.3.3-3 ii libselinux1 2.8-1+b1 ii libsystemd0 239-13 ii mount2.32.1-0.1 ii procps 2:3.3.15-2 ii util-linux 2.32.1-0.1 Versions of packages systemd recommends: ii dbus1.12.10-1 ii libpam-systemd 239-13 Versions of packages systemd suggests: ii policykit-10.105-22 pn systemd-container Versions of packages systemd is related to: pn dracut ii initramfs-tools 0.132 ii udev 239-13 -- Configuration Files: /etc/systemd/timesyncd.conf changed: [Time] NTP=sntp.cam.ac.uk -- no debconf information
