Scope

Scope of this release is for RDK-B community. This is our 2026 Annual RDK8 release of Banana Pi R4

Frequently Asked Questions

  • Can i use this release for production - Yes.
  • Does it cover all features - Yes
  • Can i share this release with my OEM's/Operators/SI's/SoC's - You are free to share
  • Can i contact RDKM team if i have any queries/to give any feedback - Yes
  • Is this release fully tested - Yes we have done End to End testing
  • Can i use release for my development/New enhancements - Yes
  • Does release support EasyMesh/Wi-Fi 7 - Yes 
  • Can i expand RAM in BPI R4 - You have to do it on Hand,Please refer here https://forum.banana-pi.org/t/bpi-r4-successfully-upgraded-8gb-ram-on-bpi-r4/17882/5

Host Setup

TBD

Build instructions

SD Build for Gateway

repo init -u https://code.rdkcentral.com/r/rdkcmf/manifests -b rdk8-1.0.0 -m rdkb-bpi-extsrc.xml
repo sync -j`nproc` --no-clone-bundle
MACHINE=bananapi4-rdk-broadband source meta-cmf-bananapi/setup-environment-refboard-rdkb
bitbake rdk-generic-broadband-image

SD Build for Gateway with EasyMesh 

repo init -u https://code.rdkcentral.com/r/rdkcmf/manifests -b rdk8-1.0.0 -m rdkb-bpi-extsrc.xml
repo sync -j`nproc` --no-clone-bundle
MACHINE=bananapi4-rdk-broadband FEATURE_TYPE=EasyMesh source meta-cmf-bananapi/setup-environment-refboard-rdkb
bitbake rdk-generic-broadband-image

SD Build for Extender with EasyMesh

repo init -u https://code.rdkcentral.com/r/rdkcmf/manifests -b rdk8-1.0.0 -m rdkb-bpi-ap-extsrc.xml
repo sync -j`nproc` --no-clone-bundle
MACHINE=bananapi4-rdk-broadband-ap-extender source meta-cmf-bananapi/setup-environment-refboard-rdkb
bitbake rdk-generic-ap-extender-image

SD Build for Gateway with USB RNDIS enabled

repo init -u https://code.rdkcentral.com/r/rdkcmf/manifests -b rdk8-1.0.0 -m rdkb-bpi-extsrc.xml
repo sync -j`nproc` --no-clone-bundle

Enable the distro for RNDIS in below path
/meta-cmf-bananapi/conf/distro/include/rdk-bpi.inc
#Enable the below DISTRO to enable Hybrid Hal(rndis/modem) for cellular devices
DISTRO_FEATURES_append_broadband = " cellular_hybrid_support"

MACHINE=bananapi4-rdk-broadband source meta-cmf-bananapi/setup-environment-refboard-rdkb
bitbake rdk-generic-broadband-image

SD Build for WiFiagent build

repo init -u https://code.rdkcentral.com/r/rdkcmf/manifests -b rdk8-1.0.0 -m rdkb-bpi-extsrc.xml
repo sync -j`nproc` --no-clone-bundle

Disable onewifi distro in below path for wifiagent build
/meta-cmf-bananapi/conf/distro/include/rdk-bpi.inc
# OneWifi feature
#DISTRO_FEATURES_append = " OneWifi onewifi_integration"

MACHINE=bananapi4-rdk-broadband source meta-cmf-bananapi/setup-environment-refboard-rdkb
bitbake rdk-generic-broadband-image

SD Build for Non-MLO build

repo init -u https://code.rdkcentral.com/r/rdkcmf/manifests -b rdk8-1.0.0 -m rdkb-bpi-extsrc.xml
repo sync -j`nproc` --no-clone-bundle

Disable generic_mlo distro in below path to trigger the non-mlo build
~/meta-cmf-bananapi/conf/distro/include/rdk-bpi.inc
#DISTRO_FEATURES_append = " generic_mlo"

MACHINE=bananapi4-rdk-broadband source meta-cmf-bananapi/setup-environment-refboard-rdkb
bitbake rdk-generic-broadband-image


NOTE: Prerequisite for SDCard build

Flashing instructions(SD card)

Tested machines - Linux,MacOs

Copy wic.bz2 from build machine

MacOs

  1. Install Balena etcher and flash using it

