Basic Requirements For 802.1X; 802.1X Security Settings Worksheet - NETGEAR WAG511 User Manual

User's Manual for the NETGEAR Dual Band Wireless PC Card 32-bit CardBus WAG511

Basic Requirements for 802.1x

802.1x requires these elements:
An 802.1x enabled wireless adapter with 802.1x client software such as the WAG511.
1.
An 802.1x enabled wireless access point.
2.
An 802.1x enabled RADIUS server with an optional Certificate Server.
3.
• For the EAP-TLS option, you need a Certificate Authority (CA) such as Windows 2000
server or a public service such as Verisign. Both the RADIUS server and the client need to
have a certificate from a certificate server.
• For the EAP-PEAP option, you need a RADIUS server and a certificate server. The
RADIUS server needs to have a certificate installed from a certificate server. The client
can dynamically download the certificate from the certificate server. However, depending
on how your network is set up, Windows Domain Controller or Active Directory login
credentials can be used for authentication.
Fill in the worksheet and use the procedure below to configure 802.1x settings of your WAG511.

802.1x Security Settings Worksheet

Print this form, fill in the configuration parameters and put it in a safe place for possible future
reference. For an existing wireless network, the person who set up the network will be able to
provide this information.
• Wireless Network Name (SSID)
The Service Set Identification (SSID) identifies the wireless local area network.
Note Some wireless access points will not broadcast their SSID as a security feature. In such
:
a case, you will need to get the SSID from the wireless network administrator.
Wireless network name (SSID): ______________________________
• 802.1x EAP Settings
— TLS
• Certificate: ___________________________________________________________
• CA Server: ___________________________________________________________
For example, CA Server: Netgear Https
• Domain Name: ___________________ Login Name: _________________
5-12
202-10041-01 September 2004
Wireless Security Configuration