[opensuse] About NetworkManager
I'm just wondering if I'm alone in this. NetworkManager just bugs out a lot. For example, just now when this laptop came out of standby, obviously (perhaps) the wifi had been lost. But it wouldn't reconnect. It just failed. It only worked after I did: service NetworkManager restart. Then it connected automatically. Sometimes when I close my VPN (configured via NM) it won't start up again. I have to go to a shell and run it manually and I don't know why, but NM will just immediately 'return' after clicking my VPN connection's "connect". Perhaps that can be fixed with "service NetworkManager restart" also. The way my system is set up there should really be no flaws. The wifi creates an SSH tunnel, when the wifi goes down the tunnel is killed. The tunnel is there for the VPN, which I create manually from the NM-applet in KDE. When the VPN goes down the tunnel is not closed, it doesn't need to. If the tunnel closes unexpectedly I'm in a bit more trouble, I have to first check whether the tunnel is still live (I do it with tunnel status) and after that I might need to check the connection to the tunnel host, I haven't automated that yet. But closing and reopening wifi also does this. NetworkManager interferes with VPNs it does not set up itself, but it is no great interference, I just cannot delete the default route of the default wifi connection. Troublesome, but no deal breaker at this point because the new openvpn route supersedes it. Troublesome though that NM think it's so important. Anyone else experience these issues? I have had before in another KDE distro as well. I was trying to create my own "NM" suite with scripts but obviously I don't know enough about KDE to create my own applet. And it requires a lot of work to get any sort of roaming support (logging onto different networks). It just seems NM's internal state often goes corrupt. Regards. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Sep 9, 2015 at 6:23 AM, Xen
Anyone else experience these issues?
I'm sure you've searched the Internet at this point, but yes, this is a very common problem which affects some users. I've seen it on Ubuntu, openSUSE, Arch, and the rest of the major distributions with a variety of different wireless cards. Usually, the answers I see floating around the Internet are pretty hacked together, using pm-utils, etc. to have systemd restart NetworkManager. The reason for this is because the problem can occur for a multitude of reasons. A few suggestions I can recommend are to try a later version of wpa_supplicant and ensuring that the kernel module for your wireless card is unloaded before sleep/suspend (see SUSPEND_MODULES for pm-utils). Every time a bug report for this issue is closed, I find someone opens it again saying the problem isn't fixed. I've had this happen on an up-to-date install of Arch as of a month ago. Brandon Vincent -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 9 Sep 2015, Brandon Vincent wrote:
I'm sure you've searched the Internet at this point, but yes, this is a very common problem which affects some users. I've seen it on Ubuntu, openSUSE, Arch, and the rest of the major distributions with a variety of different wireless cards.
Usually, the answers I see floating around the Internet are pretty hacked together, using pm-utils, etc. to have systemd restart NetworkManager. The reason for this is because the problem can occur for a multitude of reasons.
A few suggestions I can recommend are to try a later version of wpa_supplicant and ensuring that the kernel module for your wireless card is unloaded before sleep/suspend (see SUSPEND_MODULES for pm-utils).
Every time a bug report for this issue is closed, I find someone opens it again saying the problem isn't fixed. I've had this happen on an up-to-date install of Arch as of a month ago.
Thank you, very insightful. Restarting NetworkManager however doesn't solve my vpn problem :S. Maybe I'm mistaken. I seem to be needing to get to the root shell again once more each time, and run all these commands by myself. It is so tiresome. I wish it worked like it should. No regular user could ever troubleshoot such a thing by himself or herself. I just wish it plain worked... In Windows from what I've experienced if your wifi fails, you know it is a problem with the wifi. In Linux, it is probably the software bugging out. I may need to check whether my tunnel(s) are correctly closed when I shut down the wifi. And restarted. Restarting NM at least causes the wifi to connect again. I get so sick of this... Thanks for your swift answers. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/10/2015 01:47 AM, Xen wrote:
On Wed, 9 Sep 2015, Brandon Vincent wrote:
Every time a bug report for this issue is closed, I find someone opens it again saying the problem isn't fixed. I've had this happen on an up-to-date install of Arch as of a month ago.
Now I just rebooted and NM logged into my wifi. But dispatcher.d directory was not executed. I know because I log all executions. Actually what seems to have happened (or seemed) is that my tunnel script failed because I had changed my wifi device back from wls1 to wlan0. Then I started OpenVPN using NM-applet. VPN was started but could not connect. I manually started the tunnel. Now VPN connected. However, the routing table was not updated. So my VPN is live, but NM doesn't know it. But since NM wants a "management console" at port 1194 localhost, and OpenVPN is actually listening to it, any new attempt at opening a VPN connection will fail because 1194 is already taken and that is a fatal failure for it. After the link-up, it does: /usr/lib/nm-openvpn-service-openvpn-helper --tun -- tun0 1500 1528 10.8.0.6 10.8.0.5 init But then it says "NetworkManager[1594]: (process:3220): nm-openvpn-WARNING **: Could not send configuration information: The name org.freedesktop.NetworkManager.openvpn was not provided by any .service files". Then we kill the openvpn process, and it says: nm-openvpn[2960]: ERROR: could not read Auth username/password/ok/string from management interface nm-openvpn[2960]: Exiting due to fatal error avahi-daemon[1500]: Withdrawing workstation service for tun0. Then we reconnect using NM-applet: And now it says: NetworkManager[1594]: <info> (tun0): new Tun device (driver: 'unknown' ifindex: 6) NetworkManager[1594]: <info> (tun0): exported as /org/freedesktop/NetworkManager/Devices/5 instead of the earlier failure of: Could not send configuration information: The name org.freedesktop.NetworkManager.openvpn was not provided by any .service files.. Buh, maybe give them a sign about this.... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wednesday 09 of September 2015 15:23:53 Xen wrote:
NetworkManager just bugs out a lot. For example, just now when this laptop came out of standby, obviously (perhaps) the wifi had been lost. But it wouldn't reconnect. It just failed.
It only worked after I did: service NetworkManager restart.
Then it connected automatically.
I'm not sure which is at fault in my case: wifi driver, wpa_supplicant or NetworkManager. Frequently I lose wifi connection (cannot authenticate) after suspend-to-RAM, and restarting wpa_supplicant fixes this, occasionally temporarily. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
auxsvr -
Brandon Vincent -
Xen