Linux

  1. bzip2 -d <Path to ImageName.wic.bz2>

  2. sudo -E bmaptool copy --nobmap <Path to ImageName.wic> <Path to SD card device file>

Boot mode

Yocto 

Kernel & user space

  • Kernel 6.6
  • Full 64bit (User space and kernel space)

Currently supported & working WAN technologies

  • ethwan
  • fixedwirelesswan

Wi-Fi highlights

  • 2.4 Ghz (wifi0)
  • 5 Ghz (wifi1)
  • 6 Ghz(wifi2)
  • Does it support multiple creations - As of now we have not created any VAP's.Technically that is possible based on requirement.
  • EasyMesh R6
  • WiFi 7 with MLO

Cellular Network highlights

  • Tested in North America & APAC regions for WWAN0,USB RNDIS


Flashing mechanism

Hardware & Peripherals

  • Banana Pi R4 Router Board
  • BE14 Wi-Fi 7 card & Antennas
  • Quectel EM05-G Cellular Modem
  • Power supply & Heat sinks
  • Android Phone
  • Silabs IOT radio,TP Link smart plug,onvis smart plug (Reference IoT usermanual for more details)
  • Case (Optional)
  • serial cable

How to get bananapi R4

Features supported in RDK8 Broadband release

  • featuressuported

Validation  Status

Sanity Status of GW build

S.NoUse caseStatus
1

erouter0 interface got Wan IPv4 and IPv6

PASS
2

brlan0 interface got default LAN IP & Ipv6

PASS
3

Able to take SSH Connection

PASS
4

All CCSP process are running

PASS
5

Able to Ping www.google.com & ping -6 www.google.com in Gateway (i,e erouter0)

PASS
6

All systemd services are running

PASS
7

Able to connect LAN client

PASS
8

LAN client got IP from default pool range for Ipv6 and Ipv4

PASS
9

LAN client should open with CaptivePortal Page

PASS
10

Able to connect wireless client

PASS
11

Wireless client got IP from default pool range(i,e 2G,5G,6G) for Ipv4 and Ipv6

PASS
12

Wireless client can access the CaptivePortal Page(i,e 2G,5G,6G)

PASS
13

Internet should work on Connected clients after changing the default credentials

PASS
14

Using dmcli to check the CCSP TR-181 DataModels

PASS
15

WebUI page should be loaded on Connected clients after changing the default credentials

PASS
16

WebUI page should be loaded through erouter0IP via RM

PASS
17

wifi0, wifi1, wifi2 interfaces should be UP and RUNNING

PASS
18

All ccsp logs files should be generated in /rdklogs/logs folder

PASS
19

Factory Reset

PASS
20

Device stable

PASS

Features Status of GW build

S.NoFeatures testedStatus
1

WebPa get and set should work, query device.

PASS
2

LogUpload/Logrotation 

PASS
3

RFC 

PASS
4

Webconfig

PASS
5

Telemetry 2

PASS
6

Usppa get and set are working through DM’s

PASS
7

Cellular Mode

PASS
8

Local WebUI

PASS

9

Firewall

PASS
10

WPA

PASS
11

CPU Proc Analyser

PASS
12

WAN Connectivity (i,e Ipv4)

PASS
13WAN Connectivity (i,e Ipv6)PASS
14

WiFi Connectivity

PASS
15

LAN Connectivity

PASS
16

SNMP

FAIL (RDKBACCL-1468)
17

Bridge Mode 

PASS
18DACPASS
19Firmware UpgradePASS
20TR069PASS
21eSDKFAIL (RDKBACCL-1102)
22PopulateSDKPASS
23SelfHealPASS
24Test and DiagnosticPASS
25Crash UploadPASS
26SD card supportPASS
27Factory resetPASS
28ACL (MAC Filtering)PASS
29Remote DebuggerPASS
30MAP-TPASS

Sanity Status of EM build

