I think it’s just that the defaults for NetworkManager don’t play nice with systemd, wpa_supplicant would take several minutes to connect to my wifi, and dhcpd just dropped my connection after I rebooted the router (for unrelated purposes) and would reconnect for about a minute before it dropped it again.
I’ve still been having an issue where if I reboot the computer, NetworkManager will hang up the boot process indefinitely, but this doesn’t happen if I shut it down and then turn it back on with the power button. Still haven’t figured that one out, all of my research said that this issue was supposed to have been fixed with the last update, but not for me I guess!
NetworkManager 1.48 Improves (…) still have to use 3 different applications to set network settings. Great job!
Maybe the GNOME team could allocate a few bucks to move the entire network stack to
systemd-networkdand create a new unified networking UI.I’m curious where you’re having issues. I’ve been able to use the little GNOME widget for setting up wireless connections for years.
Do you have an edge usecase that makes you drop back to using nmcli or is there a missing feature forcing you back to the ip/ifconfig commands?
No sarcasm, I’d just be interested in understanding your frustration a little better.
That might be the problem with DE integration. I’ve been using KDE, and I’ve only had to deal with a single interface for setting wifi connection.
NetworkManager is still shite on KDE, I’ve had to change the backend to iwd and download a new DHCP client just this week.
Interesting. I’m curious as to the exactl issue you were facing.
I think it’s just that the defaults for NetworkManager don’t play nice with systemd, wpa_supplicant would take several minutes to connect to my wifi, and dhcpd just dropped my connection after I rebooted the router (for unrelated purposes) and would reconnect for about a minute before it dropped it again.
I’ve still been having an issue where if I reboot the computer, NetworkManager will hang up the boot process indefinitely, but this doesn’t happen if I shut it down and then turn it back on with the power button. Still haven’t figured that one out, all of my research said that this issue was supposed to have been fixed with the last update, but not for me I guess!