I can not get my WiFi connection to work

Question

I've bought a nano wifi adapter at modmypi.com (this one).

It works, I checked it in a raspbmc configuration (I used raspbmc to configure it there).

Now I'm back at my wheezy distro, and I can't get it to work.

When I do a ifconfig it's there (see below).

The help page on modmypi.com had a script, but when I run that, I get this exception: "Looks like you're using the new 2012-09-18-wheezy-raspbian image. Sorry but the script will not currently set up the wifi on this image. You need to start the GUI using command startx and set it up using WiFi Config. The script will now terminate. Press any key to continue ..."

So now I am in the GUI, and started nm-connection-editor, but it doesn't seem to get an ipaddress.

I've read about this command: dhclient -v wlan0, and this is it's output:

sudo dhclient -v wlan0
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/wlan0/00:0f:more numbers
Sending on   LPF/wlan0/00:0f:more numbers
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

And now I don't know what to do.

This is the ifconfig:

wlan0     Link encap:Ethernet  HWaddr 00:0f:1more numbers
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

iwconfig wlan0:

wlan0     unassociated  Nickname:"<WIFI@REALTEK>"
          Mode:Managed  Frequency=2.412 GHz  Access Point: Not-Associated   
          Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

/etc/wpa_supplicant/wpa_supplicant.conf:

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


network={
        ssid="Nerd"
        psk="SECRET"
        proto=RSN
        key_mgmt=WPA-PSK
        pairwise=CCMP TKIP
        group=CCMP TKIP
}

Executing wpa_supplicant -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf gives this:

wlan0: Trying to associate with 2a:65:11:f2:ce:97 (SSID='Nerd' freq=2412 MHz)
wlan0: Association request to the driver failed
wlan0: Associated with 2a:65:11:f2:ce:97
wlan0: WPA: Key negotiation completed with 2a:65:11:f2:ce:97 [PTK=CCMP GTK=TKIP]
wlan0: CTRL-EVENT-CONNECTED - Connection to 2a:65:11:f2:ce:97 completed (auth) [id=0 id_str=]
wlan0: CTRL-EVENT-DISCONNECTED bssid=2a:65:11:f2:ce:97 reason=0
wlan0: Trying to associate with 90:00:4e:87:c8:cf (SSID='Nerd' freq=2412 MHz)
wlan0: Association request to the driver failed
wlan0: Associated with 00:00:00:00:00:00
wlan0: CTRL-EVENT-TERMINATING - signal 2 received
wlan0: Trying to associate with 90:00:4e:87:c8:cf (SSID='Nerd' freq=2412 MHz)
wlan0: Association request to the driver failed

Answer 1

You might have multiple instances of wpa_supplicant running. try

ps ax | grep "wpa_supplicant -B" | grep -v grep
kill {pid of wpa_supplicant}

if that works then you can try this

sudo kill $(pgrep -f "wpa_supplicant -B")
sudo ifconfig wlan0 down
sudo ifconfig wlan0 up
sudo rm -r /var/run/wpa_supplicant/*
sudo wpa_supplicant -B -iwlan0 -f/var/log/wpa_supplicant.log -c/etc/wpa_supplicant/wpa_supplicant.conf
sleep 15
sudo dhclient -v -r wlan0
sudo dhclient -v wlan0

and tail the /var/log/wpa_supplicant.log to see what is going on.

wpa_supplicant should run at start up with the default config file. if you want to chage your config file on the fly kill the old process, blow away the /var/run/wpa_supplicant/* directory and start wpa_suplicant with the new config file by using the -c option.

Side note wpa_cli is odd the flags are not followed by a space. for example you want to do

wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant.conf

not

-c /etc/wpa_supplicant

Answer 2

I had a bad wifi password, which caused this. Specifically, the "at" symbol and quotation mark are reversed on a UK keyboard, so the "at" symbol in my password came out as a quotation mark, which the config file certainly didn't like. :)

Answer 3

http://wirelessdefence.org/Contents/LinuxWirelessCommands.htm

i had the same problem logging in with WEP, i resourced a linux web site and scored this page, tried the first one and now im linked via wifi!

Answer 4

Have you tried powering up the pi untill you have logged in either in a terminal or gui then unplugging and replugging the wifi adapter. Then remove all entries for wireless networks and re-scanning for your network then configuring it. Dont know if it will work for you but it did for me when my adaptor plays up