06-30-2011 01:24 PM
06-30-2011 01:53 PM
1) pass the first captive portal
2) stop there, and observe the 'role' that your user is in AFTER the first captive portal.... is it 'guest' ? is it 'guest login' is it something custom ?
3) check the Firewall policies on the controller for that role, specifically analyze if 'captive-portal' is a firewall policy in this role.
Sounds like the authenticated role you are in after the first public captive portal still have a captive portal redirect for http/https, instead of just a permit rule set.
07-06-2011 07:21 AM