Perform the following:
iS5comm# show dot1x
Sysauthcontrol = Enabled
Module Oper Status = Enabled
Dot1x Protocol Version = 2
Dot1x Authentication Method = Radius
Nas ID = fsNas1
At
RADIUS-Server:
Assume that the Free
RADIUS server code is used for
this configuration. Customize the following sample files available
in the raddb directory (available in the path \etc\raddb in Linux).
users
clients.conf
radiusd.conf
An
example is shown below.
- In the file users, include the
following line to allow a user named iS5comm with password iss123
and authentication type as EAP.
"[email protected]" Auth-Type := EAP, User-Password == "iss123"
- In the file clients.conf, specify the RADIUS client
information.
client 13.0.0.5 {
secret = IS5ComRadius
shortname = Rad
nastype = other
}
- In the file radiusd.conf, specify the encryption scheme for EAP.
eap {
default_eap_type = md5
timer_expire = 60
md5 {
}
leap {
}
}
chap {
authtype = CHAP
}
At
root:
#radiusd –X -A
At
Host:
- SecureSupplicant (mdc-ssd) in the file
mdc-ssd/chap-secrets (available in the path \etc\mdc-ssd in Linux)
identity
Server Secret
[email protected] * iss123
- Run the Meetinghouse
Data Communications SecureSupplicant (802.1x protocol supplicant daemon).
#mdc-ssd logfd 1 nodetach ifname eth0 identity [email protected]
The
packet flows between the host, RADIUS client,
and the RADIUS Server is illustrated
in the figure below.
Figure 1. Packet Flow between
Supplicant, RADIUS CLIENT, and RADIUS server
