On 09/30/2014 08:15 PM, Michael Healy wrote:
<me snips>
...I issue my wpa_supplicant command to the device, and it says
wpa_supplicant successfully initialized. When I use DHCPCD, however, it
waits for a carrier, but never receives one. If I use the following
command-

wpa_supplicant -B -i wlp9s0 -c <(wpa_passphrase my_SSID password)

It shows the MAC addresses talking to one another, but it says that the
device disconnects locally (deauth_leave). It does this several times in
a row, then periodically repeats the same string of output.

  <me snips more>...I know that the DHCP client and dhcpcd are working, because 
I can get internet access
using my wired Ethernet adapter. Any help would be greatly appreciated!

First of all, I don't think you need both DHCP client and dhcpcd. They both do the same thing. My instincts tell me that if you're starting them both at boot time there might be some problems as a result. I use dhcpcd because the author of both says that it's better. I you're not running a DHCP server, you don't need it. In the rest of my discussion I'm going to assume that you're using dhcpcd.

Did you install the BLFS boot scripts for dhcpcd and wpa_supplicant? When you installed wpa_supplicant, did you create /etc/sysconfig/ifconfig.wif0? In that file, make sure you have <IFACE="wlp9s0"> and not wlan0.

If you've installed both the LFS and BLFS boot scripts, the correct sequence of events, and it matters, is taken care of by the "network" script. If you try to troubleshoot by starting and stopping individual components while the "network" is up, you can get some very confusing information. The cycling device messages are caused, I think, by wlp9s0 trying to find dhcpcd and not knowing it's there.

If you want to check the operation of individual components after you boot, first bring the whole network down.

Lastly, <ping> is your friend. You can see how far you can "reach" in your network.

Dan

--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to