I have a USB Wi-Pi stick which is supposed to enable my Pi to connect to WiFi. I have opened up 'WiFi Configuration' and when trying to connect, the status will show '4-Way Handshake' for about 10 seconds, then scanning and repeats. The IP address is also missing. The Wi-Pi LED flashes throughout.

Here is the /etc/network/interfaces:

auto lo

iface lo inet loopback
iface eth0 inet dhcp

allow-hotplug wlan0
iface wlan0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp

And the /etc/wpa_supplicant/wpa_supplicant.conf:

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev

       ssid="CORRECT SSID"

I have tried looking at many other questions asked here but none have helped. Could it be a problem due to lack of power?

Any help is greatly appreciated and please ask if any other information is required.

  • 1
    That's weird. If it's reported it is starting that then you would think it should report why it did not complete because some piece of software in the stack does know. You might try what I describe in the accepted answer here to run wpa_supplicant in the foreground manually; use the commands in parentheses after "If you are using a wifi adapter..." – goldilocks Jan 3 '16 at 18:13
  • 1
    ...but don't do it in parentheses and don't use -B with the wpa_supplicant command. This will keep it in the foreground so you can see what it says. You do have to do the preliminary stuff to disable autoconfiguration, unfortunately, but as explained there it is not hard to do and restore if you pay attention. I have been meaning to write a Q&A about debugging wifi this way for a while now but have not gotten around to it. – goldilocks Jan 3 '16 at 18:14
  • 1
    Also see here: raspberrypi.stackexchange.com/q/37920/5538 In fact read that one first, it may solve your problems and save you the time of getting under the hood. – goldilocks Jan 3 '16 at 18:15
  • Thank you for your reply. I have tried changing the /etc/network/interfaces and setting up a static IP address. These made no difference. I then attempted to do what you said to run wpa_supplicant in the foreground. Using the wpa_supplicant command gave me a long-ish response about why it failed, let me know if you need to see this. This, as well, made no difference to connecting to wifi. – Mahclark Jan 3 '16 at 22:22
  • Definitely edit that in! – goldilocks Jan 3 '16 at 22:24

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.