Configuring an External Captive Portal network.
FQDN should be resolvable by connecting end systems via DNS.
Note
Walled Garden rules are not required for this network. The process of enabling a captive portal on the network automatically creates rules allowing DNS, DHCP, and redirection rules. However, if users are unable to connect to the network, consider creating specific DNS and DHCP Allow rules as a Walled Garden configuration.When you enable Captive Portal on a WLAN ExtremeCloud IQ Controller automatically builds the role and redirect rules required for captive portal based on the Network Name configured in the WLAN.
Used when building a back-end captive portal server to integrate with the system. ExtremeCloud IQ Controller sends the Identity/Shared Secret and receives a response token.
Best Practice: Use https:// in the ECP URL and de-select this option.
Note
It is possible to authenticate directly to the AAA RADIUS server. Refer to the ExtremeCloud IQ Controller User Guide for information about AAA RADIUS Authentication.Configure a primary and backup if you have more than one Access Control Engine.
End-systems are re-authenticated on ExtremeCloud IQ Controller, not from the ExtremeCloud IQ Site Engine Access Control Engine. Therefore, ExtremeCloud IQ Controller ignores ExtremeCloud IQ Site Engine re-authentication requests to modify filter-ids (policies). Modification of these timeout values initiates re-authentication from the ExtremeCloud IQ Controller to the ExtremeCloud IQ Site Engine Access Control Engine, resulting in modification of the policy/filter-id as expected.
Note
There may be a delay or network interruption on policy changes. Adjust the timeout values if you do not see a timely policy change or if you experience network interruptions during the connection attempts from clients.