Testlab WiFi setup
How to setup a full test lab including WiFi and Beacon
Last updated
Was this helpful?
How to setup a full test lab including WiFi and Beacon
Last updated
Was this helpful?
In order to test end-to-end the WiFi SDK capabilities, you need to prepare your environment by configuring properly your WiFi HW and your Cloud4Wi account.
To get started, you need an active Cloud4Wi account. Login your you account at
Add your test Access Points to a location (it can be any location as long as its Identity Domain is set to "Organization"). The value to use as MAC Address / NAS-ID depends on the specific WiFi vendor as detailed in the related configuration guide. Make sure the Access Points are not currently configured in any other Location or other Cloud4Wi Accounts.
Configure a new SSID The WiFi SDK is pre-configured to use a dedicated SSID name on the WiFi network, configured with the specific settings. Note that you need to add an additional dedicated SSID on top of those that you already have. The SSID name must be "Secure WiFi" in order to work with the Cloud4Wi Toolkit app in WPA2 Enterprise mode. For the Passpoint configuration, the domain value is "cloud4wi.securewifi.io" Depending on the WiFi vendor, you might need to set the same value in different configuration interfaces. The SSID cannot be hidden, it must be visible.
Configure the SSID with WPA2-Enterprise authentication and/or Passopint The configuration steps vary depending on the WiFi vendor ()
Configure RADIUS service As part of the WPA2-Enterprise settings, you have to configure the external RADIUS settings using the following parameters: - RADIUS Primary IP Address: 52.48.102.108 - RADIUS Secondary IP Address: 34.252.97.217 - Shared Secret: <will be communicated during account delivery>
Aruba
Most of the WiFi HWs support WPA2-Enterprise standard. If you can't find the documentation for your HW vendor, please contact our team for support