PPP Dialer interface

Hi,

The dial control center (DCC) provides the on-demand dialing service for users. The DCC can be configured on the routers connected by an Integrated Services Digital Network (ISDN) or a 3G network or on the routers functioning as a PPPoE/PPPoEoA/PPPoA client connecting to a PPPoE/PPPoEoA/PPPoA server.

The routers set up a connection by dialing only when there is data to be transmitted between them. That is, they start the DCC process to transmit signal, and tear down the connection when no data is transmitted on the link.

A dialer interface is a logical interface that is used to implement DCC. After a physical interface is bound to a dialer interface, the physical interface inherits the configurations of the dialer interface.
Refer to: https://support.huawei.com/hedex/hdx.do?docid=EDOC1100069307&id=interface_dialer&lang=en

https://support.huawei.com/hedex/hdx.do?docid=EDOC1100007335&id=dc_cfg_dcc_0001&lang=en

So you are right, when the device acts as the PPPoE client, the dialer interface should be configured.

Dialer profiles separate logical configurations from the physical interfaces that receive or make calls. Because of this separation, interfaces such as ISDN, asynchronous modems, or synchronous serial connections can be shared by multiple dialer profile configurations. Dialer profiles allow logical and physical configurations to be bound together dynamically on a per call basis, allowing physical interfaces to take on different characteristics based on incoming or outgoing call requirements. They also can define encapsulation, access control lists, minimum or maximum calls, and toggle features on or off.

The components of a dialer profile include:

• Dialer interfaces—Logical entities that use a per-destination dialer profile. Any number of dialer interfaces can be created in a router. All configuration settings specific to the destination go in the dialer interface configuration. Each dialer interface uses a dialer pool, which is a pool of physical interfaces (ISDN BRI and PRI, asynchronous-modem, and synchronous serial).

• Dialer pool—Each interface references a dialer pool, which is a group of physical interfaces associated with a dialer profile. A physical interface can belong to multiple dialer pools. Contention for a specific physical interface is resolved by configuring the optional priority command.

• Physical interfaces—Interfaces in a dialer pool are configured for encapsulation parameters. The interfaces are also configured to identify the dialer pools to which the interface belong. Dialer profiles support PPP and High-Level Data Link Control (HDLC) encapsulation.

• Dialer map-class (optional)—Supply configuration parameters to dialer interfaces (for example, ISDN speed, dialer timers parameters). A map-class can be referenced from multiple dialer interfaces.

Configuring PPP over Ethernet with NAT

Multiple PCs can be connected to the LAN behind the router. Before the traffic from these PCs is sent to the PPPoE session, it can be encrypted, filtered, and so forth

PPPoE

The PPPoE Client feature on the router provides PPPoE client support on Ethernet interfaces. A dialer interface must be used for cloning virtual access. Multiple PPPoE client sessions can be configured on an Ethernet interface, but each session must use a separate dialer interface and a separate dialer pool.

A PPPoE session is initiated on the client side by the Cisco 850 or Cisco 870 series router.An established PPPoE client session can be terminated in one of two ways:

•https://www.cisco.com/en/US/i/templates/blank.gifBy entering the clear vpdn tunnel pppoe command. The PPPoE client session terminates, and the PPPoE client immediately tries to reestablish the session. This also occurs if the session has a timeout.

•https://www.cisco.com/en/US/i/templates/blank.gifBy entering the no pppoe-client dial-pool number command to clear the session. The PPPoE client does not attempt to reestablish the session.

NAT

NAT (represented as the dashed line at the edge of the Cisco router) signifies two addressing domains and the inside source address. The source list defines how the packet travels through the network.

Configuration Tasks

Perform the following tasks to configure this network scenario:

•https://www.cisco.com/en/US/i/templates/blank.gifConfigure the Virtual Private Dialup Network Group Number

•https://www.cisco.com/en/US/i/templates/blank.gifConfigure the Fast Ethernet WAN Interfaces

•https://www.cisco.com/en/US/i/templates/blank.gifConfigure the Dialer Interface

•https://www.cisco.com/en/US/i/templates/blank.gifConfigure Network Address Translation

Configuring a Dialer Interface

Procedure

1. Run system-view

   
   

   The system view is displayed.

   
   

2. (Optional) Configure a dialer ACL.

   
   

3. 
   

   1. Run dialer-rule

      
      

      The dialer rule view is displayed.

      
      

   2. Run dialer-rule dialer-rule-number { acl { acl-number | name acl-name } | ip { deny | permit } | ipv6 { deny | permit } }

      
      

      A dialer ACL is specified for a dialer access group.

      
      

      
      

      By default, no dialer ACL is configured.

      
      

   3. Run quit

      
      

      Return to the system view.

      
      

4. Run interface dialer number

   
   

   A dialer interface is created and the dialer interface view is displayed.

   
   

5. Run dialer user user-name

   
   

   The RS-DCC function is enabled.

   
   

   
   

   By default, the RS-DCC function is disabled and the remote user name is not configured.

   
   

6. Run dialer bundle number

   
   

   A dialer bundle is specified for the dialer interface.

   
   

7. (Optional) Run dialer-group group-number

   
   

   A dialer access group is configured for the dialer interface

8. (Optional) Run dialer retry limit counts quiet-period period

   
   

   A quiet period and the maximum number of retransmissions within the quiet period are set.

   
   

9. (Optional) Configure NAT.

   
   

   If the device functions as a PPPoE client on an IPv4 network and connects to users in a downstream LAN, you need to configure NAT on the device to translate the users' private IP addresses into public IP addresses so that the users can access the Internet.

   For details, see NAT Configuration in the Huawei AR Series IOT Gateway Configuration Guide - IP Services.

   
   

10. (Optional) Configure the device to allow international mobile subscriber identity (IMSI) or serial number (SN) negotiation.

    
    

    To enhance PPPoE user access security, the PPPoE server may need to authenticate the IMSIs or SNs of PPPoE clients. In this case, the PPPoE server requests PPPoE clients to send packets carrying the IMSI or SN during LCP negotiation. If the device functions as a PPPoE client and receives the request from the PPPoE server, the device does not send a packet carrying the IMSI or SN to the PPPoE server during LCP negotiation. The PPPoE server then cannot authenticate the device's IMSI or SN.

    To solve this problem, configure the PPPoE client to allow IMSI or SN negotiation.

• Run ppp lcp imsi accept

  The PPPoE client is configured to allow IMSI negotiation during LCP negotiation.

  By default, a PPPoE client does not allow IMSI negotiation during LCP negotiation.

• Run ppp lcp sn accept

  The PPPoE client is configured to allow SN negotiation during LCP negotiation.

  By default, a PPPoE client does not allow SN negotiation during LCP negotiation.