How can I configure PAP and CHAP authentication on the DCC

3

(C-DCC) On the calling party, if DCC is enabled on physical interfaces, configure PAP or CHAP authentication on the physical interfaces; if DCC is enabled for the dialer circular group, configure PAP or CHAP authentication on the dialer interface. Therefore, on the called party, you are advised to configure PAP or CHAP authentication on both physical interfaces and the dialer interface. When a physical interface receives a DCC request, it starts PPP negotiation and verifies the identity of the calling party, and then forwards the DCC request to the DCC module.

(RS-DCC) The RC-DCC set does not apply attribute information such as the PPP authentication command to the physical interfaces. You must configure authentication information on the physical interfaces on the called party. You must configure the dialer user and PPP authentication simultaneously on the dialer interface and physical interfaces. RS-DCC requires PPP negotiation using the physical interfaces and delivers the negotiated peer end user name to the DCC after negotiation. The DCC then determines the dialer interface based on the peer end use name and returns the dialer interface address to PPP. PPP allows the physical interfaces to perform IPCP negotiation based on the dialer interface configuration.

Other related questions:
What are the features of PAP and CHAP
PAP is short for Password Authentication Protocol. It supports 2-way handshake and transmits the password in plain text. The peer end controls the connection request. PAP cannot effectively prevent attacks. CHAP is short for Challenge Handshake Authentication Protocol. It supports 3-way handshake and transmits the password in cipher text. CHAP effectively prevents repeated trial-and-error attacks.

Authentication configuration in DCC
In the circular DCC method, if DCC can be enabled on the physical interface on the transmit end, configure the PAP or CHAP authentication on the physical interface. If the DCC is enabled by the Dialer Circular Group, configure the PAP or CHAP authentication on the Dialer interface on the transmit end. It is recommended that the PAP or CHAP authentication should be configured on both the physical interface and the Dialer interface on the receive end because the physical interface performs PPP negotiation and authenticates the user who dials up first and then forwards the call to the DCC module in the upper layer for further processing after receiving a DCC call request. In the resource-shared DCC method, attribute information about the shared attribute set is not applied to the physical interface of the dialer bundle (for example, the PPP authentication command is not applied to the physical interface), which indicates that the physical interface does not inherit attribute information from the shared attribute set. Therefore, authentication information must be configured on the physical interface on the receive end. In the resource-shared DCC method, authentication (including the dialer user configuration and PPP authentication) must be configured on both the Dialer interface and the physical interface. This is because in the resource-shared DCC method, the PPP negotiation must be performed through the physical interface and the negotiated peer user name must be sent to the DCC through the physical interface. The DCC determines the Dialer interface which needs to be used based on the received peer user name and sends the IP address of the dialer interface to the PPP, allowing the PPP to use the settings of the Dialer interface to perform the IPCP negotiation.

Can I configure resource-share DCC on physical interfaces
No, cannot configure resource-share DCC on physical interfaces.

Can the circular DCC and resource-shared DCC interwork
Yes, the circular DCC and resource-shared DCC interwork.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top