You're using the network manager to type in the key?
Originally Posted by breakingcustom
From what I know, NetworkManager seems to have a problem with correctly passing the WEP key configuration to the driver. Please try this, in a terminal:
First, find your wireless interface, for me this looked like:
wlan1 is my wireless interface, the command used is iwconfig.
lo no wireless extensions.
eth0 no wireless extensions.
wlan1 IEEE 802.11g ESSID:"WLAN-AP"
Mode:Managed Frequency:2.462 GHz Access Point: 00:13:D4:32:36:74
Bit Rate=54 Mb/s Tx-Power:32 dBm
RTS thr:2347 B Fragment thr:2346 B
Link Quality:59/100 Signal level:-58 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
First, let's list some acess points: (for me this looked like:
This shows me the ESSID (WLAN-AP), the mode (managed) and the Channel (11)
stefan@lapsteef:~$ iwlist wlan1 scanning
wlan1 Scan completed :
Cell 01 - Address: 00:13:D4:32:36:74
Frequency:2.462 GHz (Channel 11)
Quality:62/100 Signal level:-56 dBm Noise level:-96 dBm
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Now, to configure with the info we just found:
This should configure your wireless interface, now to get an IP:
sudo iwconfig wlan1 mode managed
sudo iwconfig wlan1 channel yourwirelesschannel
sudo iwconfig wlan1 essid yourwirelessnetworkname
sudo iwconfig wlan1 key yourWEPkey
If successful, this will look like so:
sudo dhclient wlan1
Now please note:
stefan@lapsteef:~$ sudo dhclient wlan1
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/wlan1/00:21:00:1e:d6:aa
Sending on LPF/wlan1/00:21:00:1e:d6:aa
Sending on Socket/fallback
DHCPREQUEST of 192.168.1.11 on wlan1 to 255.255.255.255 port 67
DHCPACK of 192.168.1.11 from 192.168.1.1
bound to 192.168.1.11 -- renewal in 36643 seconds.
connecting via iwconfig and not via network manager means several applications will think you are offline. These applications include Pidgin and Firefox. You will have to use File -> disable tick for "Work Offline" in firefox when you start it.
You can simply reconnect with Pidgin to solve the issue.
A fix for network-manager seems to be in the pipeline, just not complete yet