I was following the wireless guide to get wpa_supplicant working with my WEP-only network. I based my /etc/wpa_supplicant/wpa_supplicant.conf section on the following: network={ ssid="static-wep-test" key_mgmt=NONE wep_key0="abcde" wep_key1=0102030405 wep_key2="1234567890123" wep_tx_keyidx=0 priority=5 } Unfortunately it's not clear from this whether the WEP keys are the ASCII keys commonly used (and automatically translated into hex) or the keys themselves. 'abcde', for instance, is a valid hex and ASCII string. Anyway, the reason why this is important is because enclosing a key in double quotation marks seems to force it to be interpreted as ASCII. At least, I entered my hex key in quotation marks and wpa_supplicant would seem to connect fine, but then dhcpcd would time out when sending DHCP_DISCOVERs. Removing the quotation marks instantly fixed the problem. If someone bases their config file on 'wep_key2' from the example, this problem will happen to them. Unfortunately I can't find any documentation to confirm this quoting behaviour, so I don't know if it's intentional or not. In addition, it might be obvious if you note the WPA example above it with "very secret passphrase" and then the long unquoted PSK. But for people like me who scan without reading, it might be useful to reinforce this. ;) Reproducible: Always Steps to Reproduce: 1. Enter a WEP key in quotation marks. 2. Run 'wpa_supplicant -d -Dwext -ieth0 -c/etc/wpa_supplicant/wpa_supplicant.conf' 3. Try to get a lease with 'dhcpcd -d eth0' Actual Results: wpa_supplicant will apparently connect fine, going to ASSOCIATED and then COMPLETE state. It will list your SSID and other encouraging things. However, dhcpcd will send several DHCP_DISCOVERs and then time out, falling back to an old non-working IP address. Expected Results: Gained a valid DHCP lease and enabled the internet connection. AMD64, orinoco_pci wireless driver, 64-bit WEP key. Verified working DHCP server.
Fixed in CVS.
