Home » D-Link Manuals » Hubs & Switches » D-Link DES-3528 » Manual Viewer

D-Link DES-3528 Product Manual - Page 212

Authentication Server, Authenticator, Client

UPC - 790069314346

Add to My Manuals
Save this manual to your list of manuals

Page 212 highlights

xStack® DES-3528/DES-3552 Series Layer 2 Stackable Fast Ethernet Managed Switch Web UI Reference Guide The following section will explain the three roles of Client, Authenticator and Authentication Server in greater detail. Authentication Server The Authentication Server is a remote device that is connected to the same network as the Client and Authenticator, must be running a RADIUS Server program and must be configured properly on the Authenticator (Switch). Clients connected to a port on the Switch must be authenticated by the Authentication Server (RADIUS) before attaining any services offered by the Switch on the LAN. The role of the Authentication Server is to certify the identity of the Client attempting to access the network by exchanging secure information between the RADIUS server and the Client through EAPOL packets and, in turn, informs the Switch whether or not the Client is granted access to the LAN and/or switches services. Figure 8-3 The Authentication Server Authenticator The Authenticator (the Switch) is an intermediary between the Authentication Server and the Client. The Authenticator serves two purposes when utilizing the 802.1X function. The first purpose is to request certification information from the Client through EAPOL packets, which is the only information allowed to pass through the Authenticator before access is granted to the Client. The second purpose of the Authenticator is to verify the information gathered from the Client with the Authentication Server, and to then relay that information back to the Client. Figure 8-4 The Authenticator Three steps must be implemented on the Switch to properly configure the Authenticator. 1. The 802.1X State must be Enabled. (Security / 802.1X /802.1X Settings) 2. The 802.1X settings must be implemented by port (Security / 802.1X / 802.1X Settings) 3. A RADIUS server must be configured on the Switch. (Security / 802.1X / Authentic RADIUS Server) Client The Client is simply the end station that wishes to gain access to the LAN or switch services. All end stations must be running software that is compliant with the 802.1X protocol. For users running Windows XP and Windows Vista, that software is included within the operating system. All other users are required to attain 802.1X client software from an outside source. The Client will request access to the LAN and or Switch through EAPOL packets and, in turn will respond to requests from the Switch. Figure 8-5 The Client 203

