An engineer must implement a CPU ACL that blocks web management traffic to the controller, but they also must allow guests to reach a Web Authentication Redirect page. To which IP address is guest client HTTPS traffic allowed for this to work?
Guest web authentication uses the virtual interface of the controller. When a client opens a web page, the controller intercepts the request and redirects it to the web authentication page, which is served from the virtual IP address. Cisco notes that when CPU ACL rules are enabled, an allow rule for the virtual interface IP address is required. The rule must permit TCP, on port 80 if secure web is disabled or on port 443 if it is enabled. Otherwise, after the client authenticates and moves to the RUN state, the CPU ACL takes effect and blocks the client's access to the controller page, and the login redirect fails. The management IP address is the destination that the ACL should block for web management, the DNS server and the client interface are not the destinations of the redirect. Permitting HTTPS to the virtual interface IP lets guests reach the page while the management traffic remains restricted.
[Reference:Blueprint 8.3 (Implement Control Plane ACLs on the controller); Cisco Wireless Controller Configuration Guide, WLAN security, web authentication and CPU ACLs., ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit