Wireless authentication query's

hello all,

i'm just looking for a few straight answers regarding wireless authentication on WPA2 networks, since i can never seem to find a straight answer on any Cisco docs.

would appreciate answers on any of the following;

1. when deploying WAP's in standalone mode, that is, they are configured independantly, no WLC is used, but they ARE using the same SSID, so i guess they are classed as an ESS. How do clients authenticate when roaming between AP's? do the clients need to go through the whole re-authentication process when roaming to the new AP?, and need new encryption key material for the new AP etc?

2. in WPA2 mode, for authentication, i see that in infrastructure mode, when using PEAP, the authentication process is encrypted between the client and the AP / RADIUS server. My question is this... in WPA2 personal PSK mode, how is the password passed securely between the client and the AP? Is there some secure connection which is set up prior to the key being passed to the AP?

3. How is the AES session encryption key securely exchanged between the client and AP in either PSK or enterprise mode?

i understand how this type of exchange works when connecting to an SSL web server (server passes public rsa key to client, client uses this to encrypt the session keys and passes back to the server which uses it's private key to decrypt and find the session keys. i just never seem to find a good explanation of how this sort of stuff works in wireless.

please can somebody help explain, or point me in the right direction of a good link?

thanks in advance.
L-PlateAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jackie ManCommented:
The answer for your Question 2:-

Authentication in the WPA2 Personal mode, which does not require an authentication server, is performed between the client and the AP generating a 256-bit PSK from a plain-text pass phrase (from 8 to 63characters). The PSK in conjunction with the Service Set Identifier and SSID length form the mathematical basis for the PMK (Pair-wise Master Key) to be used later in key generation.

Source: http://cs.gmu.edu/~yhwang1/INFS612/Sample_Projects/Fall_06_GPN_6_Final_Report.pdf
0
Lance_PCommented:
As far as I have tested, If you have multiple AP's, you need to have the ALL on the SAME SSID. But make sure that the nearby AP's are on DIFFERENT channels to avoid interference.

This should work without issues. I have setup a similar network at home as well with 3 AP's. No issue's.

I do not see why there would be any issues with Radius or any security since all the matters is that the AP be setup correctly to communicate with the Authentication server and that the SSID matches.
0
RikeRCommented:
Hi L-Plate,

1. If you configure the network to use WPA or WPA2 enterprise the client has to re-authenticate when roaming to a different AP. The reason being that the pairwise master key is being derived from the Radius server. A mechanism to prevent this is called PMK-caching which is only possible if there is some sort of intelligence glue-ing the accesspoint together. In most casses this is the Wireless controller.

2. When using pre-shared key authentication the PMK is allready known by both parties (client and accesspoint) calculated as jackieman states. Have a look at this video as it desribes the process very clear: http://www.securitytube.net/video/1905

3. How these key are being used to feed AES is beyond my knowledge.

Good luck

/steven
0
Darr247Commented:
For #3,  the key is in fact never actually exchanged. Very simplified, only negotiation vectors are exchanged, and if the client doesn't already know the proper key it can't make the proper response vectors to create a secured session. Even if the exchanged negotiation packets are captured, they can't be worked backwards because they are created by mixing in a "number used once" (NONCE) rather than the passphrase by itself. Both sides take the other's challenge packet, decrypt it using what they think the key is, then create a response packet using the result. If either side has a different passphrase, the responses don't match what they're supposed to be and the session is discarded.

If the wrong key is tried more than twice in 30 seconds, the WPA2 spec makes it stop allowing new connections for 2 minutes. That limits brute force hack attempts to a maximum of 4 per minute, so it would take about 2 days for a properly constructed hacker 'bot to go through a 10,000 entry dictionary just to discover you didn't use a common passphrase (like "password" or "qwertyuiop" et cetera)... or longer if it tried 3 times in 30 seconds and got locked out from trying for 2 minutes. Keep that in the back of your mind for when the symptom shows up of not being able to connect without waiting 2 minutes. ;-)
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Wireless Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.