You are not logged in.
Right, I understand the difference between enabling and starting a service. I was just pointing out that wpa_supplicant was (I thought) the only network service enabled, so nothing else should be interfering with it.
But then again, upon a closer look, I discovered that dhcpcd was running even *after* I ran "dhcpcd -k"
[ben@archlinux ~]$ systemctl status | grep dhc
│ ├─14894 dhcpcd enp0s20u3
│ ├─15107 dhcpcd wlo1
│ ├─15195 grep --color=auto dhcOn the dhcpcd wiki page, I read that "[dhcpcd's] 10-wpa_supplicant hook, if enabled, automatically launches WPA supplicant on wireless interfaces." So I ran
ln -s /usr/share/dhcpcd/hooks/10-wpa_supplicant /usr/lib/dhcpcd/dhcpcd-hooks/and then
dhcpcd wlo1...and lo and behold, dhcpcd immediately brought up the wpa_supplicant interface I'd configured. I'm now connected via wireless.
So I'm thinking dhcpcd *was* getting in the way of wpa_supplicant, and I was just too dense to realize it was still running after I'd tried to kill it.
The wpa_supplicant connection started with dhcpcd has been up and running for a few hours, without any problems. I'm marking this "Solved." Thank you all very much for your help and patience with my learning curve.
Of course, there's still the issue of getting wifi-menu up and running... but that's another thread for another day ![]()
Last edited by extrapalantine (2018-06-07 07:45:18)
Offline
I'm glad you got it to work.
That's why i prefer to use systemd for handling services, the command 'dhcpcd -k' merely releases the interface. If you look at the man page or at the unit file, you'll see that the command for killing the daemon, or dhcpcd is 'dhcpcd -x'.
To use systemd with dhcpcd is just a matter of starting dhcpcd@interface.service with 'systemctl start ...' and then stopping it with 'systemctl stop ...' instead of doing it manually.
Getting wifi-menu up and running should be a no brainer now that you found the problem. Just stop all network services with systemctl, then use 'wifi-menu' (I like to use it with the -o option so as not to store plain text passwords). wifi-menu creates a netctl profile for you. then whenever you want to connect you just need to start it with 'netctl start profile_name'.
Offline
Thanks, ivanmlerner! I tried wifi-menu again, and it worked exactly as you described.
Thanks to everyone's help, this thread has been a huge learning experience for me, and now I definitely consider it "Solved."
Offline
Then please also formally mark it as such by editing the title in your first post and prepending [SOLVED]
Offline