04-10-2023 10:18 AM
My customer's captive portal has stopped working. I'm using the controller itself to authenticate, the controller log shows timeout and reason code 8 and sometimes reason code 3. And it doesn't open the captive portal page.
Have you seen this problem?
Solved! Go to Solution.
04-13-2023 08:52 AM
You have a cluster between the 2 NX5500s (primary/standby). Captive portal policy is mapped on both controllers as well as the AP7522.
Please remove the captive portal policy from the AP7522
The firewall is disabled and is required to be enabled for proxy-arp
The NX5500 VLAN 300 is configured as such:
nx5500 40-83-DE-86-3B-88
interface vlan300
description "Guest outside"
ip address 192.168.110.2/23
nx5500 40-83-DE-86-94-C0
interface vlan300
ip address 192.168.110.2/24
Captive portal policy is configured as such:
captive-portal Captive-Caieras
server host 192.168.110.2
server mode centralized
Please reconfigure the captive portal policy server mode to centralized controller, hosting vlan 300, and use a non-resolvable host name (example: wing.cp.com). Just ensure its non-resolvable.
04-11-2023 06:16 AM
Looks like this:
Reason Code 8 Disassoc because STA is leaving BSS
Reason Code 3 Deauth because sending STA is leaving IBSS or ESS