---
description: TIP OpenWiFi 2.0
---

# Discovery without Cloud

There could be reasons cloud discovery does not complete.\
These include:

* Lack of Internet Connectivity
  * Device may require additional WAN settings
  * Network may not be connected to Internet
* No Configuration of Cloud in Certificate Authority&#x20;
  * Manufacturer may have left this value blank in the device record stored in Certificate Authority

![Manual Cloud Entry](https://1332596523-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MMa5rA2dKyutvejS11x%2F-Mf9n1nFShYpu0JZOadY%2F-Mf9oHgHT0ZhFMtLjylq%2Fimage.png?alt=media\&token=571e76c7-d9b5-4e0b-b130-640651bc6de0)

When the cloud can not be automatically discovered, OpenWiFi devices will turn on a local admin web UI made available via SSID "Maverick".

The Maverick UI will support configuring WAN interface parameters, including DHCP, Static, PPPoE, and LTE/5G settings. Please see [Local Device Settings](../access-points/local-device-settings) for details on using Maverick.\
[  \
](../access-points/local-device-settings)Additionally the Maverick UI supports direct entry of the cloud for cases when the cloud value has not been supplied during manufacture.

For non-Wi-Fi devices such as PoE access switches, the same cloud location information may be configured using local management interface.

![Admin / User Entered WAN or Cloud](https://1332596523-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MMa5rA2dKyutvejS11x%2F-Mf9n1nFShYpu0JZOadY%2F-Mf9pHz_oDyBMfDrgAtF%2Fimage.png?alt=media\&token=b2f70779-e6f3-4e84-92fc-ad1152422bf1)
