On Thu, Oct 16, 2014 at 3:53 PM, walt <w41...@gmail.com> wrote: > On 10/15/2014 08:23 PM, Tom H wrote: >> On Mon, Oct 13, 2014 at 7:39 PM, walt <w41...@gmail.com> wrote: >>> >>> I just switched my home LAN from wired to all wifi and I'm having trouble >>> with NetworkManager at boot time. >>> >>> I have systemd start NetworkManager at boot because I need the internet >>> for ntpdate and to start the nfs server for the LAN. Before I switched >>> to all-wireless this method worked perfectly, but no longer. >>> >>> After bootup I see that NetworkManager started wpa_supplicant in the >>> background, but apparently does *not* run dhcpcd. (The wlan0 is up >>> but it has no IP address and the routing table is empty.) >>> >>> As an alternative to NetworkManager I can have systemd start dhcpcd >>> at boot, which almost (but not quite) works well enough. This >>> causes a race condition because wlan0 takes several seconds to come >>> up properly and by then both ntpdate and nfs-server have already >>> run and failed. >>> >>> So, I asked myself, why not have systemd start dhcpcd at boot in >>> addition to NetworkManager? >>> >>> The reason that fails is that they both start wpa_supplicant in >>> the background and the two instances interfere with each other. >>> >>> Anyone see a way around this catch22? >> >> Do you have "All users may connect" unticked in the NM applet or >> "permissions=user:walt:;" in the NM connection's config? > > After studying the logs I'm beginning to think that NM is actually > trying to start wlan0 at boot time but failing with this message: > 'no secrets', which I assume means no password, maybe? > > Yes, I do have the all-users box ticked. Question: I've set up the > wlan0 connection (as root) several times using nmtui, including the > SSID password, yet each time I start nmtui the password field is blank > again. Is this normal behavior? How can I tell if the password is > actually being stored somewhere?
As I said some messages ago, check: /etc/NetworkManager/system-connections In that directory should be all the system-wide network configurations. Also, check /etc/NetworkManager/NetworkManager.conf and make sure you have "plugins=keyfile" in the "[main]" section. At some point NM had integration with the OpenRC network configuration, and (AFAIR) sometimes it made a mess inside /etc/conf.d. I don't know if such integration exists anymore; nowadays I don't even have /etc/{conf,init}.d, and everything works so much better. Regards. -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México