Motorola TEAM Badge (EWB100), Deployment Manual

Page: 32 / 146

EWB100 Usage and Deployment Guide Rev 1.13
Page 32
6 PEAP Authentication (Rev J)
6.1 Introduction
The EWB100 supports PEAP authentication for secure networking. The
implemention provides the following features:

PEAP authentication compatible with PEAP v1 specification

Server certification checking to provide mutual authenticate

A number of key caching mechanisms including opportunistic key caching
In order to operate, their must be PEAP server accessible to the device as well
as APs that have been properly configured. Consult the documentation for the
server and WLAN infrastrucuture for details on how to do this.
The EWB supports a two key caching modes: Pairwise Master Key (PMK) and
Opportunistic Key Caching (OKC). If supported by the WLAN infrastructure,
OKC is much more efficient as only one PEAP authentication sequence is
required regardless of the number of AP. PMK requires the EWB to authenticate
at least once with each AP. When using PMK, the EWB only maintains PMKs for
32 APs. If there are more than 32 APs, the EWB will reuse
the information “slot”
with the oldest PMK.
6.2 Configuration Parameters
6.2.1 Enable peap
This command enables and disables PEAP operation. The command is:
Set ra wpa2sec x
Where x = “none” to disable peap and “peap” to enable peap. It is disabled by
default.
6.2.2 User Default peap enable - defwpa2esec
This command sets the user default setting to enable and disable PEAP
operation. It operates as do other user default settings.
The command is:
Set ra defwpa2sec x
Where x = “none” to disable peap and “peap” to enable peap. It is disabled by
default.