scottk/wlan-docs
1
0
Fork 0
mirror of https://github.com/Telecominfraproject/wlan-docs.git synced 2025-11-24 21:54:53 +00:00
Code Issues Packages Projects Releases Wiki Activity

GitBook: [#3] No subject

Browse Source
This commit is contained in:
Chris Busch
2022-03-10 14:32:57 +00:00
committed by gitbook-bot
parent 782621dc76
commit 7b019d1874
212 changed files with 12247 additions and 154 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
getting-started/access-points/README.md Normal file
View File

@@ -0,0 +1,31 @@
---
description: TIP OpenWiFi 2.0
---
# Access Points
Initial Minimum Viable Product Release 2.0 does not include template driven device provisioning, this will be available in the next sprint.
Given many cloud and ODM partners wish to consume the 2.0 reference stack early, some with their own device provisioning logic as part of commercial cloud controllers, the following describes uCentral based management and telemetry, interactions with the OpenWiFi SDK processing provisioning and telemetry data.
## Device Interactions with SDK
![OpenWiFi with uCentral Management](<../../.gitbook/assets/image (22) (2).png>)
OpenWiFi 2.0 follows the uCentral system. Complete data model is available [here](http://ucentral.io/docs/ucentral-schema.html). Upon discovery of the cloud, a device default or specific configuration is transferred.
All devices are known to the cloud by their unique id and provisioned based on advertised capabilities. Each configuration generates a new unique hash value to ensure as devices report back to the cloud, their configuration state is guaranteed.
If the cloud sends invalid configuration data or the device has insufficient ability to complete the provisioning commands, the error handling process will send this response back to the cloud.
For example results returned to SDK from a device configuration error:
```
"results": {
"serial": "aabbcc00120a",
"status": {
"error": 0,
"rejected": [
"[W] ("A Reason will be given"
],
```

57
getting-started/access-points/local-device-settings.md Normal file
View File

@@ -0,0 +1,57 @@
---
description: OpenWiFi 2.0 Devices
---
# Local Device Settings
When OpenWiFi devices are unable to connect to the cloud during their initial power on from factory, this may be a result of Internet connectivity issues.
Certain WAN connections may require credentials such as a username and password or a mobile configuration or simply static address assignment instead of dynamic.
OpenWiFi 2.0 supports these scenarios. When a device does not have an existing configuration and is unable to contact the cloud for provisioning it enters "Maverick" mode.
For all Wi-Fi devices this means a Wi-Fi network with the SSID 'Maverick' will become available.\
Association with and logging in to the device will permit initial WAN connectivity to be entered.
## Using Maverick
![Maverick Login Page](<../../.gitbook/assets/Screen Shot 2021-07-29 at 5.04.23 PM.png>)
After association to the Maverick SSID, open a web browser to `http://192.168.1.1`\
Log into the OpenWiFi device with username: **`root`** and password: **`openwifi`**
![Logged into Maverick](<../../.gitbook/assets/Screen Shot 2021-07-29 at 5.06.35 PM.png>)
When the page above is displayed, begin to configure Uplink based on the WAN requirements of the deployment.
![Uplink Configuration in Maverick](<../../.gitbook/assets/Screen Shot 2021-07-29 at 5.07.50 PM.png>)
If connection uses Point to Point over Ethernet (PPPoE) username and password credentials, enter those values and save.
![PPPoE Uplink](<../../.gitbook/assets/Screen Shot 2021-07-29 at 5.09.14 PM.png>)
If the OpenWiFi device has a Cellular connection which is possible on device models with 4G and 5G radios, the network Access Point Name (APN) and PIN will be required. These values are supplied by your mobile network provider.
![Cellular Uplink](<../../.gitbook/assets/Screen Shot 2021-07-29 at 5.11.05 PM.png>)
When dynamic address allocation is not available, static IP address assignment may be required. IPv4 and IPv6 are supported, enter these values with DNS address and save.
![Uplink Static IP](<../../.gitbook/assets/Screen Shot 2021-07-29 at 5.12.39 PM.png>)
Otherwise leave the Uplink configuration to DHCP or cloud defaults.
![Uplink DHCP](<../../.gitbook/assets/Screen Shot 2021-07-29 at 5.13.40 PM.png>)
## Manual Redirector and Certificate Upload
If under rare circumstances it is not possible to discover the OpenWiFi cloud associated with the device or there is a need to replace device certificates, this may be configured in Settings.
![Local Redirector Setting](<../../.gitbook/assets/Screen Shot 2021-07-29 at 5.16.01 PM.png>)
## System
It is possible to reset the device to defaults, or locally update firmware using the commands available from System.
![System Commands](<../../.gitbook/assets/Screen Shot 2021-07-29 at 5.17.13 PM.png>)
\*\*\*\*