Your message dated Thu, 12 Jun 2025 09:50:13 +0000
with message-id <[email protected]>
and subject line Bug#1107683: fixed in dhcpcd 1:10.2.4-2
has caused the Debian Bug report #1107683,
regarding dhcpcd is enabled at install by default which conflicts with network 
manager and breaks dns
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.)


-- 
1107683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107683
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dhcpcd
Version: 1:10.1.0-11
Severity: normal

I connect to a network and immediately run "resolvectl" and see the following:

Link 3 (wifi)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.0.17
       DNS Servers: 192.168.0.17
        DNS Domain: REDACTED
     Default Route: yes

I run it again a couple of seconds later and that is gone.  I add it again
manually with the command "resolvectl dns wifi 192.168.0.17" and it is good
for a second or two and then goes away again.  The only way I can keep it
going is using watch(1) to repeatedly run resolvectl to keep adding it back
as dhcpcd keeps removing it.  It was not obvious that dhcpcd was doing this
in the background.  Also it doesn't happen on all networks for unknown
reasons, it seems to happen with isc-dhcp-server but not with kea but I have
a small sample size.

dhcpcd should do at least one of the following:

1) Take the same DNS data from dhcp as network-manager and use the same
settings.
2) Realise that something else configured an interface and do nothing with it.
3) Not be run by default on all interfaces.

-- System Information:
Debian Release: 13.0
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.27-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages dhcpcd depends on:
ii  dhcpcd-base                1:10.1.0-11
ii  lsb-base                   11.6
ii  sysvinit-utils [lsb-base]  3.14-4

Versions of packages dhcpcd recommends:
ii  wpasupplicant  2:2.10-24

Versions of packages dhcpcd suggests:
pn  dhcpcd-gtk  <none>

-- Configuration Files:
/etc/init.d/dhcpcd [Errno 13] Permission denied: '/etc/init.d/dhcpcd'

-- debconf-show failed

--- End Message ---
--- Begin Message ---
Source: dhcpcd
Source-Version: 1:10.2.4-2
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, 12 Jun 2025 11:03:25 +0300
Source: dhcpcd
Architecture: source
Version: 1:10.2.4-2
Distribution: experimental
Urgency: medium
Maintainer: Martin-Éric Racine <[email protected]>
Changed-By: Martin-Éric Racine <[email protected]>
Closes: 1107683
Changes:
 dhcpcd (1:10.2.4-2) experimental; urgency=medium
 .
   * dhcpcd: Conflicts: network-manager (Closes: #1107683).
     This ensures that a daemonized dhcpcd and network-manager won't install on
     the same host. Meanwhile, dhcpcd-base itself does nothing without ifupdown
     or network-manager's dhcpcd backend.
Checksums-Sha1:
 7670be048237f18ea891fe321fb88e493ccec3b4 2372 dhcpcd_10.2.4-2.dsc
 403b2c0216797f71ff173ce6590fe235e8ae4b4f 19456 dhcpcd_10.2.4-2.debian.tar.xz
 2cccb018708772bf84a33b2fcd15ec0ffe460c91 5518 dhcpcd_10.2.4-2_source.buildinfo
Checksums-Sha256:
 5680d7edbc13e9d4793b78c1fcfff781bd88a73e0a7fa04c725bba81d4ce7e83 2372 
dhcpcd_10.2.4-2.dsc
 8fdb12a47fb847b22e53dbf4a136579df7d26130202e1c51e783300507c6c153 19456 
dhcpcd_10.2.4-2.debian.tar.xz
 d995c49472e46b16e3f3f534bd34bca5cc545df4bd19f1dfe7c813335f25db21 5518 
dhcpcd_10.2.4-2_source.buildinfo
Files:
 c296cf35965c97af4e44c6831940fbf7 2372 net optional dhcpcd_10.2.4-2.dsc
 a2512ee20c329c707ed07d68192a3b5a 19456 net optional 
dhcpcd_10.2.4-2.debian.tar.xz
 35c3087b2d3dfcbf69df4c5b3792f375 5518 net optional 
dhcpcd_10.2.4-2_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmhKnqoACgkQrh+Cd8S0
17axaw//cB/M1srnWvai4NfqWTnK9sf3T3jwUgfDBDmZRqBLfeGVYoZRy92VVnQd
y6e5JXZG9HUbRcQGeEsT7ingHRutw30WGHVU/iLx2mTFFoEUin7rOSUIrr1EKW6B
oWfL5vXzO5/6lMFtGwl9SmRbSMvXTmesE1h4yha+0a5Y1J8+/X5cf6sa+M8SVjbc
Q9aCbrMF0bSyay5JXaOgljE6XdfuVpO5ggkdYOzVh7ZeZIYkRzbuZNYX8BpCopbW
e6GZRcf7MjjfNsMr+u12c/xTeaFrekuy5XwZ0yggSUUUUx8MZOUAD550ck78JtbZ
E6rVdEvmwUrIX/V067TKUcT1vh1fHvtHf2qQQzEZj+/T6Hj74b8cwwiUZHIi5Tu8
25WWIpdJiOioIwrri22/2HOOlq1dg6MzEvb3lSVAD8vZ4rkIx1OcUZVx8SAUrsE/
b1WpnwjxshLey+OKj4BgAgdXL7IIGqcPTc7Zbr4/jxHREUd97f1Z/754s2+OwBKE
OFvtRej+Fy5fXDenK/xycfdhq/bjQJ9x/iPLuaX9qTHNlx4CHGiC6FdRq7yEl07H
KhMNDjWOHwZNbtiytoWh/68/57fLqOaNptB+xaiAMySozcFfkxKGeLdgSg49/hgd
kgrO8hIhfKf1IAM6UIml6B1oTZJFgoVYufQQPFR2qW85khQKVHw=
=URWe
-----END PGP SIGNATURE-----

Attachment: pgpQeXRXWdS3y.pgp
Description: PGP signature


--- End Message ---

Reply via email to