S.NoEM Use caseStatus
1onewifi systemd service should be RUNNING in ctrl and ExtenderPass
2No core files won't be observed in /tmp folder in ctrl and ExtenderPass
3systemctl status ieee1905_em_ctrl should be RUNNING state in ctrlPass
4systemctl status em_ctrl should be RUNNING state in ctrlPass
5systemctl status ieee1905_em_agent should be RUNNING state in ctrl and ExtenderPass
6systemctl status em_agent should be RUNNING state in ctrl and ExtenderPass
7check default db values are updated in mariadbPass
8EasyMesh and ieee1905 logs files should be generated in /tmp folder   for Controller and ExtenderPass
9All configured VAPs(fronthaul,backhaul,iot) should be UP and Running - to be confirm by iw dev command for both controller and ExtenderPass
10VAPs should be broadcasting EasyMesh default SSIDs(eg, private_ssid, mesh_backhaul) for both controller and ExtenderPass
11Able to connect clients via fronthaul vaps for both controller and extenderPass
12Able to get IP for fronthaul connected clientsPass
13Able to get Internet for fronthaul connected clientsPass
14mld0 interface should be created - to confirm by iw dev for both controller and ExtenderPass
15Mld0 interface should have linked with all private vaps for both controller and ExtenderPass
16In Extender ,Ensure mesh backhaul connectivity is established over 5G through wifi1.1 interface .
iw dev wifi1.3 info – use this command to confirm in Extender		Pass
17Verify mesh backhaul connection in EM-Contrller side as well. iw dev wifi1.1.sta<i> info iw dev wifi1.1.sta<i> station dump
## This command gives information on connected client ie Extender1.		Pass
18In Extender , ping 10.0.0.1 -c 5Pass
19Able to launch RDKB CLI in browser by using ctrl wan ip (i.e erouter0_IP:8888)Pass
20Able to Navigate all the tab in RDKB CLIPass
21In iw dev , Able to see the updated ssid in ctrl and Extender when we changing the ssid names from RDKB CLIPass
22Able to change password from RDKB CLIPass
23Able to change the channel from RDKB CLI for all available radio bandsFail
24Able to do wifi reset from RDKB CLIFail
25Able to see the N/W topology in CLIFail
26Able to connect clients with updated ssid for both controller and ExtenderPass
27Able to take ssh for both controller and ExtenderPass
28Able to make daisy chain and STAR TopologyPass
29Able to get IP for lan clients for both controller and ExtenderPass
30Able to get internet for connected lan clientsPass

List of Supported Features - User Manual's

  1. Webpa - WebPA Feature Support on BPI R4 - User Manual
  2. RFC -RFC Feature Support in RDKB BPI - User manual
  3. WebConfig -WebConfig Feature Support in RDKB - User Manual
  4. Telemetry 2 - Telemetry 2.0 Feature support for RDKB BPI -User Manual
  5. Log Rotate -Log Rotation Feature Support in RDKB BPI - User manual
  6. Cellular -  Cellular Feature support in RDKB BPI - User Manual
  7. UspPa 
    1.  Including UspPa in a device
    2. TR-369/USP on RDK-B
    3. OBUSPA 8.0 User Manual(Engineering Version)
  8. CpuProcAnalyser - Cpuprocanalyzer Feature support in RDKB BPI - User Manual
  9. OneWifi - OneWifi Integration in RDKB BPI - User Manual
  10. Selfheal - Self Heal Feature in BPI - User manual
  11. TR-69 - TR069 Support for Bananapi R4
  12. SNMP - SNMP Support for BPIR4 - Preferred Program - RDK Central Wiki
  13. OneWifi with Single WiPhy support 
    1. OneWifi Integration in RDKB BPI - User Manual
    2. Single wiphy design for Onewifi/rdk-wifi-hal
  14. Crashupload - Crash Upload Feature RDK-B - RDK - RDK Central Wiki
  15. Test and Diagnostics similar to RPI- Test and Diagnostic on R-Pi
  16. Bridge Mode similar to RPI- BridgeMode Feature support in RPI
  17. DAC similar to RPI 
    1. Containerization using META DAC SDK in RDK-B RPI
    2. DAC on BPI R4 RDK-B -64 bit
    3. iperf3 application
  18. eSDK - RDKB: Extensible SDK support on (BananaPi R4) Yocto 4.0 Kirkstone build
  19. PopulateSDK : Creating Yocto SDK 
  20. SD card support - SD Monolitic image build and flashing steps for BPI R4.
  21. SpeedTest  Support : IMP/gateway speedtest integration in Banana Pi R4 - Preferred Program - RDK Central Wiki
  22. WPS support https://wiki.rdkcentral.com/display/ASP/WPS+PBC+integration+in+RDK-B+BPI+R4
  23. Port Triggering (same as RPI)  https://wiki.rdkcentral.com/display/RDK/Port+Triggering+in+RPI
  24. TelcoVoice - Telco Voice Manager
  25. Firmware upgrade - Firmware Upgradation for BPI using Xconf Server
  26. USB Dongle(RNDIS/MODEM type) support to CellularManager - Cellular RNDIS Feature User Manual
  27. ACL (MAC Filering) support - MAC Filtering in BPI
  28. RDK Remote Debugger - RDK Remote debugger - Diagnostic Debug Data Collection Tool
  29. DHCP Manager - DHCP Manager Support for BPIR4
  30. MAP-T Support - MAPT in RDK-B BPI R4
  31. Barton Support - RDK-B IoT Barton

