rdkcentral/onewifi

Purpose and runtime entry

OneWifi is an RDK-B C/C++ component that centrally manages WiFi radios, VAPs, clients, security, statistics, telemetry, and optional mesh/optimization features. It runs as a system service, with SSP lifecycle/bootstrap code starting the WiFi manager and platform bus integration.

• source/dml/wifi_ssp/ssp_main.c

• source/dml/wifi_ssp/ssp_loop.c

• scripts/onewifi.service

Core orchestration and control

wifi_mgr owns global WiFi state, hardware capabilities, and subsystem handles. The control engine is the asynchronous boundary: northbound changes, HAL indications, timers, and app requests are queued and processed before hardware/state updates. This separates request handlers from potentially slow apply operations.

• source/core/wifi_mgr.c

• source/core/wifi_ctrl.c

• source/core/wifi_ctrl_queue_handlers.c

Northbound management interfaces

TR-181/DML exposes Device.WiFi.* through RBus/CCSP-facing callbacks. Cloud configuration enters through WebConfig JSON decoding, schema-specific handlers, validation, and encoding. Both paths converge on manager/database/control flows rather than directly manipulating the HAL.

• source/dml/tr_181/ml/cosa_wifi_dml.c

• source/dml/dml_webconfig/dml_onewifi_api.c

• source/webconfig/wifi_decoder.c

Configuration, persistence, and schema boundary

The database layer mediates WiFi configuration and operational state, backed by OVSDB support and cached structures. WebConfig supports distinct subdocuments for radio, private/home SSIDs, mesh, steering, telemetry-related data, and other features. Schemas are a compatibility contract with configuration producers.

• source/db/wifi_db.c

• lib/ovsdb/ovsdb.c

• config/rdkb-wifi.ovsschema

Southbound WiFi and service application

Core data-plane/control code translates normalized state into WiFi HAL operations and reacts to hardware events. VAP services encode service-specific behavior—private, public, and mesh gateway/pod/extender—rather than scattering VAP policy across the controller. The platform layer abstracts Linux, OpenWrt, RDK-B, DBus, and bus differences.

• source/core/wifi_data_plane.c

• source/core/services/vap_svc.c

• source/platform/rdkb/bus.c

Applications, measurement, and telemetry

An application manager hosts independently enabled modules such as EasyMesh, statistics monitoring, active Blaster tests, CAC, CSI/motion sensing, station management, analytics, and client steering. Statistics collection is a major outbound flow: radio/VAP/client measurements are gathered, transformed, and can use Avro/OpenSync datapipeline artifacts for telemetry.

• source/apps/wifi_apps_mgr.c

• source/stats/wifi_monitor.c

• lib/datapipeline/dppline.c

Infrastructure and dependencies

The component targets Linux-based RDK-B and OpenWrt builds, with platform-specific makefiles and deployment configuration. Material runtime integrations are WiFi HAL/hostapd-wpa_supplicant beneath the component; RBus/CCSP PSM/PandM alongside it; OVSDB for local persistence; and WebConfig, WebPA/Parodus, and telemetry services for cloud interaction. Feature flags select mesh, WiFi 7/MLO, CSI, CAC, and other app modules.

• build/linux/makefile.common

• build/openwrt/Makefile_package

• configure.ac