Howdy folks! BTW, I love the new installer! I’m running into one problem. Not bad, eh? Only one? Well, here it is:
Whenever I log into the new EndeavourOS in KDE using ethernet or wifi, I get an error of Limited Connectivity. I have tried to make a configuration file based on the Arch Wiki using both methods listed (.set.enabled=false and just enabled=false) in a new file in etc/Network Manager/conf.d/20-connectivity.conf file. I might be able to go about 3 to 5 minutes before I get that error. Going to speedtest.net shows I’m plugging along great. I am using ExpressVPN, and I understand that VPN’s might block the ping to the connectivity servers. I’m trying to disable the ping request to keep this from popping up. How can I do this?
Have you tried the r8169 module. This is a kernel module that should load on boot. It’s using the r8168 which is an installed package. As long as you have wireless you could try to remove the r8168 package and reboot and see if it loads the r8169 kernel module and works better. I just don’t want to tell you to remove it if you don’t have a means to reinstall it if the ethernet doesn’t work on the r8169 but it does say that that is the chip.
Hi @ricklinux I have to apologize that I’m an intermediate user, and don’t know the nuts & bolts of things like this. But, when I removed the r8168 and installed r8169, it renders Ethernet dead. Thank goodness I do have wifi, I was able to switch it back. And, this is what I get after I start up. Weird thing is, even with ExpressVPN, my rates are faster than I’m paying for. Go figure. Here’s what I see…
Well that’s why wanted to give the warning about it because i wasn’t sure if it would leave you dead in the water or not but i had a suspicion it could.
Simply the notification, really. From what I understand, it’s the connectivity check Network Manager makes when it first connects to the internet. My understanding is that VPN’s can block this connection test to the server, and that’s why it shows as having limited connections. However, the network is working fine. There’s supposed to be a way to stop the Network Manager from making this initial check, but I can’t find a way to do it. I have tried using the instructions on the Arch Wiki, but they don’t work for me.
Yes, that’s the first version I tried. This is apparently disputed in the Arch Wiki, and I’ve also tried the alternative where you simply use enabled=false. Neither are working to stop the notification.
I saw on a Ubuntu thread where they added it in the NetworkManager conf file that creates the NetworkManager file but not sure whether that would work?
That’s pretty interesting! I do think I fixed it, though it might not be a pretty work around for it. According to the Arch Wiki,
The default host (configured in /usr/lib/NetworkManager/conf.d/20-connectivity.conf) is ping.archlinux.org
So, instead of using the file in the /etc/NetworkManager folder, I went to the /usr/lib/NetworkManager file, removed the line where it tries to ping the Arch servers, and put in the line of code from the other 20-connectivity.conf file in /etc/, [connectivity]
.set.enabled=false, restarted and I don’t see the error. I think it’s blocked from trying. My internet is still strong, and I’m not getting the Limited Connectivity error any more. It’s been 15 minutes, and all’s well so far. I’ll continue to test this today and tomorrow unless someone comes along and says I shouldn’t do that because of X, Y, or Z and gives me a different fix. Looks like we might have got it taken care of, @ricklinux !
Yes that is exactly what i would try and i checked my kde and it has the same file. I’m not getting any notification issue but i don’t use vpn so that maybe the difference. I don’t know and I’m not even sure why they have this to begin with?
I think it’s just an internal check to make sure you’re connected when the Network Manager’s activated. I read somewhere (that Manjaro article maybe?) that it’s a potential security risk anyway. I honestly have no idea. LOL But, I do appreciate your time and efforts in helping me!