Bug#996753: systemd: After bullseye upgrade: DNS does not work after changing wireless networks or suspending laptop
Thanks for the clarification, and I will try those steps. I have never reconfigured my networking beyond the default settings, so could this be an upgrade issue? -- Joel Cross j...@kazbak.co.uk On Mon, 18 Oct 2021, at 11:18 PM, Michael Biebl wrote: > Am 18.10.2021 um 19:51 schrieb Joel Cross: >> $ cat /etc/network/interfaces >> source-directory /etc/network/interfaces.d >> $ ls /etc/network/interfaces.d >> setup >> $ cat /etc/network/interfaces.d/setup >> auto lo >> iface lo inet loopback >> >> auto eth0 >> iface eth0 inet dhcp > > So, you have eth0 configured by ifupdown, at the same time you use > NetworkManager to configure your network. So they stomp upon each other > and depending on the order in which they are started, it's likely they > mess up each others configuration > > If you want to use NetworkManager, please remove > /etc/network/interfaces.d/setup > > If you want to use ifupdown, my advice would be to either uninstall the > network-manager package or disable the NetworkManager.service > >> $ 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 127.0.0.1 > > So, you apparently use resolvconf as well, adding another tool to the > mix and a local (caching) dns server. Another moving part. > >> $ ls -la /etc/resolv.conf >> lrwxrwxrwx 1 root root 29 Sep 29 16:34 /etc/resolv.conf -> >> ../run/resolvconf/resolv.conf > >> $ cat /run/NetworkManager/resolv.conf >> # Generated by NetworkManager >> nameserver 192.168.1.1 >> > > That looks ok. > > > All in all, this looks like a local configuration issue and neither an > issue in systemd, ifupdown or NetworkManager. > > > Attachments: > * OpenPGP_signature
Bug#996753: systemd: After bullseye upgrade: DNS does not work after changing wireless networks or suspending laptop
$ cat /etc/network/interfaces source-directory /etc/network/interfaces.d $ ls /etc/network/interfaces.d setup $ cat /etc/network/interfaces.d/setup auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp $ 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 127.0.0.1 $ ls -la /etc/resolv.conf lrwxrwxrwx 1 root root 29 Sep 29 16:34 /etc/resolv.conf -> ../run/resolvconf/resolv.conf $ cat /run/NetworkManager/resolv.conf # Generated by NetworkManager nameserver 192.168.1.1
Bug#996753: systemd: After bullseye upgrade: DNS does not work after changing wireless networks or suspending laptop
Am 18.10.21 um 10:03 schrieb Joel Cross: Thanks Michael. To whom it may concern, I should have mentioned that I use network manager to control my wireless networks - presumably this uses ifupdown under the hood, but I'm not 100% on that It doesn't. It can read ifupdown configuration to some extent and thus avoid managing interfaces which are also managed by ifupdown, but that's about it. Can you share the contents of your /etc/network/interfaces /etc/network/interfaces.d/* How does your /etc/resolv.conf look like ? cat /etc/resolv.conf ls -la /etc/resolv.conf cat /run/NetworkManager/resolv.conf OpenPGP_signature Description: OpenPGP digital signature
Bug#996753: systemd: After bullseye upgrade: DNS does not work after changing wireless networks or suspending laptop
Thanks Michael. To whom it may concern, I should have mentioned that I use network manager to control my wireless networks - presumably this uses ifupdown under the hood, but I'm not 100% on that -- Joel Cross j...@kazbak.co.uk On Mon, 18 Oct 2021, at 10:59 AM, Michael Biebl wrote: > Control: reassign -1 ifupdown > > Am 18.10.21 um 09:42 schrieb Joel Cross: >> Package: systemd >> Version: 249.5-1 >> Severity: important >> X-Debbugs-Cc: joel+debb...@kazbak.co.uk >> >> Dear Maintainer, >> >> I run a testing/sid setup. After a recent PackageKit upgrade (it might have >> been the 11.0 or 11.1 upgrade) there are serious usability issues with the >> wifi. To reproduce (on my system): >> >> * Switch the computer on and connect to a wireless network -> everything is >> fine >> * Switch to a different wireless network -> it is possible to ping IP >> addresses >> but DNS resolution does not work. Changing /etc/resolv.conf has no effect >> >> Additionally, running 'resolvctl status' yields this error: >> Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not >> found. >> (I mention this because it might be related) > > This means systemd-resolved is not enabled, i.e. you don't use > systemd-resolved. Which is fine, you don't need systemd-resolved > (currently it defaults to disabled anyway). > >> This has been a consistent issue since the upgrade, meaning I need to restart >> my laptop multiple times per day just to get a working internet connection. I >> have tried 'systemctl restart networking' (which fails with another error) >> and >> multiple other ways, but the only reliable fix I have found is to restart my >> entire system. > > networking.service is provided by ifupdown, a separate package not under > systemd's control. > > Assuming that you control your network configuration with ifupdown, I'm > going to reassign the bug report accordingly. It's more likely that they > can help you debug your network related problems. > > If it turns out to be an actual issue in systemd, please reassign back. > > Michael > > > Attachments: > * OpenPGP_signature
Bug#996753: systemd: After bullseye upgrade: DNS does not work after changing wireless networks or suspending laptop
Control: reassign -1 ifupdown Am 18.10.21 um 09:42 schrieb Joel Cross: Package: systemd Version: 249.5-1 Severity: important X-Debbugs-Cc: joel+debb...@kazbak.co.uk Dear Maintainer, I run a testing/sid setup. After a recent PackageKit upgrade (it might have been the 11.0 or 11.1 upgrade) there are serious usability issues with the wifi. To reproduce (on my system): * Switch the computer on and connect to a wireless network -> everything is fine * Switch to a different wireless network -> it is possible to ping IP addresses but DNS resolution does not work. Changing /etc/resolv.conf has no effect Additionally, running 'resolvctl status' yields this error: Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found. (I mention this because it might be related) This means systemd-resolved is not enabled, i.e. you don't use systemd-resolved. Which is fine, you don't need systemd-resolved (currently it defaults to disabled anyway). This has been a consistent issue since the upgrade, meaning I need to restart my laptop multiple times per day just to get a working internet connection. I have tried 'systemctl restart networking' (which fails with another error) and multiple other ways, but the only reliable fix I have found is to restart my entire system. networking.service is provided by ifupdown, a separate package not under systemd's control. Assuming that you control your network configuration with ifupdown, I'm going to reassign the bug report accordingly. It's more likely that they can help you debug your network related problems. If it turns out to be an actual issue in systemd, please reassign back. Michael OpenPGP_signature Description: OpenPGP digital signature
