Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Table of Contents

Scope

Goal of this document helps RDK-B community to Port Unified-easy-mesh on to their Gateway/Extender platforms

Assumption

Test EM on Raspbian OS

Use cases

...

R5 Specification

...

R6 specification with Wi-Fi 7

Use case diagram

...

Generic Porting stages

  • Yocto support
  • New cli migration
  • Golang support
  • Segmentation faults fixing

Current state

Done

...

<<OneWifiMeshCli>>: reset erouter0 bananapi encode_config_reset:354: {

...

(gdb) bt #0  0x0000000000417fb8 in em_cmd_t::init (this=this@entry=0x7f8b4b7010, dm=dm@entry=0x7f8b7fe690)     at ../../../git/src/ctrl/../../src/cmd/em_cmd.cpp:127 #1  0x0000000000418764 in em_cmd_t::em_cmd_t (this=0x7f8b4b7010, type=em_cmd_type_reset,     param=<error reading variable: Cannot access memory at address 0x7ffc9a6470>, dm=...)     at ../../../git/src/ctrl/../../src/cmd/em_cmd.cpp:703 Backtrace stopped: Cannot access memory at address 0x7ffc9a63f8

...

Ongoing

  • Golang support in RDK-B added
  • ongoing with latest cli in progress
    • Creating yocto recipe to compile cli go code from yocto
    • Will retest the crashes and update 

Next phase

  • Optimizing mariaDB - Target to keep size < 10 MB
  • Package Manager
  • Stripped onewifi for AP extender

...

  • EasyMesh controller integration - On Going
  • Test with BPI R4 controller & RPI4 Agent - TBD
  • Test with with BPI R4 controller & BPI R4 agent - TBD

Extender specific steps

  • OSS image with SoC specific changes done
  • Integration of OneWifi on going
  • EasyMesh Agent - To start after Onewifi integration
  • Testing with RPI4 controller and BPI R4 Extender

Platform agnostic c++ coding

State machine(WIP)

...

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 )

...

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.


Sample logs

EM-Controller and EM-Agent success logs

...