You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

OpenSync activities with RDKB

OpenSync supported platforms

List of supported platforms that has already added OpenSync package in default builds,

Device nameCurrent OpenSync versionPlanned OS releaseBuild instructions
Turris Omnia Residential GWOpenSync 2.0.5OpenSync 3.2.6Turris Omnia RDK-B Gateway - Yocto 3.1(Dunfell)
Turris Omnia ExtenderOpenSync 2.0.5OpenSync 3.2.6 RDKB Extender Yocto 3.1 - Dunfell
Raspberrypi 4 extenderOpenSync 2.0.5OpenSync 3.2.6RPI 4B Model Reference Platform: Extender build instructions

OpenSync cloud Requirements

To establish connection with Plume cloud server using the OpenSync, follow the cloud Access Guide

WiFi Extender with Turris Omnia Reference Platform - Cloud Access Guide

OpenSync connection establishment with cloud

OpenSync Backhaul Support

The OpenSync Backhaul Support will enable extender connectivity requires two wireless interfaces as well as bridge and subnet

Wifi dongles connected to device(Raspberry pi 4 example) 

  • Netgear wifi dongle1 (2GHz)
  • Netgear wifi dongle2 (5GHz)


OpenSync service should be up and running. List of OpenSync process running,

root@raspberrypi4-rdk-extender:~# ps -Af | grep "open"
root       296     1  1 03:54 ?        00:00:03 /usr/sbin/ovsdb-server --remote=punix:/var/run/openvswitch/db.sock --remote=db:Open_vSwitch,Opb
root       299     1  0 03:54 ?        00:00:02 /usr/sbin/ovs-vswitchd --pidfile=/var/run/openvswitch/ovs-vswitchd.pid
root       372     1  0 03:54 ?        00:00:00 /usr/opensync/bin/pl2rld
root       375     1  0 03:54 ?        00:00:00 /usr/opensync/bin/dm
root       377   375  0 03:54 ?        00:00:00 /usr/opensync/bin/dm
root       384   377  0 03:54 ?        00:00:00 /usr/opensync/bin/om
root       385   377  0 03:54 ?        00:00:00 /usr/opensync/bin/nm
root       386   377  0 03:54 ?        00:00:00 /usr/opensync/bin/qm
root       387   377  0 03:54 ?        00:00:00 /usr/opensync/bin/xm
root       392   377  0 03:54 ?        00:00:01 /usr/opensync/bin/cm
root       394   377  0 03:54 ?        00:00:00 /usr/opensync/bin/wm
root       398   377  0 03:54 ?        00:00:00 /usr/opensync/bin/sm
root       400   377  0 03:54 ?        00:00:00 /usr/opensync/bin/lm
root       831   385  0 03:54 ?        00:00:00 /sbin/udhcpc -i br-wan -f -p /var/run/udhcpc-br-wan.pid -s /usr/opensync/bin/udhcpc.sh -t 60 -X
root      1272   308  0 03:59 ttyS0    00:00:00 grep open


OpenSync Manager should be active

root@raspberrypi4-rdk-extender:/usr/opensync/tools# ./ovsh s Manager
-----------------------------------------------------------------------------
_uuid            | 5fc9~61e8                                                |
_version         | ef39~9332                                                |
connection_mode  | ["set",[]]                                               |
external_ids     | ["map",[]]                                               |
inactivity_probe | 30000                                                    |
is_connected     | true                                                     |
max_backoff      | ["set",[]]                                               |
other_config     | ["map",[]]                                               |
status           | ["map",[["sec_since_connect","137"],["state","ACTIVE"]]] |
target           | ssl:34.208.159.154:443                                   |
-----------------------------------------------------------------------------

Current plans

  • Stabilising OpenSync_3.2.6 version is being performed by the Plume Team


For more information on OpenSync, visit https://www.opensync.io

  • No labels