When an AP cannot reach the controller, it goes into "SELFRUN" state.
In this state, it doesn't make sense to redirect the guests to the portal (controller) which is not reachable, so the AP will automatically allow guests to use the network without redirecting. Moreover:
- The guest access policies will still be effective (L2/L3 isolation) along with the restricted subnets feature
- The user group (bandwidth limiting, etc) associated with this WLAN will still be effective.
- When the controller comes back online (and the AP goes into MANAGED state), the guest portal redirection feature will restore automatically.
How to Configure "SELFRUN" State
The config.properties file needs to be placed under <unifi_base>/data/sites/<site id>/ directory because config properties are site related. Note: Prior to version 3, users were able to add/modify <unifi_base>/data/config.properties.
|Note: The location <unifi_base> will vary depending on your operating system. See this article for more information.|
# config.selfrun_guest_mode=pass # when controller is offline, automatically # authorize all guests (all guest isolation # / policy is still enforced) # config.selfrun_guest_mode=off # to disable all the guest SSIDs when controller # is not reachable. Note that "guest portal" must # be being used otherwise controller will NOT disable # guest SSIDs.
| Warning: When choosing a line to enter into the config.properties file, do NOT enter any comments, or hashtag symbols before or after. So for example, to disable guest SSID when in SELFRUN mode the line in config.properties would look like the following: