On Sun, 22 Nov 2020, Matteo F. Vescovi wrote: > On 2020-11-04 at 21:09 (+01), Cristian Ionescu-Idbohrn wrote: > > [...] > > > IMO, my remarks and comments are all _but_ snide and stupid. The > > problem here, as I see it, is this maintainer's _arrogant_ attitude. > > Michael, sorry to say, but Cristian is right: > > I see no snide and stupid comments to the bug report and I'm > actually affected by this weird behaviour since a week or so, I must > admit.
Yes, I'm not alone. I noticed this odd behaviour months ago but did not report it, as I expected that kind of _arrogant_ reaction. > I'm still digging in to find the culprit (possibly, a particular > version of NM or MM that introduced the issue) For me, it does not appear ModemManager has anything to do with this, but I can't rule that out. > but I need some more tests with alternative setups to fully > understand the situation (seems like systems with both Wi-Fi and > WWAN are affected). I can reproduce this in another way too. My laptop has both a wifi and a wired chip. When I stick in the cable, the same problem occurs: I loose the DNS configuration in /etc/resolv.conf. I can add that manually, but that should _not_ be expected. Another peculiar behaviour is that if I poweroff connected to the wifi and startup wired connected, I end up having to disconnect the cable and connect it back again to be able to get things (sort of) working again. In both cases (wired/wireless) I rely on the router's DHCP to provide the proper DNS configuration. That may need another bug report, if anyone else is able to reproduce. Cheers, -- Cristian