Requirements
The AFC Proxy Server and Geolocation Service Server are only accessible to registered RUCKUS client devices (meaning, devices that have successfully onboarded to a RUCKUS controller, and are in the Operational state). Therefore, ensure that the client devices are registered before deploying the AFC workflow.
It is necessary to have a RUCKUS Cloud account with valid credentials to enable AFC on the controller.
Firewall Requirements for AFC
To ensure proper AFC operation deployments, configure the firewall to allow outbound HTTPS (TCP port 443) connectivity to the following RUCKUS cloud services.
Domains
| Domain | Purpose |
|---|---|
| serviceloc.ruckuswireless.com | Service Locator used to discover AFC, Geolocator, and dAuth service endpoints. |
| afc.ruckus.cloud | AFC Proxy service used for AFC spectrum inquiries and response retrieval. |
| geolocation.ruckus.cloud | Geolocator service used for AP geolocation. |
| ruckus.cloud | Cloud Authentication (dAuth/OAuth) service used to obtain access tokens for AFC and Geolocator services. |