04-24-2017 07:45 PM
The user gets the initial role and successfully pops up the portal,but the page is the controller's login page.That's why?
The login page under the aaa authentication captivepartal profile is correct.
Manually enter the portal address can pop up portal.
04-25-2017 12:29 AM
Hey, would you be able to post a copy of your configuration so we can review? If the role is being assigned correctly and the login page is set to /auth/index.html then maybe it is a browser cache issue? Does it happen with all clients?
If my post addresses your query, give kudos:)
04-25-2017 03:51 AM
3: No inter vlan routing enabled in between the guest network and CPPM
Make sure that we have enabled inter Vlan routing. For instance , say that the CPPM, Controller and AP are on Management Vlan ( Vlan 1) while the guest clients gets and ip from Vlan 10. Ensure that the VLAN interface for the Guest network on the controller has an IP
address assigned to it, otherwise the HTTP TCP SYN&ACK will take an asynchronous routing path which will not work.
04-30-2017 09:49 PM
Please paste the following outputs:
show user-table | include <ip-address of user>
We can check the role assigned to the user from the above command.
The, run the following command:
#show rights <role assigned to user>
From the above command we can see the captive portal profile mapped to the user-role.
Run the following command to verify the login-url in the captive portal profile mapped to the user-role:
show aaa authentication captive-portal <name of captive-portal profile>