Page History

...

RDK-B devices provide multiple interfaces like MoCA, WiFi, Ethernet and so on for the , etc. for clients to get connected. LMLite, a component within RDK-B, does the job of updating the Host tables table (Host table is a table containing the data of connected clients over various interfaces) based on the devices connected over MoCA, WiFi and Ethernet.

...

LMLite interacts with other components of RDK-B stack over DBUS. Each of these components registers a "callback" function with respective HAL. The HAL performs a “callback” whenever there is an update in connected clients. This triggers a DBus call to LMLite with the necessary data. LMLite receives this data and adds it to a the Host tablestable.

Notifications

LMLite notifies the Notification component which in turn tells the interested PAs about the connection and disconnection of the connected devices.

...

Example: For WiFi the dedicated parameter is
“Device.Hosts.X_RDKCENTRAL-COM_LMHost_Sync_From_WiFi”.
This parameter is of string type and contains values for fields phyAddr, ssid, status and so on, etc.

NotifyMsg 2

In this type of notification message, LMLite monitors the values of all the connected clients. Whenever For any connection/disconnection updates happen in host table is updated, it updates the notify component. The data sent from LMLite to notify component is status, MAC, interface of the connected device.

...