Netgear ME103 ME103 Reference Manual - Page 51

Advanced Configuration, Configuring Advanced Security 802.1x Options

Get Netgear ME103 - 802.11b ProSafe Wireless Access Point PDF manuals and user guides
UPC - 606449026375
View all Netgear ME103 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 51 highlights

Chapter 5 Advanced Configuration This chapter describes how to configure the advanced features of your ME103 802.11b ProSafe Wireless Access Point. These features can be found under the Advanced heading in the main menu. Configuring Advanced Security 802.1x Options For an overview of 802.1x, see "Understanding 802.1x Port Based Network Access Control" on page B-9. The ME103 802.11b ProSafe Wireless Access Point supports these 802.1x options: • Key Exchange. Key exchange (PEAP, EAP-TLS, EAP-TTLS) provides strong security through mutual authentication and automatic key exchange between the two endpoints. Periodic updates are performed using public-key cryptography through a certificate server and a Remote Authentication Dial-In User Service (RADIUS) server. The ME103 configuration procedures for these options are presented below. Basic Requirements for 802.1x 802.1x requires these parts: 1. Authenticator: ME103 2. Authentication Server - a RADIUS server. Microsoft Internet Authentication Server (IAS) provides RADIUS functionality. Other vendors also support RADIUS for 802.1x. 3. Supplicant - Windows 2000 with the 802.1x client patch applied (SP4 802.1x client) or Windows XP. 4. Optionally, the Key Exchange options (PEAP, EAP-TLS, and EAP-TTLS) can take advantage of a Certificate Authority (CA) such as Windows 2000 server provides. To use certificate-based authentication, both the RADIUS server and the client need to have a certificate from a certificate server such as Windows 2000 or a public service such as Verisign. Advanced Configuration 5-1 August 2003

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
Advanced Configuration
5-1
August 2003
Chapter 5
Advanced Configuration
This chapter describes how to configure the advanced features of your ME103 802.11b ProSafe
Wireless Access Point. These features can be found under the Advanced heading in the main
menu.
Configuring Advanced Security 802.1x Options
For an overview of 802.1x, see
“Understanding 802.1x Port Based Network Access Control” on
page B-9
. The ME103 802.11b ProSafe Wireless Access Point supports these 802.1x options:
•
Key Exchange
. Key exchange (PEAP, EAP-TLS, EAP-TTLS) provides strong security
through mutual authentication and automatic key exchange between the two endpoints.
Periodic updates are performed using public-key cryptography through a certificate server and
a Remote Authentication Dial-In User Service (RADIUS) server.
The ME103 configuration procedures for these options are presented below.
Basic Requirements for 802.1x
802.1x requires these parts:
1.
Authenticator: ME103
2.
Authentication Server - a RADIUS server.
Microsoft Internet Authentication Server (IAS) provides RADIUS functionality. Other
vendors also support RADIUS for 802.1x.
3.
Supplicant - Windows 2000 with the 802.1x client patch applied (SP4 802.1x client) or
Windows XP.
4.
Optionally, the Key Exchange options (PEAP, EAP-TLS, and EAP-TTLS) can take advantage
of a Certificate Authority (CA) such as Windows 2000 server provides. To use
certificate-based authentication, both the RADIUS server and the client need to have a
certificate from a certificate server such as Windows 2000 or a public service such as Verisign.