Roadmap of new Features

Q4' 2024(Previous prebeta release,Oct 2024)Q1' 2025 (current beta release,Feb 05 2025 )Q12025 official ReleaseQ2' 2025Q3' 2025Q4'2025Q1'2026Annual RDK8 ReleaseFuture
  • Board bringup
  • Core RDK-B Porting
  • Ethernet WAN support
  • LAN support
  • Basic Wi-Fi bringup
  • WebPA
  • TR369
  • Telemetry 2.0
  • RFC
  • Cellular WAN support
  • DHCP(IPv4,IPv6)
  • CPU Proc Analyzer
  • Local WebUI
  • Webconfig
  • Log upload/Log rotation
  • Firewall
  • Selfheal
  • TR-69
  • SNMP
  • Onewifi with single WiPhy support(First RDK-B device with this design)
    • 2.4 Ghz
    • 5 Ghz
    • 6 Ghz
  • Crashupload
  • Test and Diagnostics
  • Bridgemode
  • SD Card Support
  • DAC
    • Bundlegen support for BPI R4
    • meta-dac-sdk support for BPI R4
  • eSDK
  • PopulateSDK
  • Factory reset
  • Configurable WAN support
  • USP 8.0 migration
Same features of Beta Release
  • Speedtest
  • Port Triggering
  • WPS




  •  No Release due to GitHub migration
  • TelcoVoice
  • Firmware upgrade
  • EasyMesh Gateway
  • EasyMesh Extender
  • IEEE1905
  • Kernel Migration to 6.6
  • USB Dongle(RNDIS/MODEM type) support to CellularManager
  • WiFi 7
  • DAC support with meta-rdk-broadband-apps layer
  • ACL (MAC Filering) support in BPI build 
  • RFC manager integration
  • RDK Remote Debugger  Integration
  • Dhcp Manager Integration
  • Map-T Integration
  • IOT support (Barton) - Matter Over wifi,Matter over Thread,Bluetooth
  • DFS Testing in Non MLO Image
  • MLO support in Wi-Fi 7
Same Features of Q1'2026
  • WAN Over WiFI
  • RDK Generic Broadband Dev Image
  • wrynose
  • PPPoE
  • Edge AI support

References


Reference image 

  • Can be provided to RDK-B Licenses on demand

Test results reference

Testing of Easy Mesh build on BPI R4

EM Controller Side

Please ensure below processes are running in ctrl.

