I've been trying to solve this problem for nearly a year now. I've got a laptop with a Linksys WPC11 V3 card and a Linksys WAP11 V2.2 access point. I'm trying to set up an 802.11 link between them. The problem is that WEP isn't working. Or rather, the link won't work when WEP encryption is enabled. I've tried the card with two different laptops, and a palmtop, running 3 different OSs, and it never works. Right now its on a Dell latitude running Linux. I've got the card setup properly, and I can run kismit. I'm using wlan-ng, and everything looks fine. The access point works great too, at least as far as I can tell. Everything works great without encryption, and I can link them. The problem happens when I enable encryption. I CAN link to the AP somewhat, but then can't access anything with TCP/IP. When I turn off encryption everything works. It happens on Linux and Windows, although its a little easier to set up under Linux. Okay, heres what I do: I login to HTTP remote admin on the AP. I set WEP to mandatory and set the keys using the keygen with a word, in this case, for example "pleasework". I click generate, and it produces the HEX keys. I then copy the keys into the config file on the laptop, enable WEP. I set the config on the AP, and try to bring up the wlan interface. Then nothing happens. It CAN recognize the AP, but TCP/IP never works. I've followed the manuals _exactly_, I've tried messing with the settings(advanced and otherwise), I've tried resetting it to the factory state and reconfiguring many times. Nothing seems to be working with WEP. Am I doing something wrong here?

??? I don't use Linksys, but I've configured several other WAPs, and I've never seen it be set up in the config file? Generally when you enable WEPs you do the configuration of the keys on the WAP and the Wireless cards, not the computer itself! You should remove the WEP key from your config file, go into networks, select your Wireless Card, either the adapter or the tcp/ip settings, select property and there should be a section to input the WEP key to match the same WEP key that your WAP is set to. It may ask you to enable WEP first before giving you the option to set the keys, but it will be there. Do this with any Wireless Card that you want to have access to your WAP. D

I'm running linux, so its set under a config file. But I followed your suggestion, and figured out how to set the keys on the actual card. Apparently, you have to run "/etc/pcmcia/wlan-ng start wlan0" to initialize the card with the config file settings. I didn't find that in the documentation I was reading. I set the keys in the /etc/pcmcia/wlan-ng.opts config file, and tried running "wlan-ng start wlan0" first: (keys x'ed out) %/etc/pcmcia/wlan-ng start wlan0 /etc/pcmcia/wlan-ng start wlan0 message=lnxreq_hostwep resultcode=no_value decrypt=true encrypt=true message=dot11req_mibset mibattribute=dot11WEPDefaultKeyID=0 resultcode=success message=dot11req_mibset mibattribute=dot11ExcludeUnencrypted=true resultcode=success message=dot11req_mibset mibattribute=dot11PrivacyInvoked=true resultcode=success message=dot11req_mibset mibattribute=dot11WEPDefaultKey0=xx:xx:xx:xx:xx resultcode=success message=dot11req_mibset mibattribute=dot11WEPDefaultKey1=xx:xx:xx:xx:xx resultcode=success message=dot11req_mibset mibattribute=dot11WEPDefaultKey2=xx:xx:xx:xx:xx resultcode=success message=dot11req_mibset mibattribute=dot11WEPDefaultKey3=xx:xx:xx:xx:xx resultcode=success %/sbin/ifup wlan0 Error for wireless request "Set Encode" (8B2A) : SET failed on device wlan0 ; Function not implemented. Error for wireless request "Set ESSID" (8B1A) : SET failed on device wlan0 ; Function not implemented. Determining IP information for wlan0... done. But when I run /sbin/iwconfig I get: wlan0 IEEE 802.11-b ESSID:"net1" Nickname:"net1" Mode:Managed Frequency:2.437GHz Access Point: 00:06:25:54:27:11 Bit Rate:11Mb/s Tx-Power:2346 dBm Retry min limit:8 RTS thr:off Fragment thr:off Encryption key:off Link Quality:78/92 Signal level:-47 dBm Noise level:-98 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 It says there isn't any encryption. I ran kismet to analyze the network, and it says its encrypted, so I'll assume that's correct.