Section	Page
Intended Readers	10
Typographical Conventions	10
Notes, Notices and Cautions	10
Chapter 1 Web-based Switch Configuration	11
Introduction	11
Login to the Web Manager	11
Web-based User Interface	12
Web Pages	13
Chapter 2 System Configuration	14
Device Information	14
System Information Settings	15
Dual Configuration Settings	16
Firmware Information Settings	17
Port Configuration	18
PoE	21
Serial Port Settings	24
System Log configuration	25
Time Range Settings	29
Time Settings	29
User Accounts Settings	30
Stacking	31
Chapter 3 Management	35
ARP	35
Gratuitous ARP	37
IPv6 Neighbor Settings	38
IP Interface	39
Management Settings	43
Session Table	44
Single IP Management	44
SNMP Settings	54
Telnet Settings	64
Web Settings	64
Chapter 4 L2 Features	65
VLAN	65
Q-in-Q	88
Layer 2 Protocol Tunneling Settings	90
Spanning Tree	91
Link Aggregation	100
FDB	103
L2 Multicast Control	107
Multicast Filtering	132
ERPS Settings	136
LLDP	139
Chapter 5 L3 Features	149
Local Route Settings	149
IPv4 Static/Default Route Settings	149
IPv4 Route Table	150
IPv6 Static/Default Route Settings	151
IPv6 Route Table	151
Policy Route Settings	152
IP Forwarding Table	153
Chapter 6 QoS	154
802.1p Settings	156
Bandwidth Control	159
Traffic Control Settings	161
DSCP	164
HOL Blocking Prevention	167
Scheduling Settings	168
SRED	171
Chapter 7 ACL	174
ACL Configuration Wizard	174
Access Profile List	175
CPU Access Profile List	193
ACL Finder	207
ACL Flow Meter	208
Chapter 8 Security	211
802.1X	211
RADIUS	224
IP-MAC-Port Binding (IMPB)	229
MAC-based Access Control (MAC)	236
Web-based Access Control (WAC)	240
Japanese Web-based Access Control (JWAC)	245
Compound Authentication	252
Port Security	256
ARP Spoofing Prevention Settings	258
BPDU Attack Protection	259
Loopback Detection Settings	261
Traffic Segmentation Settings	262
NetBIOS Filtering Settings	263
DHCP Server Screening	264
Access Authentication Control	265
SSL Settings	274
SSH	276
Trusted Host Settings	280
Safeguard Engine Settings	281
Chapter 9 Network Application	284
DHCP	284
DNS	296
PPPoE Circuit ID Insertion Settings	298
SNTP	299
Chapter 10 OAM	302
CFM	302
Ethernet OAM	311
DULD Settings	315
Cable Diagnostics	316
Chapter 11 Monitoring	318
Utilization	318
Statistics	320
Mirror	332
sFlow	334
Ping Test	337
Trace Route	338
Peripheral	340
Chapter 12 Save and Tools	341
Save Configuration ID 1	341
Save Configuration ID 2	341
Save Log	342
Save All	342
Stacking Information	342
Download Firmware	344
Download Configuration File	344
Upload Configuration File	345
Upload Log File	346
Reset	347
Reboot System	347
Appendix A Mitigating ARP Spoofing Attacks Using Packet Content ACL	348
How Address Resolution Protocol Works	348
How ARP Spoofing Attacks a Network	350
Prevent ARP Spoofing via Packet Content ACL	351
Configuration	351
Appendix B System Log and Trap List	354
System Log Entries	354
DES-3528/DES-3552 Series Trap List	362
Proprietary Trap List	362
Appendix C Password Recovery Procedure	365

Match case Limit results 1 per page

xStack® DES-3528/DES-3552 Series Layer 2 Stackable Fast Ethernet Managed Switch Web UI Reference Guide

The following section will explain the three roles of Client, Authenticator and Authentication Server in greater detail.

Authentication Server

The Authentication Server is a remote device that is

connected to the same network as the Client and

Authenticator, must be running a RADIUS Server program

and must be configured properly on the Authenticator

(Switch). Clients connected to a port on the Switch must be

authenticated by the Authentication Server (RADIUS)

before attaining any services offered by the Switch on the

LAN. The role of the Authentication Server is to certify the

identity of the Client attempting to access the network by

exchanging secure information between the RADIUS

server and the Client through EAPOL packets and, in turn,

informs the Switch whether or not the Client is granted

access to the LAN and/or switches services.

Figure 8-3 The Authentication Server

Authenticator

The Authenticator (the Switch) is an intermediary between

the Authentication Server and the Client. The

Authenticator serves two purposes when utilizing the

802.1X function. The first purpose is to request

certification information from the Client through EAPOL

packets, which is the only information allowed to pass

through the Authenticator before access is granted to the

Client. The second purpose of the Authenticator is to

verify the information gathered from the Client with the

Authentication Server, and to then relay that information

back to the Client.

Figure 8-4 The Authenticator

Three steps must be implemented on the Switch to properly configure the Authenticator.

The 802.1X State must be

Enabled

. (

Security / 802.1X /802.1X Settings

)

The 802.1X settings must be implemented by port (

Security

802.1X

802.1X Settings

)

A RADIUS server must be configured on the Switch. (

Security

802.1X

Authentic

RADIUS Server

)

Client

The Client is simply the end station that wishes to gain

access to the LAN or switch services. All end stations

must be running software that is compliant with the

802.1X protocol. For users running Windows XP and

Windows Vista, that software is included within the

operating system. All other users are required to attain

802.1X client software from an outside source. The Client

will request access to the LAN and or Switch through

EAPOL packets and, in turn will respond to requests from

the Switch.

Figure 8-5 The Client

203