PPPoE Service Reference
Complete reference for PPPoE (Point-to-Point Protocol over Ethernet) subscriber services in the Nokia BNG Lab.Overview
PPPoE is a method for encapsulating PPP frames inside Ethernet frames, commonly used for broadband connections. It provides authentication, encryption, and compression capabilities.Key Features
- PAP/CHAP Authentication: Flexible authentication methods
- Session Management: Per-subscriber PPP sessions
- IPv4 and IPv6: Dual-stack support
- NAT Integration: Automatic NAT for IPv4 subscribers
- RADIUS Integration: Centralized authentication and accounting
PPPoE Policy Configuration
Policy Parameters
| Parameter | Value | Description |
|---|---|---|
| ppp-authentication | pref-pap | Prefer PAP, fallback to CHAP |
| ppp-initial-delay | true | Delay LCP negotiation slightly |
| ppp-mtu | 1500 | Maximum PPP frame size |
| reply-on-padt | true | Send PADT response on termination |
| keepalive interval | 10 | LCP echo interval (seconds) |
| hold-up-multiplier | 4 | Missed keepalives before timeout (40s) |
Authentication Methods
Authentication Methods
Authentication Configuration
RADIUS Authentication Policy
- Password: testlab123 (shared secret)
- Access Method: PAP-CHAP (both supported)
- Re-authentication: Enabled (RADIUS-triggered)
- Fallback: Local database “clientes”
Local User Database
Group Interface Configuration
- Admin State: Enabled
- Policy: “pppoe” (with keepalive, MTU, etc.)
- Session Limit: 131,071 total sessions
- SAP Session Limit: 131,071 per SAP
- User DB: “clientes” (fallback)
PPPoE Session Establishment Flow
Complete Session Setup
Discovery Phase
-
PADI (PPPoE Active Discovery Initiation)
- Client broadcasts to find PPPoE servers
- Contains service name (optional)
-
PADO (PPPoE Active Discovery Offer)
- BNG responds with its MAC address
- Offers PPPoE service
-
PADR (PPPoE Active Discovery Request)
- Client requests session from specific BNG
- Unicast to BNG MAC
-
PADS (PPPoE Active Discovery Session-confirmation)
- BNG assigns unique Session ID
- PPP session begins
Session Phase
-
LCP (Link Control Protocol)
- Negotiates PPP parameters
- MTU, authentication method, etc.
-
Authentication (PAP/CHAP)
- Client sends credentials
- BNG validates via RADIUS or local DB
-
IPCP (IP Control Protocol)
- Negotiates IPv4 address
- DNS servers, default route
-
IPv6CP (IPv6 Control Protocol)
- Negotiates IPv6 parameters
- Interface identifier
Session Termination
Graceful Termination
Keepalive Timeout
Subscriber Session Example
PPPoE Session Details
Verification Commands
Troubleshooting
PPPoE Discovery fails (no PADO)
PPPoE Discovery fails (no PADO)
Symptoms: Client sends PADI but receives no PADOCheck:Debug:
- PPPoE enabled on group interface
- Capture SAP operational
- VPLS forwarding
Authentication fails
Authentication fails
Symptoms: PADS sent but LCP/Auth failsCheck:Debug:Common Issues:
- RADIUS connectivity
- Username/password correct
- Shared secret matches
- Wrong RADIUS shared secret
- RADIUS server unreachable
- User not in RADIUS database
- Password mismatch
Session established but no IP connectivity
Session established but no IP connectivity
Check:Common Causes:
- IPCP negotiation successful
- Default route installed
- NAT configuration
- IPCP not negotiating IP address
- NAT pool exhausted
- Routing issue
- Filter blocking traffic
Session drops unexpectedly
Session drops unexpectedly
Check keepalive:Possible causes:
- Keepalive timeout (no LCP echo response)
- Link failure
- PADT from client
- RADIUS disconnect/CoA
MTU issues / fragmentation
MTU issues / fragmentation
Symptoms: Large packets fail, small packets workCheck PPP MTU:Solution:
- PPP MTU: 1500
- Consider MSS clamping for TCP
- Adjust MTU in RADIUS if needed