netviz

802.11 · WiFi

Captive portal (CWA) the guest network's bouncer

You join the café Wi-Fi and you're 'connected' instantly — but you're really in a holding pen with one door, to the login page. CWA is the bouncer. This plate shows every message that decides when the rope drops.

Sequence diagram poster of the WPA2 4-way handshake

Requesting scene from the content service…

MAB
starts the CWA flow
UDP 1700
the CoA port
redirect ACLChange of AuthorizationCisco ISEWeb Auth Pending

What you'll learn

  • How MAC Authentication Bypass (MAB) starts CWA and why the client lands in 'Web Auth Pending'.
  • What the redirect ACL and url-redirect in the RADIUS Access-Accept actually do.
  • Why the captive portal pops via the OS probe, and why HTTPS sites can't be silently redirected.
  • How Change of Authorization (CoA, UDP 1700) turns provisional access into full access without re-joining.
  • The two classic CWA failures: a redirect-ACL name mismatch (black hole) and a blocked CoA (logged in, no access).

Authentication that lives in the network, not the AP

Central Web Authentication separates joining from being authorized. The client associates to an open guest SSID and the controller runs MAC Authentication Bypass to a RADIUS server (Cisco ISE), which replies with provisional access: a redirect ACL that permits only DHCP, DNS and the portal, plus a URL to send the browser to. The user's credentials never touch the access point — they terminate at ISE.

When the user logs in or accepts the terms, ISE issues a Change of Authorization back to the controller, which re-evaluates the same session and applies full access. Nothing about the radio link changed; only permission did.

Where it breaks, and the Wi-Fi 6E successor

Two failures dominate CWA tickets, and the plate replays both: a redirect-ACL whose name ISE sends but the controller never defined (the client onboards into a black hole), and a Change of Authorization blocked by a firewall on UDP 1700 (the user logs in but access never opens). On a Wi-Fi 5 open SSID the link itself is cleartext, so the portal's HTTPS is the only thing protecting credentials — which is exactly why the Wi-Fi 6E plate runs the same flow over an OWE-encrypted link.

Atlas index