Skip to main content

OpenWiFi Quick Access Testing Guide

Helping Customers Rapidly Deploy OpenWiFi Test Environments

This guide helps customers quickly build and validate wireless testing environments based on the OpenWiFi architecture, utilizing existing network infrastructure, to enable a seamless experience with network controller functions, wireless network access, and management capabilities.

1 Components Required

To deploy the solution, you only need three components:
  1. Asterfusion’s OpenWiFi Access Points (APs) with preloaded firmware
  2. Standard Ethernet switch (provided by customer or Asterfusion)

2 Asteria Campus Controller Deployment & Network Architecture

2.1 Resource Requirements

Recommended environment:
  • x86 server
  • Ubuntu 18.04+
  • Docker 20+
AP Count
CPU
Memory
Disk
500
4 cores
8 GB
500 GB
1000
8 cores
16 GB
1 TB
1500
8 cores
16 GB
1.5 TB
2000
16 cores
32 GB
2 TB

2.2 Local Deployment

Upload the packaged controller software to your local environment and run the one-click install script. Use the -i parameter to set the controller’s IP address.
You can then access the controller directly via this IP.
network-controller-deployment-commands
Users can directly access the controller through this IP address.

2.3 Cloud Deployment

Cloud deployment requires the same resources and steps as local deployment.
Currently, you can also use our official cloud controller to manage your OpenWiFi APs without needing to deploy your cloud controller.
Enter https://app.cloudswitch.io/ in your browser

asteria-campus-controller-login-homepage

Contact Bd@Cloudswit.ch now to get your trial access!

2.4 AP Online Logic Diagram

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

2.5 Asterfusion Campus Topology

* We recommend using DHCP Option 138 for automatic controller access, and also provide manual controller address configuration as an alternative.

3 AP Online OpenWiFi Controller Methods

3.1 Method 1: Automatic Online via DHCP Option 138

DHCP Version: ISC-DHCP 4.3.5
The DHCP server needs to support configuring the Option 138 (capwap-ac) field, which is used to notify the AP of the cloud controller address.
Configuration content: Set Option 138 to the controller address, such as 192.168.18.141

Access process:
1. Import the AP’s MAC address into the inventory bound to the corresponding cloud controller account
Note: AP licenses need to be applied for through https://lic.asterfusion.com/. Please apply for the corresponding AP license information in advance; otherwise, the radio cannot be enabled after going online.

2. Connect the AP to the network and power it up
3. AP obtains IP and controller address from DHCP
4. AP automatically establishes a connection with the controller

3.2 Method 2: Manual Controller Address Configuration

If the DHCP server cannot configure Option 138, you can log into the AP via SSH or the serial port to manually set the controller address:
1. Import the AP’s MAC address into the inventory bound to the corresponding cloud controller account
2. Log into AP: ssh root@<AP-IP> or serial port login (default baud rate 115200)
3. Modify configuration file: /etc/ucentral/gateway.json

4. Modify the server field to the controller address, for example, 192.168.18.141
5. Restart the control process: /etc/init.d/ucentral restart
After completing the above steps, the AP will actively connect to the cloud controller.

4 Configure AP After Online

  • Add wireless configuration template

The device type and configuration tags in the configuration template must match the devices in inventory; otherwise, the configuration cannot be delivered.

Formally configure wireless services, including SSID, authentication method, wireless frequency band, etc. Click the Save button in the upper-right corner after configuration.

If there is a specific application scenario, the administrator can also customize the default configuration of the AP in the [advanced settings].

* For the detailed configuration process, please refer to →OpenWiFi Network Controller Usage Guide←

5 Compatibility with Other Hardware Platforms

In addition to our officially provided OpenWiFi APs, if customers already have the following devices, we can directly provide OpenWiFi images:
– EAP101
– EAP102
– EAP105
– RAP630C-311G
– hfcl_ion4xe

For devices not in the above list, please visit https://tip-1.gitbook.io/openwifi/about/supported-hardware to view the complete list of supported devices. We will adapt and compile OpenWiFi firmware according to specific models for customers to flash and access the controller.

6 Other Notes

  • Cloud controller is located on the public network, no need to deploy any local software or hardware controllers.
  • Controller supports multi-tenancy, remote configuration, log viewing, firmware delivery, AP health monitoring, and other functions.
  • All data is transmitted through encrypted channels by default, meeting enterprise-level security requirements.

7 Common Issues and Solutions

  • If AP cannot go online, check if DHCP successfully assigned an IP.
  • Check if Option 138 is correctly configured or if the manual configuration file is successfully saved.
  • If the controller cannot be accessed, check if the local network can access the public network.
  • For firmware flashing support or special model adaptation, please contact our support personnel.