Hello everyone,
This post refers to the issue that the portal authentication is successful, but the user cannot access the internet, as part of the Troubleshooting Series on the Forum. Please see more below.
Physical Network Topology
The network where the portal authentication is successful, but the user cannot access the internet.
![]()
Fault description
After a user associates its terminal with Wi-Fi, a Portal page is displayed. The user enters the user name and password for authentication. The "verification succeeded!" message is displayed.
The administrator can find this user in the online user list on the Agile Controller, but the RADIUS server attribute is empty.
The administrator can also find a record in the login log, but the RADIUS Authentication Log has no data.
The administrator cannot find the user on the AC by running the display access-user command. The user cannot access the Internet.
Figure 1-2. One of the symptoms
![]()
Figure 1-3. One of the symptoms
![]()
Troubleshooting procedure
Step 1. The terminal initiates authentication on the Portal page. The Agile Controller searches for the corresponding authentication device from the device management module based on the terminal IP address. If the access terminal IP list configured for the authentication device contains the IP address of the terminal, the Agile Controller sends Portal packets to the authentication device. If the Access terminal IP list field is not configured for authentication devices, the Agile Controller cannot find the target authentication device and does not send Portal packets to the authentication device. Instead, the Agile Controller authenticates the user name and password locally. If the authentication succeeds, the Agile Controller returns to the "verification succeeded!" message.
Step 2. In this case, online users cannot be found on the authentication device because the Agile Controller does not initiate interaction with the authentication device.
Step 3. In Portal authentication, the Agile Controller sends Portal packets to the authentication device, and then the authentication device sends RADIUS packets to the Agile Controller. Due to the configuration error, the Agile Controller does not interact with the authentication device, and no RADIUS authentication log is generated.
Solution
Configure the Access terminal IP list field on the Authentication Parameters tab page.
![]()
Root cause
On the Device Management menu of the Agile Controller, the Access terminal IP list field on the Authentication Parameters tab page is not configured.
![]()
This is what I want to share with you today, thank you!