Zero Touch Provisioning
OpenWiFi 2.0
OpenWiFi supports Zero Touch Provisioning in a number of ways.
Zero Touch Mesh
Zero Touch WDS
Zero Touch Provisioning ( Provisioning Services in upcoming 2.5/2.6 Release )
Onboarding
OpenWiFi makes use of TIP device certificates present on every access point as a secure identity from which to automate a number of Zero Touch operations.
Onboarding is a local EAP-TLS based authentication service available on any OpenWiFi device that works together with default OpenWiFi firstboot behavior to scan for "OpenWifi-onboarding"
SSID, associate to that SSID, when challenged supply TIP root signed device certificate.
Onboarding Steps
Provision an Access Point for onboarding role as an SSID config
{ "purpose": "onboarding-ap", "bss-mode": "ap", "encryption": { "proto": "wpa2", "ieee80211w": "required" }, "certificates": { "use_local_certificates": true }, "radius": { "local": { "server-identity": "uCentral-EAP" } }, "name": "OpenWifi-onboarding", "wifi-bands": [ "2G" ] }
Ensure the SSID for onboarding use provides network connectivity for clients
Any topology such as NAT, Bridge, VLAN may be used
Any radio(s) may be used
Firstboot devices with no WAN wired port detected will
Enable all radios
Scan for SSID "OpenWifi-onboarding"
Associate and when challenged use TIP certificate as identity
Obtain IP connection using DHCP over wireless interface association to onboarding AP
Connect to SDK, obtain provisioning from OpenWiFi Gateway service
Reload configuration
Zero Touch Mesh
Deployment of Mesh may have multiple Mesh Client access points with no wired connectivity. These devices use IEEE802.11s Mesh participating interface(s) as transit for WAN / LAN connections.
In a Zero Touch Mesh deployment, the Gateway Access Point, sometimes termed the Root node, advertises mesh participating interfaces when "bss-mode": "mesh"
is applied to an SSID. Please see Mesh for further details on initial setup.
Mesh Client Access Points needing to associate wirelessly for initial provisioning to join the mesh network, may be served using the onboarding feature of OpenWiFi.
Adding an SSID to the Mesh Gateway Access Point configuration to advertise "OpenWifi-onboarding"
enables initial boot of any OpenWiFi Access Point to reach the OpenWiFi Gateway.
Upon connection to Onboarding, the Access Point obtains management network access from the upstream Access Point providing "onboarding-ap"
service.
With management network access, reachability for the Mesh Client Access Point to the OpenWiFi Gateway should be possible, device provisioning stage will initiate with the production configuration being loaded to the client device.
Once processed, client Access Point will have receive provisioning to join the Mesh network as a Mesh Client Access Point.
Zero Touch WDS
Deployment of WDS links may have multiple WDS client devices with no wired WAN connectivity. WDS Access Points use the 4-tuple frame header with participating WDS Clients. Therefore WDS Clients must first receive provisioning from the OpenWiFi Gateway for their production state as a WDS link participant.
WDS Client Access Points needing to associate wirelessly for initial provisioning to join the WDS network, may be served using the onboarding feature of OpenWiFi from the WDS Root Access Point at the top of the topology with a "bss-mode": "ap"
SSID for onboarding.
Adding an SSID to the WDS Root Access Point configuration to advertise "OpenWifi-onboarding"
enables initial boot of any OpenWiFi Access Point to reach the OpenWiFi Gateway.
Upon connection to Onboarding, the WDS Client Access Point obtains management network access from the upstream WDS Root Access Point providing "onboarding-ap"
service.
With management network access, reachability for the WDS Client Access Point to the OpenWiFi Gateway should be possible, device provisioning stage will initiate with the production configuration being loaded to the client device. For more information on WDS configuration please consult WDS.
Once processed, WDS Client Access Point will have receive provisioning to join the WDS link as a Client WDS node.
Last updated