Configuring CHAP on DSL Interfaces (Optional)

For interfaces with PPPoA encapsulation, you can optionally configure interfaces to support the PPP Challenge Handshake Authentication Protocol (CHAP). When you enable CHAP on an interface, the interface can authenticate its peer and be authenticated by its peer.

If you set the passive option to handle incoming CHAP packets only, the interface does not challenge its peer. However, if the interface is challenged, it responds to the challenge. If you do not set the passive option, the interface always challenges its peer.

For more information about CHAP, see the Junos Network Interfaces Configuration Guide.

To configure CHAP on the ATM-over-ADSL or ATM-over-SHDSL interface:

Navigate to the top of the configuration hierarchy.
Perform the configuration tasks described in Table 47.
If you are finished configuring the J Series device, commit the configuration.
To check the configuration, see Verifying DSL Interface Configuration.

Table 47: Configuring CHAP

Task	CLI Configuration Editor
Navigate to the Access level in the configuration hierarchy.	From the [edit] hierarchy level, enter edit access
Define a CHAP access profile—for example, A-ppp-client—with a client named client 1 and the secret (password) my-secret.	Enter set profile A-ppp-client client client1 chap-secret my-secret.
Navigate to the appropriate ATM interface level in the configuration hierarchy—for example, at-3/0/0 unit 0.	From the [edit] hierarchy level, enter edit interfaces at-3/0/0 unit 0
Configure CHAP on the ATM-over-ADSL or ATM-over-SHDSL interface and specify a unique profile name containing a client list and access parameters—for example, A-ppp-client.	Enter set ppp-options chap access-profile A-ppp-client
Specify a unique hostname to be used in CHAP challenge and response packets—for example, A-at-3/0/0.0.	Enter set ppp-options chap local-name A-at-3/0/0.0.
Set the passive option to handle incoming CHAP packets only.	Enter set ppp-options chap passive