Bug 394869 - network connection failure after setting custom DNS, resetting DNS fails
Summary: network connection failure after setting custom DNS, resetting DNS fails
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-networkmanager-qt
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.44.0
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-30 17:44 UTC by Elkasir
Modified: 2022-12-26 05:21 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Elkasir 2018-05-30 17:44:14 UTC
On a clean Kubuntu 18.04 install (plasma 5.12.5, framework 5.44.0, Qt 5.9.5) I applied the following sequence:

open "System Settings/Network/Connections" select current connection
	in tab "IPv4" set "Method:" to "Automatic (Only addresses)"
		set "DNS Servers:" to "1.1.1.1, 1.0.0.1"
	in tab "IPv6" set "Method:" to "Automatic (Only addresses)"
		set "DNS Servers:" to "2606:4700:4700::1111,2606:4700:4700::1001"
	click "Apply"
open "Terminal"
	execute "sudo service network-manager restart"

> After this I kept seeing "setting network address" followed by "disconnected" in a repeating loop.
> I reset the DNS values to the system defaults, restarted the network-manager, rebooted; the problem persisted.
> I reinstalled Kubuntu 18.04, setup a VM of Kubuntu and applied the same custom dns sequence in the VM and it worked.
> So I tried the sequence on my reinstalled system and it worked, until I rebooted.
Comment 1 Elkasir 2018-06-01 09:35:14 UTC
I've now tested this on 3 other systems, and the sequence works without a flaw.
I guess the problems I have on my system setting up DNS is somehow hardware related.
Comment 2 Elkasir 2018-06-10 04:41:40 UTC
I now know it's not just a problem when changing DNS, it also happens when I set a cloned MAC address. I suspect changing anything in the "Connections" causes the network to fail, and changing settings back & rebooting does not make it work again.

In fedora 28 with plasma (5.12.5) it's also happening.
In KDE Neon 16.04.4 useredition (5.12.5) there's no problem.

I've come across another system (also with a pre 2012 motherboard) that has the same problem with Kubuntu 18.04. So it's not an isolated case.
Comment 3 Justin Zobel 2022-11-26 00:13:51 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2022-12-11 05:07:16 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2022-12-26 05:21:07 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!