You are not logged in.
I use netctl-auto to manage my wifi connections. However, it can't connect to wifi automatically on boot.
At first, I thought wpa_supplicant and its wpa_actiond didn't successfully start. But the 'systemctl status' of netctl-auto show that it worked well.
Then I check the journalctl and found that the wpa_actiond did start successfully and included all the profiles EXCEPT connecting to the network !
The log from journalctl:
Jul 18 09:30:51 shockwave wpa_actiond[429]: Starting wpa_actiond session for interface 'wlp3s0'
Jul 18 09:30:51 shockwave netctl-auto[263]: Included profile 'wlp3s0-SITCON2014-R0'
Jul 18 09:30:51 shockwave netctl-auto[263]: Included profile 'wlp3s0-HUNTERxHUNTER'
...(profiles)....
Jul 18 09:30:51 shockwave netctl-auto[263]: Included profile 'wlp3s0-SITCON2014-R1'
Jul 18 09:30:51 shockwave netctl-auto[263]: Included profile 'wlp3s0-Hsu-Family-new'
Jul 18 09:30:51 shockwave netctl-auto[263]: Included profile 'wlp3s0-CIRCDDC'
Jul 18 09:30:51 shockwave netctl-auto[263]: Included profile 'wlp3s0-iPad'
Jul 18 09:30:51 shockwave netctl-auto[263]: Included profile 'wlp3s0-87752141'
netcl-auto just stopped there!
No sooner had I restarted the netctl-auto service did the wpa_actiond started to connect to the network.
Jul 18 09:34:13 shockwave wpa_actiond[1053]: Starting wpa_actiond session for interface 'wlp3s0'
Jul 18 09:34:14 shockwave wpa_actiond[1053]: Interface 'wlp3s0' connected to network 'Hsu-Family-new'
How did that happen? Did I miss some configuration?
Offline