Not a big problem, only an annoyance: When I start up the computer the network comes up and works fine but a pop up window remains saying “You need to log in to this network”:
I can press the close button and the window disappears and everything still works fine, if I press the Log in button, the browser is opened on http://networkcheck.kde.org/ which returns a simple “OK” and also the window is gone.
Ideally I do not want to see this window, nothing is wrong.
I am using not wicked but the Network Manager which to my surprise seems to be a gnome thing, but there is also a KDE part because of the url used and the fact I can find the url in the half binary file /usr/share/plasma/plasmoids/org.kde.plasma.networkmanagement/contents.rcc and the binary file /usr/lib64/qt5/plugins/kf5/kded/networkmanagement.so
Apart from the Wired connection I am also using a local WiFi AP connection (no Internet) and a secondary VPN connection. For the WiFi connection no pop up windows is displayed, for the VPN connection it is.
This seems to be a regression, I did not see it two months ago, I am wondering if also others see it.
Also still wondering how to debug / report this problem.
While I can not help you with your problem itself, I see you are a bit confused by the several parts of Network Manager.
NetworkManager is a client-server application. So the server (a deamon) does the real work (and for that runs owned by root), but the clients (running owned by “normal” users) can be different implementations belonging to different desktop environments and there is also a CLI client. So yes, as end-user you see one NM client when using KDE and a different one when using Gnome.
KDE does not detect anything. Detection is performed completely by NetworkManager. While there could of course be bugs in GUI, the very fact that GUI displays this dialogue means NetworkManager did not get expected response when checking connectivity URL. Further troubleshooting needs this URL.
NetworkManager[1143]: <warn> [1571988507.4137] device (enp2s0): connectivity: "/proc/sys/net/ipv4/conf/all/rp_filter" is set to "1". This might break connectivity checking for IPv4 on this device
I am not sure I really want rp_filter to be set to zero, but for a test I tried setting it to 0 and reboot. That did not work as after the reboot the value was again 1.
Two things I will try to do:
Find out the right way to override (temporary) rp_filter during boot
NetworkManager[1143]: [1571988507.4137] device (enp2s0): connectivity: “/proc/sys/net/ipv4/conf/all/rp_filter” is set to “1”. This might break connectivity checking for IPv4 on this device
I don’t see that here, although:
cat /proc/sys/net/ipv4/conf/all/rp_filter
also shows “1”
Out of curiosity, does it still happen if you add:
interval=0
to the “[connectivity]” section (of NetworkManager.conf) , to disable the connectivity check.
Checked that removing ifcfg-suse from the plugins did not break things but the reason this was still there is that I had been playing with the uri in the past setting it to an own uri. I did revert that before reporting but in the process of testing found now that was done in a backup file…
So with “uri=http://conncheck.opensuse.org” in /etc/NetworkManager/NetworkManager.conf everything works fine although I still see the warning about rp_filter in the log and the also in the manual.