Uploaded July 2025 | Updated November 2026, 1 hour ago
This talk showcases automation features developed in order to support the entire lifecycle of running Wireless LANs (WLANs) on commodity hardware from the adoption of the Wireless Access Points (WAPs) into a command and control system to provisioning of the actual WLANs. The OpenWiFi Gateway (OWGW), which is deployed as a VM with custom bootstrapping logic, and the OpenWiFi WAPs both run open source software from the Telecom Infrastructure Project (TIP). The onboarding lifecycle involves generating SSL certificates on these devices and sending those certificates to a Certificate Authority for signing, then using these certificates for mutual authentication between the OWGW and the WAPs via mutual Transport Layer Security (mTLS). This creates a web of trust between devices in the environment. Management of the Certificate Authority for this purpose is also included.
After the WAPs are onboarded, they must be provisioned with configuration based on operator intent. This is accomplished via JSON API transactions with the OWGW and Websocket transactions between the OWGW and the WAPs. This means that many WLAN configuration options, e.g., Open, Pre-Shared Key (PSK), multiple Pre-Shared Key via Remote Authentication Dial In User Service (mPSK-RADIUS), hidden, 2.4/5/6 GHz, WiFi Protected Access 2/3 (WPA2/3, including transitional WPA), tunneling via Generic Routing Encapsulation (GRE) and Opportunistic Wireless Encryption (OWE), are operator-configurable parameters that get translated into device configuration JSON. The operator can configure the WLANs appropriate to their environment, whether it be a Multi Dwelling Unit (MDU), a Large Public Venue (LPV), or something else, via a vendor neutral Web UI and then see the appropriate configuration be generated and pushed to all WAPs in their environment. In addition to the configuration management, operational state is continuously monitored through the KAFKA telemetry streams, and firmware updates can be initiated through a convenient web interface.
This talk showcases automation features developed in order to support the entire lifecycle of running Wireless LANs (WLANs) on commodity hardware from the adoption of the Wireless Access Points (WAPs) into a command and control system to provisioning of the actual WLANs. The OpenWiFi Gateway (OWGW), which is deployed as a VM with custom bootstrapping logic, and the OpenWiFi WAPs both run open source software from the Telecom Infrastructure Project (TIP). The onboarding lifecycle involves generating SSL certificates on these devices and sending those certificates to a Certificate Authority for signing, then using these certificates for mutual authentication between the OWGW and the WAPs via mutual Transport Layer Security (mTLS). This creates a web of trust between devices in the environment. Management of the Certificate Authority for this purpose is also included.
After the WAPs are onboarded, they must be provisioned with configuration based on operator intent. This is accomplished via JSON API transactions with the OWGW and Websocket transactions between the OWGW and the WAPs. This means that many WLAN configuration options, e.g., Open, Pre-Shared Key (PSK), multiple Pre-Shared Key via Remote Authentication Dial In User Service (mPSK-RADIUS), hidden, 2.4/5/6 GHz, WiFi Protected Access 2/3 (WPA2/3, including transitional WPA), tunneling via Generic Routing Encapsulation (GRE) and Opportunistic Wireless Encryption (OWE), are operator-configurable parameters that get translated into device configuration JSON. The operator can configure the WLANs appropriate to their environment, whether it be a Multi Dwelling Unit (MDU), a Large Public Venue (LPV), or something else, via a vendor neutral Web UI and then see the appropriate configuration be generated and pushed to all WAPs in their environment. In addition to the configuration management, operational state is continuously monitored through the KAFKA telemetry streams, and firmware updates can be initiated through a convenient web interface.










