The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The PPPoE on Bridge Domain Interface feature enables configuration and initiation over a VLAN domain. PPPoE over BDI allows clients to establish an authentic and secured PPPoE session with the remote PPPoE server over a VLAN domain.
Before you can configure the PPPoE on BDI feature, enable PPPoE, and specify a virtual template for PPPoE sessions.
PPPoE is supported only on BDIs created over the Ethernet ports.
PPPoE is not supported on the Cisco ASR 900 Series RSP3 module.
One PPPoE client is supported per node/router.
PPPoE client over BDI is used to get configuration file from server over vlan domain. The BDI or the virtual interface used by PPPoE client should not be used for routing.
PPPoE server is not supported.
PAP and CHAP are the supported authentication methods.
Traceback messages appear when PPPoE session is initiated over the BDI tagged interface. You need to clear the PPPoE traceback error messages from the server side.
To set the limit of sessions to be sourced from a MAC address, use the following command in VPDN configuration mode:
|
Command |
Purpose |
|---|---|
|
Sets the limit of sessions to be sourced from a MAC address. |
The Virtual Template Interface Service feature provides a generic service that can be used to apply predefined interface configurations (virtual template interfaces).
For example you can enable PPP authentication on the virtual template using the ppp authentication chap command to be used for PPPoE session.
PPPoE session can be enabled using virtual template or using Dialer interface
To create and configure a virtual template, use the following commands beginning in global configuration mode:
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
Router(config)# interface virtual-template number |
Creates a virtual template, and enters interface configuration mode. |
|
Step 2 |
Router(config-if)# mtu bytes |
Sets the maximum transmission unit (MTU) size for the interface. |
|
Step 3 |
Router(config-if)# ip address negotiated |
Obtains IP address via PPP/IPCP negotiation. |
|
Step 4 |
Router(config-if)# ppp authentication chap |
Sets the maximum transmission unit (MTU) size for the interface. |
Use pppoe client dialer interface to initiate the pppoe session.
|
Command |
Purpose |
|---|---|
|
Creates a Dialer interface. |
|
Specifies the IP address Dialer interface as a node in the destination network to be called. The IP address can be obtained during IPCP negotiation. |
|
Specifies the PPP encapsulation. |
|
Specifies the dialing pool to use for calls to this destination. |
|
Assigns the Dialer interface to a dialer group. This applies the specified traffic definition to the interface. |
|
Enables Cisco Discovery Protocol (CDP) on the interface. |
|
Specifies the PPP authentication method. This is only needed if you are not doing CLID or DNIS-based binding. |
|
Specifies the PPP user-name and password for the Password Authentication Protocol (PAP). |
|
Specifies the PPP Challenge Handshake Authentication Protocol (CHAP) hostname. |
|
Specifies the PPP CHAP password. |
To enable PPPoE on BDI, use the following command in global configuration mode:
|
Command |
Purpose |
||
|---|---|---|---|
|
Specifies a bridge domain interface on the router. |
||
|
Specifies the group to be used for establishing PPPoE sessions. |
||
|
Configures a PPP over Ethernet (PPPoE) client and specifies the dialer interface.
|
To monitor the PPPoE session, use the following commands in EXEC mode:
|
Command |
Purpose |
|---|---|
|
Displays PPPoE session details with remote as well as local MAC and session count details. |
interface Dialer1
ip address negotiated
encapsulation ppp
dialer pool 1
dialer-group 1
no cdp enable
ppp authentication pap chap callin
ppp pap sent-username r1 password r2
ppp chap hostname r1
ppp chap password r2The following example enables PPPoE on a BDI:
interface bdi1
pppoe enable
pppoe-client dial-pool-number 1The following example specifies virtual template for PPPoE session:
bba-group pppoe global
virtual-template 1
interface Virtual-Template1
mtu 1492
ip address negotiated
ppp authentication pap
ppp pap sent-username r1 password 0 r2
inter BDI10
pppoe enable group global
no shut
The following sections provide references related to the PPPoE on BDI feature.
|
Related Topic |
Document Title |
|---|---|
|
Configuring PPPoE on ATM |
PPPoE over ATM |
|
Configuring PPPoE on IEEE 802.1Q encapsulation |
PPPoE Over IEEE 802.1Q VLANs |
|
Standard |
Title |
|---|---|
|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
— |
|
MIB |
MIBs Link |
|---|---|
|
No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature. |
To locate and download MIBs for selected platforms, Cisco IOS XE releases, and feature sets, use Cisco MIB Locator found at the following URL: |
|
RFC |
Title |
|---|---|
|
RFC 2516 |
A Method for Transmitting PPPoE |
|
RFC 4813 |
Multiprotocol Encapsulation over ATM Adaptation Layer 5 |
|
Description |
Link |
|---|---|
|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. |
Feedback