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.

Scroll to top