CHAPTER THREE - PL3000 BASICS
43
Wi-Fi
When you start configuring the wireless LAN (WLAN) interface on the PL3000,
you will make a decision on which of two available 802.1X supplicants you are
going to use for handling the WLAN connectivity. Together with the supplicant you
also choose how you configure the supplicant part of the WLAN communication.
On the ‘Main’ page of a Wi-Fi applet there is an ‘Active Profile’ field to choose
from the following profiles: ‘Default’ and ‘ThirdPartyConfig’. When the ‘Default’ is
selected, a third-party supplicant is in use. The ‘ThirdPartyConfig’ profile refers to a
Windows Embedded CE built-in supplicant. To avoid confusion over the concept of
‘third party’, in this text the ‘third party’ is used from the Windows CE perspective.
So, the Wi-Fi is a third-party utility to configure, to monitor, and to manage WLAN
interface and communication on the PL3000. The actual name of the applet is
‘Summit Client Utility’.
If you select the ‘Default’ profile in the Summit Client Utility (SCU), your
supplicant configuration utility is the SCU, and WLAN 802.1X stack is based on
OpenSSL Toolkit. On the contrary, if you select the ‘ThirdPartyConfig’ in the SCU,
your supplicant configuration utility is a Windows Embedded CE built-in Wireless
Zero Configuration (WZC) service, and WLAN 802.1X stack is a native Windows
CE implementation.
You may need the SCU, although the WZC is your supplicant configuration
utility. A ‘Global’ page in the SCU is independent of the Active Profile setting,
meaning that the settings on the ‘Global’ page apply to the WLAN interface no
matter which supplicant is in use. In addition, a ‘Profile’ page of the SCU also
relates to the ‘ThirdPartyConfig’ profile.