7
Configuring CHAP authentication (authenticator name is not
configured)
Restrictions and guidelines for CHAP authentication (authenticator name is not configured)
For local AAA authentication, the username and password of the peer must be configured on the
authenticator.
For remote AAA authentication, the username and password of the peer must be configured on the
remote AAA server.
The username and password configured for the peer must meet the following requirements:
•
The username configured for the peer must be the same as that configured on the peer by
using the
ppp chap user
command.
•
The password configured for the peer must be the same as that configured on the peer by using
the
ppp chap password
command.
Configuring the authenticator
1.
Enter system view.
system-view
2.
Enter interface view.
interface interface-type interface-number
3.
Configure the authenticator to authenticate the peer by using CHAP.
ppp
authentication-mode
chap
[
[
call-in
]
domain
{
isp-name
|
default
enable
isp-name
}
]
By default, PPP authentication is disabled.
4.
Configure local or remote AAA authentication.
For more information about AAA authentication, see
Security Configuration Guide
.
Configuring the peer
1.
Enter system view.
system-view
2.
Enter interface view.
interface interface-type interface-number
3.
Configure a username for the CHAP peer.
ppp chap user
username
The default setting is null.
4.
Set the CHAP authentication password.
ppp chap password
{
cipher
|
simple
}
string
The default setting is null.
For security purposes, the password specified in plaintext form and ciphertext form will be
stored in encrypted form.
Configuring MS-CHAP or MS-CHAP-V2 authentication
Restrictions and guidelines for MS-CHAP or MS-CHAP-V2 authentication
The device can only act as an authenticator for MS-CHAP or MS-CHAP-V2 authentication.
L2TP supports only MS-CHAP authentication.
