Your message dated Fri, 26 Dec 2025 13:17:08 +0000
with message-id <[email protected]>
and subject line Bug#1123962: fixed in dhcpcd 1:10.1.0-11+deb13u2
has caused the Debian Bug report #1123962,
regarding dhcpcd-base: NTP is disabled by default, leading to unsynchronized
Debian installations
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1123962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1123962
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dhcpcd-base
Version: 1:10.1.0-11+deb13u1
Severity: serious
Justification: time is important
Control: affects -1 + systemd-timesyncd
Hi,
Spotted on a local CI: my bookworm hosts are NTP-synced, while my
trixie hosts are not. The installation procedure is the very same
though: netinst images and almost-all-default answers all the way.
This means having:
- ifupdown/isc-dhcp-client (dhclient) on bookworm;
- ifupdown/dhcpcd-base on trixie.
On bookworm hosts, lease information stored by dhclient include the
ntp-servers option, which trickles down to systemd-timesyncd via
/run/systemd/timesyncd.conf.d/01-dhclient.conf
On trixie hosts, that's not happening, /run/systemd/timesyncd.conf.d/
is not even present.
There's /usr/lib/dhcpcd/dhcpcd-hooks/50-timesyncd.conf though, which
would be doing the trick except… the default setting in dhcpcd-base is
the following:
| # Most distributions have NTP support.
| #option ntp_servers
This dates back to commit aa1a876387301cbfe636a3f737fde1baf7d00493 in
2017. I'm not sure what “Most distributions have NTP support.” means
in the first place, or why the default was changed, as there were no
explanations whatsoever…
See:
https://github.com/NetworkConfiguration/dhcpcd/commit/aa1a876387301cbfe636a3f737fde1baf7d00493
What I can say for sure though is that default installations that
wouldn't be able to access the default NTP servers (as in the ones
embedded in systemd-timesyncd, see also FallbackNTP=), e.g. because of
network-level restrictions, end up without NTP synchronization with the
default dhcpcd-base configuration, which is a HUGE functional regression
from bookworm.
Uncommenting the `option ntp_servers` line in /etc/dhcpcd.conf is
sufficient to fix the issue:
- /run/systemd/timesyncd.conf.d/ gets created;
- /run/systemd/timesyncd.conf.d/dhcpcd-ens18.dhcp.conf gets populated
with an NTP= entry matching what's provided by the DHCP server.
- `timedatectl` reports `System clock synchronized: yes` as well as
`NTP service: active` (as opposed to `no` and `active` resp.).
- `timedatectl show-timesync --all` now reports a non-empty
`SystemNTPServers=`.
- And of course the system isn't running anymore with one full minute
worth of offset (after 2 days of uptime)…
I strongly suggest adjusting the configuration to enable this option,
first in unstable, and then in trixie, making sure to coordinate with
the release team.
(I think that's orthogonal to #1087113 which I first glance could have
been related to this issue, except that (currently-disabled) test was
actively setting the option via the command line, so that's another
story I suppose.)
Cheers,
--
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/
--- End Message ---
--- Begin Message ---
Source: dhcpcd
Source-Version: 1:10.1.0-11+deb13u2
Done: Martin-Éric Racine <[email protected]>
We believe that the bug you reported is fixed in the latest version of
dhcpcd, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Martin-Éric Racine <[email protected]> (supplier of updated dhcpcd
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 25 Dec 2025 11:40:14 +0200
Source: dhcpcd
Architecture: source
Version: 1:10.1.0-11+deb13u2
Distribution: trixie
Urgency: medium
Maintainer: Martin-Éric Racine <[email protected]>
Changed-By: Martin-Éric Racine <[email protected]>
Closes: 1123962
Changes:
dhcpcd (1:10.1.0-11+deb13u2) trixie; urgency=medium
.
* [patches]
+ Uncomment 'ntp_servers' in dhcpcd.conf (Closes: #1123962).
Checksums-Sha1:
9d5036466cce9f642842ac97bc72c60366e87085 2164 dhcpcd_10.1.0-11+deb13u2.dsc
75217e4c9a8cb3b2579ee1b572c4086a2a59f275 22728
dhcpcd_10.1.0-11+deb13u2.debian.tar.xz
2b62c831f880f97ba1bd82cc03492c0b8cdb4ecc 5562
dhcpcd_10.1.0-11+deb13u2_source.buildinfo
Checksums-Sha256:
98b70740fcffc4e63637061ca7589083abdae20b1f4480cddc3d99a0a720159d 2164
dhcpcd_10.1.0-11+deb13u2.dsc
f7230c2254cafe81513ff989e19d30cbd3377d482a2dbb686b951c9c3904bd54 22728
dhcpcd_10.1.0-11+deb13u2.debian.tar.xz
8d31da2ef87b151e9cc88b9a097a422d526272e5280d1910de3de9887fdbca00 5562
dhcpcd_10.1.0-11+deb13u2_source.buildinfo
Files:
5c3d9b1f918ee6f3ab9396c77480886a 2164 net optional dhcpcd_10.1.0-11+deb13u2.dsc
fb679974358de683f97de0ca26a79472 22728 net optional
dhcpcd_10.1.0-11+deb13u2.debian.tar.xz
bc2f2ba2b7694c783ba4587fb23ceb77 5562 net optional
dhcpcd_10.1.0-11+deb13u2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmlNEkEACgkQrh+Cd8S0
17aarA//UVRAfnWdUUDjV1VsFaIzcg9c5cxRJMqXqTvFDw+hvkrjk9IF/AmGOyo3
dJCAGWOZLzAX3izK5j6tKYXTM89zeXheqaNu3CAx4STEtv/Bm/gOqD+mFv3peYgO
GeFBKLeXo2eviaRzwFBfUhBVBhiHxr/UOKbclmUgNKzNI1vOwzQVppynS789Z4S9
qnPYIIqscKD265uPsE5P8WQUDNiEAeTX7+GsUVb86e5dgGrwtP+wcIcDsGrBGwKn
L+5K8VMcJdWPQUEmUDoq27v22KYilZY0xUEilfqL7mjB/vUOoEDTMuScSReNakNC
irtivmkUFuif7jTwj6bC8yIcfSLHmdEA/t//VH14vF7Gt/1wCblPobxmZA7MEkxr
NZOn9TW/9B7BKhblsXTZIaGRM9yot+hpz5FUIePX8Gm0s38ggdmvcU2HgeteYGSW
dYfFsvWwlQWrbFp+jBZmGsYqRZ4pVvVYw2RVvXT7t4enziYIVlLJfRhl6zm3T+f/
zNgAMM3h1jU+0NUgx2A7mH+g9KH4wwqgwHufHs9A0ZLSe+5EugUWw0ajAkqoLEti
RumzhIis8RdBCeMvd3VY1ody6VbTkpmYAuvIVXaTDviNsv+EdIviUxGahlQAJtC0
D+l6xf6bB65VAdOmXjM3w0+kA6ArtJ2QkFnJtWZj34P8QP+mjdU=
=0V2j
-----END PGP SIGNATURE-----
pgpa7APlcOhTP.pgp
Description: PGP signature
--- End Message ---
