MSR v9 series routers do not send charging packets after PPPOE authentication
- 0 Followed
- 0Collected ，9Browsed
Network Topology
The MSR router functions as a PPPOE server and interfaces with RADIUS for AAA authentication
Problem Description
The MSR router functions as a PPPoE server and interfaces with RADIUS for AAA authentication.
Users can go online normally. Through debug and packet capture analysis, it is acknowledged that after user authentication (Uauth) succeeds, the device does not send charging packets, causing the user to go offline due to charging timeout.
Process Analysis
Checked the virtual template configuration and found no error. Most cases of not sending charging packets are due to the lack of ppp account-statistics enable configuration, but this time the configuration is complete.
#
interface Virtual-Template1
ppp authentication-mode chap domain login
remote address pool cgnat
ppp account-statistics enable
Checked the RADIUS status and found it active with no flapping block.
Primary accounting server:
Host name: Not configured
IP : 10.254.246.50 Port: 1813
VPN : Not configured
State: Active (duration: 0 weeks, 0 days, 22 hours, 8 minutes, 45 seconds)
Weight: 0
Checked the domain configuration and found the private network user attribute user-address-type private-ipv4 configured. This attribute is used in CGN scenarios, while regular NAT does not require it. Since MSR routers currently do not support the CGN attribute, this configuration caused abnormal user login and failed charging.
#
domain name login
accounting quota-out online
authentication ppp local radius-scheme 1
authorization ppp local radius-scheme 1
accounting ppp radius-scheme 1 local
user-address-type private-ipv4
Solution
Tested normally after removal
#
domain name login
accounting quota-out online
authentication ppp local radius-scheme 1
authorization ppp local radius-scheme 1
accounting ppp radius-scheme 1 local