Page History

...

• 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 2.0 USB portKirkstone 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

...

• 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 WebUI
• All Wi-Fi testcase should be working with Netgear Wi-Fi dongle in Kirkstone

Risks

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

...