[Wireless] What is the point of Open System Authentication with WEP data encryption?

[bex0rs]

I recently bought a Proxim RangeLAN-DS 802.11b access point. It does not appear to support shared key authentication, although it does support 40-bit and 128-bit WEP for data encryption. So, whether or not I enable WEP, the access point will always be using open system authentication.
I realize that WEP is only a mediocre security measure, but I still want to have it enabled.

There are two wireless clients on my network. One is a laptop running XP with a Prism2 based card, which I was able to get running by using the reference Intersil drivers. In order to get it on my network with WEP data encryption enabled, I had to choose the "WECA Compliant (open system)" authentication algorithm in the advanced tab of the card's properties. That setting makes sense, as my AP does not support shared key authentication.

The other client is an ipaq, also with a Prism2 based card. I installed the Intersil WinCE 3.0 reference drivers, but they only sort of work. There does not seem to be an option to select the authentication system independent of WEP, ie. the drivers either use open/no wep OR shared key/wep. This is obviously a problem, since I seem to have the only access point out there which doesn't allow for the authentication system to be changed (regardless of the WEP setting). Unless there is a driver setting which I have missed, it appears that the only way to get the ipaq on my open-authentication-only network is to have WEP disabled on the AP.

This seems odd to me. What is the point of an implementation like this? Why support WEP data encryption but not support authentication based on the [same] WEP key? Is there any reason to set up a network this way? And if anyone knows the solution to my ipaq issue, please let me know too.

Thanks,

~bex0rs

 

[bex0rs]

still curious, thanks

~bex0rs

 

[Scarpozzi]

I would contact Compaq and see if they have a patch or know of another adapter that may work with your AP. This problem sounds like a Windows incompatibilty so Compaq would be the ones to speak with. They will have to support the OS on the IPAQ since it's part of the OEM agreement. I would think they may either know of a compatible adapter or possibly, like I said, a patch that may work with the Access Point. Proxim has pretty good support, but not through their tech lines....check their website. It's design is pretty good. Good luck.

 

[SaigonK]

Shared key authentication is a piece of junk and you should not use it.
The problem being is the following:

1. Ipaq sends a signal out to your WAP to get online.
2. WAP sends an UNENCRYPTED key back to the Ipaq to have it decode it and send it back to the WAP to assure it is allowed on the LAN.
3 The Ipaq sends back the key needed to authenticate to the WAP in an unencrypted manner in order to get on the WAN.

Therein lies your problem, anyone can pick up the response the WAP is aking for and hook up to your WAN.

Use OPen Authentication, in most instances it is much safer, go with a authentication server (Cisco) if you really want secure transmissions.
I would do as suggested before and look at the Compaq site for a patch....