Edimax Wireless USB Adapter EW-7811Un Not Connecting

[LikeyThePi]

Hello...

I've been attempting to get my new RPi to connect to my wireless router using a new Edimax EW-7811Un USB adapter. I've read many posts concerning this and I'm wondering if it's actually the adapter and not the settings listed below:

/etc/network/interfaces
auto lo

iface lo inet loopback
iface eith0 inet dhcp

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

/etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network={
ssid="my_ssid"
psk="my_password"
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP
auth_alg=OPEN
}

The wpa_gui does show the adapter as wlan0; the network as my_ssid. The Current Status tab Status line changes from Associating to Scanning and the Last message line changes from Association request to the driver failed and bssid=mac_address reason=0.

Ifconfig shows the Edimax adapter as wlan0 and provides its HWaddr mac_address. Lsusb shows the Edimax Bus and Device numbers. I'm using 2013-12-20-wheezy-raspbian as the OS.

Anyone have an ideas why I can't connect to my wireless router? Every other device I have does with no problems. Should I purchase a different USB wireless adapter? Any suggestions would be helpful. Thank you.

[MrEngman]

You could try using just /etc/network/interfaces to configure your network which avoids problems with wpa_supplicant.

Try something like this.

Code: Select all

auto lo

iface lo inet loopback
iface eth0 inet dhcp

allow-hotplug wlan0
iface wlan0 inet dhcp
wpa-ssid "network-name"
wpa-psk "network-password"

Your current setup looks reasonably OK but there is likely to be an issue with one of the settings in wpa_supplicant.conf which is stopping it connecting.

You could leave /etc/network/interfaces as it is and change /etc/wpa_supplicant/wpa_supplicant.conf to look like

Code: Select all

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

network={
	ssid="network-name"
	psk="network-password"
}

using this format wpa_supplicant works out the remaining items it needs for itself.


MrEngman

[LikeyThePi]

Thank you for the reply MrEngman.

1st) I tried just changing the wpa_supplicant.conf file to your recommendations. There was no connection. The wpa_gui was responding as initially posted.

2nd) I kept the wpa_supplicant.conf to your recommendations and then changed the interfaces file as you suggested. There was no connection. When checking the wpa-gui, it showed no adapter at all. When I changed the interfaces file back to its original contents, the wpa-gui found the adapter. Odd...

Any other recommendations by chance?

[MrEngman]

Either of the suggestions should work but as you say using the Wifi Config gui initially shows an association and it then fails it could be a power supply issue. The supply may not be able to supply sufficient current or if it can the voltage output may be insufficient or unstable when drawing the current required.

If you use the /etc/network/interfaces file as I suggested then the gui will not work as it no longer relies on wpa_supplicant to work. The network set up is then completely controlled by /etc/network/interfaces.


MrEngman

[LikeyThePi]

I didn't think that it would be a power supply issue. The product description stated that it was specifically designed and tested for the Pi and can deliver a full 1A without the output voltage dropping below the recommended 5V necessary for reliable Raspberry Pi operation. Hmm...

I'll try the interfaces file setup again as you recommended as I can't remember if the Edimax blue light was blinking or not at that point. [Edit - I tried it again and if works] Thank you very much for your time.

What you posted was great information to know about the interfaces and wpa_supplicant.conf file.

[MrEngman]

I didn't think that it would be a power supply issue. The product description stated that it was specifically designed and tested for the Pi and can deliver a full 1A without the output voltage dropping below the recommended 5V necessary for reliable Raspberry Pi operation. Hmm...

I'll try the interfaces file setup again as you recommended as I can't remember if the Edimax blue light was blinking or not at that point. [Edit - I tried it again and at least the blue light is flashing, however, still can't connect]

What you posted was great information to know about the interfaces and wpa_supplicant.conf file.

There's a little bit more you may find useful here.


MrEngman

[LikeyThePi]

I apologize, I edited my post before I saw your reply. It now works! Thank you very much for your insight and help getting me connected.

I guess my next question would be how to make the Pi use a static IP address using the interfaces file with a specific port. You wouldn't happen to know what lines I should type/change in the interfaces file do you?

[DougieLawson]

Code: Select all

auto lo

iface lo inet loopback
iface eth0 inet dhcp

allow-hotplug wlan0
iface wlan0 inet static
address 192.168.xxx.yyy
gateway 192.168.ggg.hhh
netmask 255.255.255.0
wpa-ssid "network-name"
wpa-psk "network-password"

You have to supply the numbers for xxx, yyy, ggg & hhh.

[LikeyThePi]

Is there a way that I could use a specific port in the interfaces file? I'm thinking in terms of connecting to my Pi from outside/WAN.

[DougieLawson]

Is there a way that I could use a specific port in the interfaces file? I'm thinking in terms of connecting to my Pi from outside/WAN.

You're not making any sense.

You open a port (one of 64K) to establish a connection. You don't define ports in the interfaces file.
There is a concept called port forwarding for NAT routers but that's nothing to do with the interfaces file either. That's something that you do on the NAT router.

[LikeyThePi]

My apologies... It's late and I was thinking in terms of how I have one of my other network devices configured. It requires a port to be defined in its setup. This is my first dealing with the interfaces file.

Thanks for all the help in getting me connected! Much appreciated.