08-24-2015 11:48 AM
I am looking for information step-by-step when a wifi client associates and authenticates on the network. I am interested in DHCP process (what happens between client, controller and DHCP server) and authentication process (what happens between client, controller and AD).
Can anyone suggest?
08-24-2015 07:39 PM - edited 08-24-2015 08:18 PM
What kind of authentication are you referring to?
What level of detail do you require? There are many ways to describe this based on what you actually need.
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
08-25-2015 07:12 AM
Here is your answer,
Client connectivity will pass through 3 phases,
3.Getting IP Address
Association completes (Open Auth) L1 connectivity and then Authention(dot1x) Completes L2 connectivity and then and Client will get IP address on successful Authentication.
1. Association: between Client <-->
Auth request<->Auth Response
Association Req <--> Association Resp
2. Authentication :
1. Here Controller+AP works like Authenticator and exists between Client and Auth server (RADIUS+AD)
2. Till the EAP negotiation Controller will convey handshakes between Client and Auth server
3. Once EAP tunnel is establishes between Client and Auth server, client traffic is not visible to the controller
4. Client will share it's credentials with the Server directly, on successful authentication, Authserver will send RADIUS success message to the controller and shares the Master session key with controller and Client
5. with the help of master session key Client and controller ( AP) will perform dot11i key exchange to derive a temporal key for encrypting the traffic.
After successful Authentication, Controller will allow the usertraffic, i.e it will allow DHCP traffic
Controller will process DHCP traffic and helps the client to get an IP address.
Hope you got some clarity on this.
[Is my post helped you ? Give Kudos :) ]