Your message dated Sat, 13 Aug 2022 14:49:10 +0000
with message-id <[email protected]>
and subject line Bug#1006724: fixed in network-manager 1.38.4-1
has caused the Debian Bug report #1006724,
regarding network-manager: DNS information not cleaned correctly when switching 
of networks
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.)


-- 
1006724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006724
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 1.36.0-2
Severity: normal

  Hi,

  When I change of location with my laptop (putting it in suspend-to-ram
during the transfert), I found several times that the network become slow.
  Looking more in details, I discovered that network-manager does not cleanup
correctly the DNS information of the previous (wired) connection. As I have
specific settings, the network-manager connection is not the same at work and
at home (specific Mac fixed at home, forced fixed IPv6 at work, ...)
  The DNS information still present in /etc/resolv.conf comes from DHCP
information (at work or at home) that are kept when the connexion is switched
by network-manager.
  Even when I disable the connexion, the DNS information are kept.

  Here is the current situation (with anonymisation of IP and dnsdomain) where
I manually disable the wired connexion (so I do not have network access for
now):
vdanjean@eyak:/run/resolvconf/interface$ nmcli 
docker0: connecté à docker0
        "docker0"
        bridge, XX:XX:XX:XX:XX:5D, sw, mtu 1500
        inet4 172.17.0.1/16
        route4 169.254.0.0/16 metric 1000
        route4 172.17.0.0/16 metric 0
        inet6 fe80::42:45ff:fe7a:55d/64

3C:DC:BC:D0:26:00: déconnecté
        "Silk"
        1 connexion disponible
        bt (bluez), 3C:DC:BC:D0:26:00, hw

enx98fc84e13b03: déconnecté
        "Realtek RTL8153"
        2 connexions disponibles
        ethernet (r8152), XX:XX:XX:XX:XX:03, connexion automatique, hw, mtu 1500

en-wifi: déconnecté
        "Intel 8265 / 8275"
        3 connexions disponibles
        wifi (iwlwifi), XX:XX:XX:XX:XX:29, connexion automatique, hw, mtu 1500

p2p-dev-en-wifi: déconnecté
        "p2p-dev-en-wifi"
        wifi-p2p, hw

veth315cdd3: non-géré
        "veth315cdd3"
        ethernet (veth), XX:XX:XX:XX:XX:A7, sw, mtu 1500

lo: non-géré
        "lo"
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536

DNS configuration:
        servers: AAA.AAA.24.30 BBB.BBB.1.22
        domains: mywork1.fr mywork2.fr

        servers: AAAA:AAAA:AAAA:AAAA:4 BBBB:BBBB:BBBB:BBBB::7

        servers: AAA.AAA.24.30 BBB.BBB.1.22
        domains: mywork1.fr mywork2.fr

        servers: AAAA:AAAA:AAAA:AAAA:4 BBBB:BBBB:BBBB:BBBB::7

        servers: AAA.AAA.24.30 BBB.BBB.1.22
        domains: mywork1.fr mywork2.fr

        servers: AAAA:AAAA:AAAA:AAAA:4 BBBB:BBBB:BBBB:BBBB::7

Utilisez « nmcli device show » pour obtenir des informations complètes sur les >

Consultez les pages de manuel nmcli(1) et nmcli-examples(7) pour les détails co>
vdanjean@eyak:/run/resolvconf/interface$ cat NetworkManager 
search mywork1.fr mywork2.fr
nameserver AAA.AAA.24.30
nameserver BBB.BBB.1.22
nameserver AAAA:AAAA:AAAA:AAAA:4
nameserver BBBB:BBBB:BBBB:BBBB::7
vdanjean@eyak:/run/resolvconf/interface$ cat /etc/resolv.conf 
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "resolvectl status" to see details about the actual nameservers.

nameserver AAA.AAA.24.30
nameserver BBB.BBB.1.22
nameserver AAAA:AAAA:AAAA:AAAA:4
search mywork1.fr mywork2.fr


Only if I restart NetworkManager, then these outdated informations go out:
vdanjean@eyak:/run/resolvconf/interface$ sudo systemctl restart NetworkManager
vdanjean@eyak:/run/resolvconf/interface$ cat NetworkManager 
search home.fr sub1.home.fr sub2.home.fr
nameserver 10.77.0.2
nameserver fd77:53::1
nameserver 192.168.77.1
vdanjean@eyak:/run/resolvconf/interface$

If I disable my home connextion (that NetworkManager connects automatically on 
restart),
I come back to the previous nmcli state (ie no active connexion) as before, 
but, this time,
/run/resolvconf/interface/NetworkManager do not exists and the "DNS
configuration:" section in nmcli is not printed.



  So, it seems that sometimes NetworkManager forgets to clean DNS information
(as shown by nmcli) when switching between networks connexion. As manual
restart of the NetworkManager deamon allows one to fix that.


  Regards,
    Vincent




