| EAP NAK |
|
|
| Written by Devin Akin | |
| Tuesday, 04 September 2007 | |
|
While it's often not a topic of discussion because EAP types are usually manually configured, supplicants and authentication servers can "negotiate" an EAP authentication protocol type. Now this is where it gets interesting. The above 3 steps are generic to every EAP type used in wireless. The next EAP frame is unique per EAP type. Before this frame, you don't know which type of EAP you're going to be dealing with. EAPoL-Request (PEAP, EAP-TTLS, LEAP, TLS, etc) ..... Authentication Server (AS) > Authenticator > Supplicant. This unique frame informs the supplicant of the EAP type that the AS wants to use for this authentication session. The AS decides on which type of EAP it wants to start based on a priority list (if multiple EAP types are supported on the AS). If the station doesn't support the specified EAP type, it will send a NAK to the AS along with a suggested EAP type. This "suggestion" is found in the "Authentication Type" field specified in RFC2284. A nice list of these authentication types can be found on page 165 of this document. If the AS supports the suggested EAP type, it will then start that EAP type with the supplicant. If not, then it move to the next highest-priority supported EAP type and start the process over at the "4th" EAPoL-Request frame. For example: EAPoL-Start EAPoL-Request/ID EAPoL-Response/ID EAPoL-Request (PEAP-Start) EAPoL-Response (NAK + Suggested EAP type = LEAP) EAPoL-Request (LEAP) EAPoL-Response (LEAP) EAPoL-Success or EAPoL-Start EAPoL-Request/ID EAPoL-Response/ID EAPoL-Request (PEAP) EAPoL-Response (NAK + Auth Type = LEAP) EAPoL-Request (TTLS) EAPoL-Response (NAK + Auth Type = LEAP) EAPoL-Request (TLS) EAPoL-Response (NAK + Auth Type = LEAP) Comments (1)
![]() ... written by Batjedi, September 05, 2007
interesting
Write comment
|
| < Prev | Next > |
|---|
Add this feed to your online news reader