#1031539 network-manager: NM since 1.42.0-1 overwrites pre-existing dns-search entries

Package:
network-manager
Source:
network-manager
Description:
network management framework (daemon and userspace tools)
Submitter:
Christoph Anton Mitterer
Date:
2023-02-23 17:24:03 UTC
Severity:
normal
Tags:
#1031539#5
Date:
2023-02-18 01:05:27 UTC
From:
To:
Hey.

Just wanted to file this as a bug against ifupdown, but while writing I found out
that actually the upgrade from 1.40.10-1 to 1.42.0-1 causes this:

Ssince around the 10th of Feburary (and I've updated NM on the 11th) my dns-search
doesn't get added to resolvconf anymore.

Since years I have in /etc/network/interfaces:
   iface lo inet loopback
           dns-search      scientia.org

And while I also keep eth/wlan config in it, it's not enabled per default but
NetworkManager is used for that (because of the GUI stuff - talking about a laptop
here). So I have:
   allow-auto      lo
   #allow-hotplug  eth0 wlan0

So ifupdown does basically nothing, except for being there in case NM should have
troubles ... and setting my personal dns-search.
I also use the resolvconf package.

My DHCP sends me an additional fritz.box for the dns-search, which I fail to block ^^
But despite all this, for many years, my own dns-search was always added, too.
Now only the fritz.box remains.



It seems, that since 1.42.0-1 NM no longer just appends its own dns-search domains
(i.e. fritz.box) but also clears out any that are already there.
Downgrading "fixes" that.


Though it's of course arguable, whether this behaviour is actually proper or not.


Anyway... you guys know probably better if that's a desired change or some bug.
If the former, it would perhaps be nice if a NEWS.Debian entry could be added?


Thanks,
Chris.

#1031539#10
Date:
2023-02-18 08:04:00 UTC
From:
To:
Am 18.02.23 um 02:05 schrieb Christoph Anton Mitterer:

It doesn't "clear out" pre-existing dns-search entries, but no longer
adds one set via /etc/network/interfaces.

The ifupdown support is horribly buggy (and I do not recommend
managed=true, btw), so it's very well possible, there is a bug somewhere
in the the ifupdown plugin.

Anyway, please send me a verbose debug log of both NetworkManager 1.40.x
and 1.42.0

Michael

#1031539#15
Date:
2023-02-23 16:26:58 UTC
From:
To:
Hey Michael.
used now) seems to behave a bit different from how it's described in
the GUI (I think cinnamon also just uses network-manager-gnome?!).
There it says for v4 and v6: "Additional search domains:"

However, when setting mine there, I seem to no longer get the
"fritz.box" which the router advertises via DHCP.
Actually, I personally like that, cause I hate that some possibly
untrusted may set my dns-search.
Think I should report that usptream?

TBH, I wouldn't mind if you just leave it as is (I mean the "bug"). I
hadn't even remembered that I still use the plugin in some way (thought
it was deactivated since it's not in my plugins=keyfile)

Interestingly though, after my tests for your logs below, I got the
maintainer version of NetworkManager.conf installed:
[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false

With that my WiFi and Ethernet stops completely from working, they do
not even show up anymore (the whole sections) in the applet.
[main]
plugins=keyfile

[ifupdown]
managed=true

[logging]
level=DEBUG
domains=ALL


Attached are log files for the old and new versions.
I removed my system-connections and cleared some MAC-addresses for
privacy reasons.
If you need these, I'd rather send it to you in private.

But as I've said... don't waste too much time on this :-)


Thanks	,
Chris.

#1031539#20
Date:
2023-02-23 17:21:00 UTC
From:
To:
Am 18.02.23 um 02:05 schrieb Christoph Anton Mitterer:
tried this setup with 1.40.10 but can *not* confirm that scientia.org is
added to /etc/resolv.conf this way.

And from the log you sent, it seems you use systemd-resolved.
So you have an interesting mix/setup of managed=true, NM and resolved
which is probably something you need to debug locally or provide
step-by-step instructions in a minimal environment how this can be
reproduced.

Maybe it helps, if you remove some of the involved components, like
resolved/resolvconf

Michael