VX and V3 WEP

[nelson05]

I wanted to post the following information with the news that V3 for the WAR is just about here and that WEP support will likely make it into the first release.

I have been using V2 on WRAPs for my CPE to attach to a number of Cisco 350 AP/Bridges with no problems for the last couple of years. While the Cisco equipment is slowly, but surely going away, I have to keep it in place as an AP until I rid myself of the Cisco WGB 350s (which will only associate with a Cisco AP) we deployed for our business customers when we first began service.

Again, this hasn't been a problem until I ordered a batch of WARs (thinking that I would have V3 on them before they were actually deployed) and found that the WARs with VX could not associate with the Cisco equipment. The Cisco equipment is not doing anything fancy (just basic WEP) and as I mentioned earlier, the WRAPs with V2 can associate without any problems.

Below is the WEP config from V2 that works:

### set a 104-bit (128-bit under Windows) WEP key, in index 1
encryption enable
authentication shared-key
cipher wep
keysource local
key 1 104 A220B22C22D22E22F22A74B22C
key 1 default

I setup VX with WEP using what looks to be the equivalent configuration. Under the Security button on the Basic Configuration section of the wireless card, I enabled WEP encryption using a Shared Key with the following WEP key A220B22C22D22E22F22A74B22C.

Unfortunately, I could not associate to the Cisco. Any ideas? I changed other elements of the configuration (Long/Short, Super A/G, XR, etc.) and tried multiple WARs with the same result. I held off posting since V3 was imminent and I didn't plan on deploying VX anyway. However, now that is is almost here, I wanted to get this out there in case something is broken with WEP in the new Atheros driver.

[lonnie]

Thanks for the info, but you will have to test the new driver for us. We do not have any Cisco units to try it with.

I wanted to post the following information with the news that V3 for the WAR is just about here and that WEP support will likely make it into the first release.

I have been using V2 on WRAPs for my CPE to attach to a number of Cisco 350 AP/Bridges with no problems for the last couple of years. While the Cisco equipment is slowly, but surely going away, I have to keep it in place as an AP until I rid myself of the Cisco WGB 350s (which will only associate with a Cisco AP) we deployed for our business customers when we first began service.

Again, this hasn't been a problem until I ordered a batch of WARs (thinking that I would have V3 on them before they were actually deployed) and found that the WARs with VX could not associate with the Cisco equipment. The Cisco equipment is not doing anything fancy (just basic WEP) and as I mentioned earlier, the WRAPs with V2 can associate without any problems.

Below is the WEP config from V2 that works:

### set a 104-bit (128-bit under Windows) WEP key, in index 1
encryption enable
authentication shared-key
cipher wep
keysource local
key 1 104 A220B22C22D22E22F22A74B22C
key 1 default

I setup VX with WEP using what looks to be the equivalent configuration. Under the Security button on the Basic Configuration section of the wireless card, I enabled WEP encryption using a Shared Key with the following WEP key A220B22C22D22E22F22A74B22C.

Unfortunately, I could not associate to the Cisco. Any ideas? I changed other elements of the configuration (Long/Short, Super A/G, XR, etc.) and tried multiple WARs with the same result. I held off posting since V3 was imminent and I didn't plan on deploying VX anyway. However, now that is is almost here, I wanted to get this out there in case something is broken with WEP in the new Atheros driver.