Cannot use Home WEP Key on Aironet 350 PCMCIA with Linux

[djreedps]

I have had a strange problem with my Cisco Aironet 350 PCMCIA card since I installed RedHat Linux 7.2. I have seen the same problem with Mandrake as well as Suse Linux on the same laptop, but I do not see the problem when I boot into Windows 2000.

The problem is that I am unable to get a DHCP assigned IP address from my wireless access point at home if I use the Home Network Configuration and set the 128 bit Home WEP key. At first I thought this problem was with my Linksys BEFW11S4 router since WEP was working fine at my workplace using Cisco access points. So I bought a DLink 614+ access point for home, but I still have the same problem of not being able to get a DHCP assigned IP address. It does associate, though, at least the Cisco ACU shows association.

The workaround is that I can either disable WEP at home, or use the Enterprise Configuration at home and change WEP Key 1 in CEM to my home access point's WEP key. In either of those cases, I can get an IP address at home.

So, is my 350 card defective, or is this a known problem with the Cisco Linux client?

Thanks,

-Dennis

[mmellet]

I would bet it's the Linux client that's got a bug.

[djreedps]

Thanks, I have gotten into the routine using the Enterprise configuration for both home and work, and unselecting Leap and reselecting Enable WEP when I get home. I am able to keep both my work and home SSIDs set as SSID1 and SSID2, which works pretty well.

I am patiently waiting for Cisco to release a Linux ACU client that supports profiles and automatic profile switching like the latest Windows ACU client does. Hopefully there are enough fellow Linux nerds out there to support future Cisco Linux development.