Versions Compared

Key

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

...

draw.io Diagram
bordertrue
diagramNameOpenSync_Architecture
simpleViewerfalse
widthlinksauto
tbstyletop
lboxtrue
diagramWidth1081
revision2

...

draw.io Diagram
width
bordertrue
diagramNameSystem Architecture
simpleViewerfalse
linksauto
tbstyletop
lboxtrue
diagramWidth501
revision3

...

VAP IndexNameComment
1private_ssid_2g2g user private ssid 
2private_ssid_5g5g user private ssid
12mesh_backhaul_2gMesh backhaul on 2g
13mesh_backhaul_5gMesh backhaul on 5g
14mesh_sta_2gMesh station on 2g
15mesh_sta_5gMesh station on 5g

Identified task list

...

Target Build Variant 

  •  RPI4 Kirkstone build with  kernel 5.15 

Identified task list

  • Need to learn how OpenSync work with OneWiFi - Communication is through DM/RBUS, not wifi hal. May need to refer Comcast device.

  • Need to compile OpenSync for OneWifi (some kconfig should be enabled)

  • Need to know how to start OpenSync through OneWiFi

  • Need to know OVSDB tables of OpenSync collaborate with OVSDB tables of OneWiFi(wifi.db)

  • Bringup OVSDB manager for synchronization

  • Wi-Fi interface alignment with Netgear wifi dongle and  Make sure existing wifi functionality won't be disturbed.

  • Netgear driver support with Kirkstone version

  • Conversion of Linux bridge into OVS bridge(brlan0) - OVSAgent is now part of rootfs but not operational

  • Update dnsmasq configuration for OpenSync backhaul AP feature (wifi2, wifi3)

  • Enable IP_GRE as kernel module

  • Home AP bringup in RPI GW

  • Backhaul AP bringup in RPI GW

  • Make sure that GRE tunnel is created for backhaul communication and it is stable (Need to be tested with Extender)

  • Need to make sure that onewifi existing functionality is not breaking

...

  • Dongle's minimal support for 2AP and 1 STA.

  • If Netgear dongle is not providing such support, need to find new WiFi dongle.

  • Device provisioning in Plume Inventory (require Plume's support)

  • ovsdb manager/OVSM acts as medium between onewifi webconfig subdoc  and plume controller
  • OpenSync have run-time dependencies with ovsdb-server & openvswitch(ovsdb-server start up is part of ovsagent . currently, this server is not running in rpi).

Considerations

...

  • if we go with dunfell, we may need to put extra effort for kirkstone based build

  • dunfell may be supported for next few releases.

  • if we want to go with dunfell based build, its better to start with 64bit build

Validation

  • Check opensync service / OpenSync process will be run by meshagent DM parameter

  • Check opensync managers

  • Check Manager table for Online status

  • Associate RPI4 extender with RPI4 gateway

  • check ovsdb and wifi db table updation if any action taken in plume NOC / RDK WebUICheck synchronization of both OpenSync DB and RDKB Wifi DB tables during updates through Plume NOC / RDKB WebUI/ DMCLI
  • All Wi-Fi testcase should be working with Netgear Wi-Fi dongle in Kirkstone
  • Validation of Mesh will be done with SuperPOD as extender

Risks

  • Availability of OVSM for RDK Community is mandatory
  • Wireless interface names for Wifi dongle needs to be aligned for OpenSync convention

Flow Diagram/Pseudo Code


draw.io Diagram
bordertrue
diagramNameflow
simpleViewerfalse
width
linksauto
tbstyletop
lboxtrue
diagramWidth781
revision4

Sequence Diagrams


draw.io Diagram
bordertrue
diagramNameSequence diagram
simpleViewerfalse
linksauto
tbstyletop
lboxtrue
diagramWidth1192
revision4

Build Instructions

TargetYocto versionBuild instruction
RPI4 32bitDunfell RPI 4B Model Reference Platform
RPI4 32bitKirkstonekirkstone RDK-B RPI4 32 bit
RPI4 64bitDunfellRPI 4B Model Reference Platform with 64bit Arch
RPI4 64bitKirkstoneKirkstone RDK-B RPI4 64 bit (Both User Space & Kernel Space)

...