You are not logged in.
Unfortunately, so far I've only had bad experience with networkmanager. In the end, I had to manually setup all 3G and Wifi connections. In both cases, troubleshooting manually was much easier compared to trying to use network manager which just introduced additional bugs.
One bug was when I tried to connect to a wifi network. It was infinitely asking me for a password via GUI even though I was using it through nm-cli (the reason for using nm-cli is not to have to deal with GUIs; what if I were to try to setup a connection through nm-cli through SSH?). When I put password in GUI (which again should not appear to begin with) it just did not give any feedback at all and each 30 seconds asked for a password again ad-infinitum. Go figure what is wrong. Is the password wrong? Does wpa_supplicant return some error? Is there something wrong with gnome-keyring? Not only NetworkManager just never tells you, its complexity obfuscates the picture even more.
However, it has some nice high level functionality that would have to be implemented manually.
Is there some way one can use custom configs wpa_supplicant and wv_dial scripts with networkmanager? Ideally, there would have to be some hook which is run when networkmanager wants to connect to the, e.g, wifi network, which would give control to a script to run wpa_supplicant and return control to network manager once the wpa_supplicant or wv_dial is started.
Is there at least some way to see which config network manager tries to feed wpa_supplicant , so that I can compare it to my current config and troubleshoot?
Am I the only one frustrated by this?
Offline
Is NetworkManager your only enabled network service? Could it be that for instance netctl is interfering? This might explain the endless password asking.
Offline