process_status 
root@Filogic-GW:~# systemctl status ieee1905_em_ctrl
● ieee1905_em_ctrl.service - ieee1905 EasyMesh Controller service
     Loaded: loaded (/lib/systemd/system/ieee1905_em_ctrl.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2022-04-28 17:43:33 UTC; 3 years 3 months ago
    Process: 4793 ExecStartPre=/bin/sh -c sleep 5 (code=exited, status=0/SUCCESS)
    Process: 4941 ExecStartPre=/bin/sh -c if [ ! -e "/sys/class/net/eth0_virt_peer/address" ]; then `/usr/ccsp/EasyMesh/setup_veth_for_em.sh brlan0 eth0 true`; fi (code=exited, status=0/SUCCESS)
    Process: 4942 ExecStart=/bin/sh -c /usr/bin/ieee1905 -f ieee1905::al_sap=trace,ieee1905::cmdu_handler=trace,ieee1905::cmdu_proxy=trace,ieee1905::cmdu_observer=trace -i eth0_virt_peer --sap-data-path /tmp/al_em_ctrl_data_socket --sap-control-path /tmp/al_em_ctrl_control_socket >> /tmp/ieee1905_ctrl_log.txt & (code=exited, status=0/SUCCESS)
   Main PID: 4943 (ieee1905)
      Tasks: 7 (limit: 4713)
     Memory: 22.3M
     CGroup: /system.slice/ieee1905_em_ctrl.service
             └─ 4943 /usr/bin/ieee1905 -f ieee1905::al_sap=trace,ieee1905::cmdu_handler=trace,ieee1905::cmdu_proxy=trace,ieee1905::cmdu_observer=trace -i eth0_virt_peer --sap-data-path /tmp/al_em_ctrl_data_socket --sap-control-path /tmp/al_em_ctrl_control_socket
 
Notice: journal has been rotated since unit was started, output may be incomplete.
 
 
root@Filogic-GW:~# systemctl status em_ctrl
● em_ctrl.service - EasyMesh Controller service
     Loaded: loaded (/lib/systemd/system/em_ctrl.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2025-08-07 05:54:27 UTC; 20min ago
    Process: 18033 ExecStartPre=/bin/sh -c /usr/ccsp/EasyMesh/setup_mysql_db_pre.sh (code=exited, status=0/SUCCESS)
    Process: 18038 ExecStart=/bin/sh -c /usr/bin/onewifi_em_ctrl bpi\@root >> /tmp/em_ctrl.log & (code=exited, status=0/SUCCESS)
    Process: 18040 ExecStartPost=/bin/sh -c /usr/ccsp/EasyMesh/setup_mysql_db_post.sh (code=exited, status=0/SUCCESS)
   Main PID: 18039 (onewifi_em_ctrl)
      Tasks: 15 (limit: 4713)
     Memory: 185.2M
     CGroup: /system.slice/em_ctrl.service
             └─ 18039 /usr/bin/onewifi_em_ctrl bpi@root
 
Notice: journal has been rotated since unit was started, output may be incomplete.
root@Filogic-GW:~#
 
root@Filogic-GW:~# systemctl status ieee1905_em_agent
● ieee1905_em_agent.service - ieee1905 EasyMesh Agent service
     Loaded: loaded (/lib/systemd/system/ieee1905_em_agent.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2025-08-07 05:54:31 UTC; 21min ago
    Process: 4944 ExecStartPre=/bin/sh -c if [ ! -e "/sys/class/net/eth1_virt_peer/address" ]; then `/usr/ccsp/EasyMesh/setup_veth_for_em.sh brlan0 eth1 false`;fi (code=exited, status=0/SUCCESS)
    Process: 4945 ExecStartPre=/bin/sh -c while [ ! -e /tmp/wifi_initialized ] && [ ! -e /tmp/wifi_dml_complete ] ;do sleep 1; done  (code=exited, status=0/SUCCESS)
    Process: 17690 ExecStartPre=/bin/sh -c sleep 5 (code=exited, status=0/SUCCESS)
    Process: 19496 ExecStart=/bin/sh -c /usr/bin/ieee1905 -f ieee1905::al_sap=trace,ieee1905::cmdu_handler=trace,ieee1905::cmdu_proxy=trace,ieee1905::cmdu_observer=trace -i eth1_virt_peer >> /tmp/ieee1905_agent_log.txt & (code=exited, status=0/SUCCESS)
   Main PID: 19497 (ieee1905)
      Tasks: 7 (limit: 4713)
     Memory: 18.8M
     CGroup: /system.slice/ieee1905_em_agent.service
             └─ 19497 /usr/bin/ieee1905 -f ieee1905::al_sap=trace,ieee1905::cmdu_handler=trace,ieee1905::cmdu_proxy=trace,ieee1905::cmdu_observer=trace -i eth1_virt_peer
 
Notice: journal has been rotated since unit was started, output may be incomplete.
 
root@Filogic-GW:~# systemctl status em_agent
● em_agent.service - EasyMesh Agent service
     Loaded: loaded (/lib/systemd/system/em_agent.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2025-08-07 06:15:40 UTC; 17s ago
    Process: 476399 ExecStartPre=/bin/sh -c /usr/ccsp/EasyMesh/setup_agent_pre.sh (code=exited, status=0/SUCCESS)
    Process: 476405 ExecStartPre=/bin/sh -c sleep 15 (code=exited, status=0/SUCCESS)
    Process: 482087 ExecStart=/bin/sh -c /usr/bin/onewifi_em_agent >> /tmp/em_agent.log & (code=exited, status=0/SUCCESS)
   Main PID: 482089 (onewifi_em_agen)
      Tasks: 8 (limit: 4713)
     Memory: 8.8M
     CGroup: /system.slice/em_agent.service
             └─ 482089 /usr/bin/onewifi_em_agent
 
2025 Aug 07 06:15:25 Filogic-GW systemd[1]: Starting EasyMesh Agent service...
2025 Aug 07 06:15:40 Filogic-GW systemd[1]: Started EasyMesh Agent service.


Observation in EM-Controller device side:  

  • All configured VAPs should be UP and Running
  • VAPs should be broadcasting EasyMesh default SSIDs(eg, private_ssid, mesh_backhaul)
  • Logs files are generated under /tmp folder

Extender 1 + STAR Topology

1.Please ensure below processes are running in Ext1

process_status 
root@Filogic-GW:~# systemctl status onewifi
* onewifi.service - Cosa service
     Loaded: loaded (8;;file://Filogic-GW/lib/systemd/system/onewifi.service/lib/systemd/system/onewifi.service8;;; enabled; vendor preset: e)
     Active: active (running) since Thu 2022-04-28 17:43:15 UTC; 3min 29s ago
TriggeredBy: * filogicwifiinitialized.path
    Process: 1781 ExecStartPre=/bin/sh /usr/ccsp/wifi/onewifi_pre_start.sh (code=exited, status=0/SUCCESS)
    Process: 2085 ExecStart=/usr/bin/OneWifi -subsys $Subsys (code=exited, status=0/SUCCESS)
   Main PID: 2086 (OneWifi)
      Tasks: 14 (limit: 4713)
     Memory: 38.2M
     CGroup: /system.slice/onewifi.service
             `- 2086 /usr/bin/OneWifi -subsys eRT.
 
2022 Apr 28 17:42:48 Filogic-GW systemd[1]: Starting Cosa service...
2022 Apr 28 17:42:53 Filogic-GW UTOPIA[2086]: system.syscfg Shared memory file not found
2022 Apr 28 17:42:53 Filogic-GW UTOPIA[2086]: 2022-04-28  17:42:53., ../../../../git/source/syscfg/lib/syscfg_lib.c:466, Error initializing sy
2022 Apr 28 17:43:15 Filogic-GW systemd[1]: Started Cosa service.
2022 Apr 28 17:44:01 Filogic-GW [OneWifi][2086]:   WiFi radio radio1 is set to UP

root@Filogic-GW:~# systemctl status ieee1905_em_agent
* ieee1905_em_agent.service - ieee1905 EasyMesh Remote Agent service
     Loaded: loaded (8;;file://Filogic-GW/lib/systemd/system/ieee1905_em_agent.service/lib/systemd/system/ieee1905_em_agent.service8;;; enabl)
     Active: active (running) since Thu 2022-04-28 17:43:35 UTC; 3min 16s ago
    Process: 3284 ExecStartPre=/bin/sh -c /usr/ccsp/EasyMesh/setup_ext_pre.sh (code=exited, status=0/SUCCESS)
    Process: 3303 ExecStartPre=/bin/sh -c if [ ! -e "/sys/class/net/eth1_virt_peer/address" ]; then `/usr/ccsp/EasyMesh/setup_veth_for_em.sh )
    Process: 3304 ExecStartPre=/bin/sh -c sleep 5 (code=exited, status=0/SUCCESS)
    Process: 3439 ExecStart=/bin/sh -c /usr/bin/ieee1905 -f ieee1905::al_sap=trace,ieee1905::cmdu_handler=trace,ieee1905::cmdu_proxy=trace,ie)
   Main PID: 3440 (ieee1905)
      Tasks: 7 (limit: 4713)
     Memory: 10.5M
     CGroup: /system.slice/ieee1905_em_agent.service
             `- 3440 /usr/bin/ieee1905 -f ieee1905::al_sap=trace,ieee1905::cmdu_handler=trace,ieee1905::cmdu_proxy=trace,ieee1905::cmdu_obserr
 
2022 Apr 28 17:43:30 Filogic-GW systemd[1]: Starting ieee1905 EasyMesh Remote Agent service...
2022 Apr 28 17:43:35 Filogic-GW systemd[1]: Started ieee1905 EasyMesh Remote Agent service.
 
root@Filogic-GW:~# systemctl status em_agent        
* em_agent.service - EasyMesh Agent service
     Loaded: loaded (8;;file://Filogic-GW/lib/systemd/system/em_agent.service/lib/systemd/system/em_agent.service8;;; enabled; vendor preset:)
     Active: active (running) since Thu 2022-04-28 17:44:00 UTC; 2min 57s ago
    Process: 3283 ExecStartPre=/bin/sh -c sleep 30 (code=exited, status=0/SUCCESS)
    Process: 3621 ExecStartPre=/bin/sh -c /usr/ccsp/EasyMesh/setup_ext_pre.sh (code=exited, status=0/SUCCESS)
    Process: 3640 ExecStart=/bin/sh -c /usr/bin/onewifi_em_agent >> /tmp/em_agent.log & (code=exited, status=0/SUCCESS)
   Main PID: 3641 (onewifi_em_agen)
      Tasks: 9 (limit: 4713)
     Memory: 10.8M
     CGroup: /system.slice/em_agent.service
             `- 3641 /usr/bin/onewifi_em_agent

2.Ensure mesh backhaul connectivity is established over 5G through wifi1.1 interface.

iw dev wifi1.3 info

3.Verify mesh backhaul connection in EM-Contrller side as well.

iw dev wifi1.1.sta<i> info
iw dev wifi1.1.sta<i> station dump ## This command gives information on connected client ie Extender1.

4. Wait for few minutes( for Agent to propagate SSID information from Controller to OneWifi in Extender1) and then check

  • Check all configured VAPs should be up and running with "iw dev" command
  • VAPs should be broadcasting default EasyMesh SSIDS (ie private_ssid, mesh_backhaul)
  • logs files are generated under /tmp folder

5. Test the connectivity to EM-Controller through backhaul

ping 10.0.0.1 -c 5

Test the connectivity with wireless clients.

Extender2 (For Daisy-Chain )

1. Ensure Extender 1 is running properly with configured vap's of FH and BH.

2. Make atleast 7 feet distance from Ext1 to Ext2 

3. Ensure  ieee1905_em_agent,onewifi_em_agent processes are running in Ext2

4. Ensure mesh backhaul connectivity is established over 5G through wifi1.1 interface.

iw dev wifi1.3 info

5. Verify mesh backhaul connection in Extender1 side as well.

iw dev wifi1.1.sta<i> info
iw dev wifi1.1.sta<i> station dump ## This command gives information on connected client ie Extender2.

6. Wait for few minutes( for Agent to propagate SSID information from Controller to OneWifi in Extender2) and then check

  • Check all configured VAPs should be up and running with "iw dev" command
  • VAPs should be broadcasting default EasyMesh SSIDS (ie private_ssid, mesh_backhaul)

7. Test the connectivity to EM-Controller through backhaul

ping 10.0.0.1 -c 5

Test the connectivity with wireless clients.

RDKB-CLI Testing

  1. Ensure below service is running in your controller image
EM_CLI Service 
root@Filogic-GW:~# systemctl status em_cli
● em_cli.service - EasyMesh RDKB CLI service
     Loaded: loaded (/lib/systemd/system/em_cli.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2025-12-19 07:50:51 UTC; 2h 42min ago
    Process: 13248 ExecStart=/bin/sh -c /usr/bin/onewifi_em_cli >> /tmp/em_cli.log & (code=exited, status=0/SUCCESS)
   Main PID: 13249 (onewifi_em_cli)
      Tasks: 7 (limit: 4708)
     Memory: 28.1M
     CGroup: /system.slice/em_cli.service
             └─ 13249 /usr/bin/onewifi_em_cli

2025 Dec 19 07:50:54 Filogic-GW sh[13249]: 2025/12/19 07:50:54 Loaded 14 clients
2025 Dec 19 07:50:54 Filogic-GW sh[13249]: 2025/12/19 07:50:54 Loaded system configuration
2025 Dec 19 07:50:54 Filogic-GW sh[13249]: 2025/12/19 07:50:54 Initialized wireless settings with 2 profiles
2025 Dec 19 07:50:54 Filogic-GW sh[13249]: 2025/12/19 07:50:54 Coverage map initialized
2025 Dec 19 07:50:54 Filogic-GW sh[13249]: 2025/12/19 07:50:54 Connecting with controller IP 192.168.2.221 and port: 49153
2025 Dec 19 07:50:55 Filogic-GW sh[13249]: 2025/12/19 07:50:55 WebSocket client connected. Total: 1
2025 Dec 19 07:50:56 Filogic-GW sh[13249]: 2025/12/19 07:50:56 Performing coverage analysis for band 2.4ghz with threshold -70 dBm
2025 Dec 19 07:50:56 Filogic-GW sh[13249]: 2025/12/19 07:50:56 Coverage analysis completed: 100.0% total coverage
2025 Dec 19 07:51:36 Filogic-GW sh[13249]: 2025/12/19 07:51:36 WebSocket client disconnected. Total: 0
2025 Dec 19 07:51:36 Filogic-GW sh[13249]: 2025/12/19 07:51:36 WebSocket client connected. Total: 1
root@Filogic-GW:~#


2. Launch the browser and enter the URL as http://<IP>:<Port> .IP should be the erouter0 IP of device on which rdkb-cli is running, for example:http://192.168.2.221:8888/

3.Please refer the rdkb cli page below.

4.User can configure the controller Ip(i,e erouter0) and port by clicking user-avatar icon as highlighted in below image.

5.On clicking on user avatar icon, popup will come to configure IP and port for controller to connect. Please enter the controller IP(i,erouter0) and port no and click on save.

6.Network Topology
To get the current network topology, click on Network Topology tab as shown below.
Note: The topology is being fetch from controller and redraw on every 60 sec if user stay on topology page or page reload.

7. Update SSID and Password
User can update SSID and Password as steps shown below.
Click on tab Wireless Settings, The wireless network profile will be fetch as shown on the GUI as shown in picture below.

8. User can click on the Edit button on the profile which ssid and passphase needed to be updated. On click on Edit button the pop up will come with existing ssid and passphase, which can be edited and save. 

user can edit multiple network profile and apply the updated setting by clicking “Apply Profile Setting” on top of the same page. Please refer the images below.

9. Channel Update
User can update Radio channel as steps shown below:

Click on tab Wireless Settings, Radio Configuration will be fetch as shown on below picture

Toggle the bands and user can select the channel from dropdown list and click on Apply Radio Settings button

10. Wifi Reset
User can reset the controller as steps show below.
Click on tab “System Setting” for wifi reset page and select the AL MAC from the drop down list.

user can also select haultypes if any ssid and password has to be updated with reset.
On click Reset wifi, it will ask for the user configuration to apply reset.

On click on “OK”, the reset will apply.

Please do manual reboot of all connected devices once we performed the Reset operation in RDKB CLI to configure the default configurations .

Known Issue on Easy Mesh builds: 

  • Randomly, observing cli crash when user try to change the channel value in GUI. To recover need to do WiFi Reset. (refer step 10)
  • Channel number change, WiFi reset and network topology not working from CLI.

For support

References

Known issues

#

Component

JIRA / Reference

Details

1

eSDK is not working

RDKBACCL-1102

eSDK FAIL in 2026 Q1 release. PopulateSDK is PASS. Under investigation.

2

WebUi page is not loaded in bridge mode

RDKBACCL-512

Issue is there from Q4 2024

3

SNMP get/set is not working

RDKBACCL-1468

Issue observed with MLO enabled builds

Known issues in Non MLO build

#SummaryJIRA/ReferenceDetails
1

Observing build issues when we disable generic_mlo distro in BPI RDKB builds

RDKBACCL-1651 - Getting issue details... STATUS

Observing build issues when we disable generic_mlo distro in BPI RDKB builds
Fix : https://github.com/rdkcentral/meta-cmf-bananapi/pull/460


  • No labels

1 Comment

  1. Yaniv Yizhak

    Jun 09, 2026

    Hi,

    How RDK8 annual release is different than the old quarterly RDKB releases?

    What's the purpose of RDK8? Is it the same architecture as RDK-B?

    Going forward, both releases will be available? yearly and quarterly?
    Is there any diff in the feature list or content?

    Thanks,

    Yaniv

DISCLAIMER: Please note that the use of the RDK Wiki is subject to its Privacy Policy & Terms of Use. In addition, this Wiki may be accessed by all RDK licensees and their contractors.