Bug 466298

Summary:	KDE Network Manager shows incorrect Primary Nameserver
Product:	[Plasma] plasma-nm	Reporter:	qtm4ig
Component:	applet	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED UPSTREAM
Severity:	minor	CC:	fkrueger, nate, shawn
Priority:	NOR
Version:	5.27.1
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	NetworkManager 1.42

Description qtm4ig 2023-02-23 11:16:29 UTC

STEPS TO REPRODUCE
1. upgrade networkmanager to 1.42.0 and/or kde plasma to 5.27.1 versions
2. open kde NM tray applet

OBSERVED RESULT
Primary Nameserver is not valid (in my case 8.116.124.209)

EXPECTED RESULT
Primary Nameserver must be valid as in IP4.DNS[1] value from nmlci (in my case 192.168.1.1)

SOFTWARE/OS VERSIONS
Linux: archlinux with 6.1.12 kernel
KDE Plasma Version: 5.27.1
KDE Frameworks Version:  5.103.0
Qt Version: 5.15.8
NetworkManager:  1.42.0

ADDITIONAL INFORMATION
https://bbs.archlinux.org/viewtopic.php?id=283573

Comment 1 Shawn 2023-02-23 17:13:22 UTC

Seeing this as well with the same software versions as qtm4ig@gmail.com except Networkmanager updated to 1.42.2-1 today with the same result.

Also noticed the IP displayed in IPv4 Primary Nameserver changes with every reboot.  Mine is displaying 40.211.92.136 (Eli Lilly in Germany), however I've also seen IPs from the USPS and various other organizations.

Comment 2 Frank Kruger 2023-02-23 17:37:32 UTC

Created attachment 156653 [details]
NetworkManager 1.42

I have been experiencing the same issue with openSUSE Tumbleweed, KDE Plasma 5.27.1 and NM 1.42 (see attachment). 
> nmcli connection show wifi | grep -i ip4.dns
IP4.DNS[1]:                             192.168.0.1
gives the correct nameserver, consistent with /etc/resolv.conf. Restart of NM changes the primary nameserver again. It is not clear to me whether plasma-nm5 or NM  is the culprit here. Any idea?

Comment 3 Nate Graham 2023-02-24 19:46:36 UTC

Definitely a Networkmanager bug. Please report upstream. Thanks!

Comment 4 Frank Kruger 2023-03-11 06:56:57 UTC

JFYI: The issue is solved for me with NM 1.42.4.