Ieee 802.1X Extensible Authentication Protocol Types - D-Link DWS-1008 - AirPremier MobileLAN Switch Product Manual

2. To configure server-1 and server-2 into server-group-1, the administrator enters the
following command:
DWS-1008# set server group server-group-1 members server-1 server-2
3. To enable PEAP offload plus local authentication for all users of SSID mycorp at @example.
com, the administrator enters the following command.
DWS-1008# set authentication dot1x ssid mycorp *@example.com peap-mschapv2
server-group-1 local

IEEE 802.1X Extensible Authentication Protocol Types

Extensible Authentication Protocol (EAP) is a generic point-to-point protocol that supports multiple
authentication mechanisms. EAP has been adopted as a standard by the Institute of Electrical and
Electronic Engineers (IEEE). IEEE 802.1X is an encapsulated form for carrying authentication messages
in a standard message exchange between a user (client) and an authenticator.
The table below summarizes the EAP protocols (also called types or methods) supported by MSS.
EAP Type
EAP-MD5
Authentication algorithm that
(EAP with Message
uses achallenge-response
Digest
mechanism to compare hashes.
Algorithm 5)
Protocol that provides mutual
authentication, integrity-
EAP-TLS
protected encryption algorithm
(EAP with Transport
negotiation, and key exchange.
Layer
EAP-TLS provides encryption
Security)
and data integrity checking for
the connection.
The wireless client
PEAP-MSCHAP-V2
authenticates the server
(Protected EAP with
(either the switch or a RADIUS
Microsoft Challenge
server) using TLS to set up
Handshake
an encrypted session. Mutual
Authentication
authentication is performed by
Protocol version 2)
MS-CHAP-V2.
D-Link DWS-1008 User Manual
Description
Wired authentication only 1
Wireless and wired
authentication. All
authentication is processed on
the switch.
Wireless and wired
authentication:
• The PEAP portion is
processed on the switch.
• The MS-CHAP-V2 portion
is processed on the RADIUS
server or locally,
depending on the configuration.
Use
This protocol provides
no encryption or key
establishment.
This protocol requires X.509
public key certificates on
both sides of the connection.
Requires use of local
database. Not supported
for RADIUS.
Only the server side of the
connection requires a
certificate.
The client needs only a
username and password.
Considerations
80