-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'oldstable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), 
(500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armel, mipsel

Kernel: Linux 5.16.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages network-manager depends on:
ii  adduser          3.118
ii  dbus             1.14.0-1
ii  libaudit1        1:3.0.7-1
ii  libbluetooth3    5.62-2
ii  libc6            2.33-7
ii  libcurl3-gnutls  7.81.0-1
ii  libglib2.0-0     2.70.4-1
ii  libgnutls30      3.7.3-4+b1
ii  libjansson4      2.13.1-1.1
ii  libmm-glib0      1.18.6-2
ii  libndp0          1.6-1+b1
ii  libnewt0.52      0.52.21-5+b1
ii  libnm0           1.36.0-2
ii  libpsl5          0.21.0-1.2
ii  libreadline8     8.1.2-1
ii  libselinux1      3.3-1+b1
ii  libsystemd0      250.3-2
ii  libteamdctl0     1.31-1
ii  libudev1         250.3-2
ii  policykit-1      0.105-33
ii  udev             250.3-2

Versions of packages network-manager recommends:
ii  dnsmasq-base [dnsmasq-base]  2.86-1.1
ii  libpam-systemd               250.3-2
ii  modemmanager                 1.18.6-2
ii  ppp                          2.4.9-1+1
ii  wireless-regdb               2021.08.28-1
ii  wpasupplicant                2:2.9.0-23

Versions of packages network-manager suggests:
ii  iptables       1.8.7-1
pn  libteam-utils  <none>

Versions of packages network-manager is related to:
ii  isc-dhcp-client  4.4.2-P1-1

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: network-manager
Source-Version: 1.38.4-1
Done: Michael Biebl <[email protected]>

We believe that the bug you reported is fixed in the latest version of
network-manager, 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.
Michael Biebl <[email protected]> (supplier of updated network-manager 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: SHA256

Format: 1.8
Date: Sat, 13 Aug 2022 15:51:32 +0200
Source: network-manager
Architecture: source
Version: 1.38.4-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 
<[email protected]>
Changed-By: Michael Biebl <[email protected]>
Closes: 1006724
Changes:
 network-manager (1.38.4-1) unstable; urgency=medium
 .
   * New upstream version 1.38.4
     - core: avoid stale entries in the DNS manager for non-virtual devices
       (Closes: #1006724)
   * Clean up build dependencies
Checksums-Sha1:
 e79686e0f4f52ec182981ccb6e21a36ebd139332 3045 network-manager_1.38.4-1.dsc
 1401d1920aa561bd137fb3fa466f139790d3d4ae 5446860 
network-manager_1.38.4.orig.tar.xz
 cd448aa28e719a201e2ba163951db41919af7c6b 46856 
network-manager_1.38.4-1.debian.tar.xz
 0a81fce226976ecad4f3aa9efb2e88facae4d29a 8895 
network-manager_1.38.4-1_source.buildinfo
Checksums-Sha256:
 d4543c18c9fba0dfc18eeafdeeac38fedbb1e3529876a7b1128cfb1fcabc54fa 3045 
network-manager_1.38.4-1.dsc
 841f64d41776aadd92b151f47e50f62be8a0611a9056fe6bf81881024e6a96c5 5446860 
network-manager_1.38.4.orig.tar.xz
 b8c32ea554fa2c8ce1186d00f7a27ba2f1f898c4cee3ee248818778818622571 46856 
network-manager_1.38.4-1.debian.tar.xz
 944d0abd00b538ee245dc99a7e9e5cf51e887cf1861c2e0b0a34447f9ab1d37e 8895 
network-manager_1.38.4-1_source.buildinfo
Files:
 8f1e7f8e920cd30b852b5028359df4a9 3045 net optional network-manager_1.38.4-1.dsc
 eaaefa0da3f56c84aa1d9324cffb89ff 5446860 net optional 
network-manager_1.38.4.orig.tar.xz
 6dcf59c8a687f19cb8643d526234b301 46856 net optional 
network-manager_1.38.4-1.debian.tar.xz
 29c956896d87c022c56ad4b137920dd5 8895 net optional 
network-manager_1.38.4-1_source.buildinfo

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

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAmL3rQIACgkQauHfDWCP
ItwcjA//S1ZTD7Xji0c8Z7LNGqA3yf4MKuzol+ARhhYMI4RmtUXiNE0SFOApHov1
8Rq+N/rJwgZ3vWNg6QYYJt6eJ/38pIOGJ7CTkb/hJ53/TKfKPS8OsEjP7qhApdU9
r7EbFTf9N++TPnLNEfbNEUgK+q3zNbmLBxxejp5sAL/IhNr1oiubHHUU66lbJXHj
BUm2nE4CHWvrzg5jtU3MLMcS0GLeUJSZ5CW6FLSxjraNo+TUHdC3qaS1fScC61TD
ffrmw49wO/X0CMmdpsRJ5bUh/9R5FKQOS0Q/lbf7nGsxj28RhN/I7+IYZ3I4EvnI
zMSArv4B8geuB7X6AKV4BRbrbK9nRRI4Xz44jIWpu55O/dbMrmFK+Mc+kqB4eN1R
ZvwU7edFKjuftHAhqXs1bGZbrqu98gdzefJHd6NYz1buaUl1PC7yUk4QdxLJPu8G
V2mY4d40fAedCWseLo3vtiaAH/sBM7K4nv303mF37CJrj6xQCqYEWipG5oVZREcB
c3ON4hSNZlFhd7rZv68IrFSvqEYDTRAoZMuOl3b9Z3qYDIcPscpuivdXvTt0e0Ce
Ysk1FHoOGYz04CulkaZiCn9Ppg3pbGA3dmQFS7HHvEg7HekXSVKZ/1E6DfaXkWSn
XL3O5S3tYCdyY382CrM5pE9EyzCQ4AW8UqA7BdVz9/xSnWoIf3o=
=vS0r
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to