RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
...
Limitation: Image download process was verified through tftp server,Yet to have http support
...
No
...
Feature
...
Supported
...
Opensync covers layers from just above the drivers within a device, to the connection to the cloud within that device. It is responsible for translating Cloud management commands to the hardware driver calls and reports to the Cloud state and telemetry in a mesh multi-AP Wi-Fi network
1) Openvswitch - Provides OVSDB for opensync communication
2) OpenSync - Provides Various managers (DM,CM,WM,NM,etc..)
3) MeshAgent - Ensures the sync between RDKB and Plume
4) rdkb-turris-hal - Contains the hardware level code to reterive AP and stats information, using Netlink, hostapd_cli and iw
Opensvswitch → Version has been upgraded from 2.6.0 to 2.13.0 (dunfell branch)
OpenSync → Version 1.4.0.1 (master branch)
MeshAgent → CMF git (dunfell branch)
rdkb-turris-hal → rdkcentral GitHub (dunell branch)
Opensync has to be manually triggered , and respective certificate has to be copied into the image (/nvram/certs)
Execute the below script , for linking the back-haul interfaces
...
title | Back haul and DNS script |
---|
...
root
@TurrisOmnia
-GW:# sh start_hostapd.sh
#!/bin/bash
killall dnsmasq
dnsmasq -u root -a
10.0
.
0.1
-i brlan0 -F
10.0
.
0.2
,
10.0
.
0.20
--dhcp-option=
3
,
10.0
.
0.1
--dhcp-option=
6
,
10.0
.
0.1
\
-a
169.254
.
2.1
-i wifi2 -F
169.254
.
2.2
,
169.254
.
2.10
\
-a
169.254
.
3.1
-i wifi3 -F
169.254
.
3.2
,
169.254
.
3.10
\
-C /dev/
null
-z --except-
interface
=lo -l /nvram/dnsmasq.leases --dhcp-script=/nvram/scripts/restart_mesh.sh \
--log-facility=/tmp/dnsmasq.log --log-dhcp
#touch /tmp/hostapd-acl0
#touch /tmp/hostapd-acl1
touch /tmp/hostapd-acl2
touch /tmp/hostapd-acl3
#hostapd_cli -i global raw ADD bss_config=wlan0:/nvram/hostapd0.conf
#hostapd_cli -i global raw ADD bss_config=wlan1:/nvram/hostapd1.conf
hostapd_cli -i global raw ADD bss_config=wlan2:/nvram/hostapd2.conf
hostapd_cli -i global raw ADD bss_config=wlan3:/nvram/hostapd3.conf
Execute the below script for running the opensync Managers
Expand | ||
---|---|---|
| ||
|
Note: Cert files are provided by Opensync for Licencees
Opensync mangers and NOC status can verified by querying OVSDB table
root@TurrisOmnia-GW:# /usr/plume/tools/ovsh s Manager
...
title | Expand Output |
---|
...
Opensync covers layers from just above the drivers within a device, to the connection to the cloud within that device. It is responsible for translating Cloud management commands to the hardware driver calls and reports to the Cloud state and telemetry in a mesh multi-AP Wi-Fi network
1) Openvswitch - Provides OVSDB for opensync communication
2) OpenSync - Provides Various managers (DM,CM,WM,NM,etc..)
3) MeshAgent - Ensures the sync between RDKB and Plume
4) rdkb-turris-hal - Contains the hardware level code to reterive AP and stats information, using Netlink, hostapd_cli and iw
Opensvswitch → Version has been upgraded from 2.6.0 to 2.13.0 (dunfell branch)
OpenSync → Version 1.4.0.1 (master branch)
MeshAgent → CMF git (dunfell branch)
rdkb-turris-hal → rdkcentral GitHub (dunell branch)
Opensync has to be manually triggered , and respective certificate has to be copied into the image (/nvram/certs)
Execute the below script , for linking the back-haul interfaces
Expand | ||
---|---|---|
| ||
|
Execute the below script for running the opensync Managers
Expand | ||
---|---|---|
| ||
|
Note: Cert files are provided by Opensync for Licencees
Opensync mangers and NOC status can verified by querying OVSDB table
root@TurrisOmnia-GW:# /usr/plume/tools/ovsh s Manager
Expand | ||
---|---|---|
| ||
|
1) Log on to plume NOC, with the following URL https://piranha-osacademy.dev.us-west-2.aws.plume.tech/noc/login
UserName and Password are provided for Opensync Licencees
2) We should be able to view Plume NOC with Connected device graph (If Device is connected)
SSID name change sync between Plume NOC and RDKB WEBUI is not supported.
No | Feature | Supported |
---|---|---|
1 | LAN Connected Devices-Ethernet | |
2 | WAN Connected Devices-Wi-Fi | |
3 | Parental Control | |
4 | Firewall settings | |
5 | Advanced Config: Port Triggering | |
6 | Advanced Config: Port Forwarding | |
7 | Advanced Config: Remote Management | |
8 | Advanced Config: DMZ | |
9 | Xfinity Wi-Fi 2.4/5 GHz – Public Hotspot | |
10 | Test and Diagnostics | |
11 | Local WebUI Configuration | |
12 | Factory Reset | |
13 | DHCP /Reserved IP | |
14 | EthWan | |
15 | Eth Agent | |
16 | 2.4 GHz Band Support | |
17 | 5 GHz Band Support | |
18 | Bridge Mode Support | |
19 | Persistent Storage Management | |
20 | WebPA for Comcast,community | |
21 | Lost and Found | |
22 | Bluetooth | |
22 | Harvester Support | |
23 | TR-69 | |
24 | SNMP | |
27 | Boot time data measurement | |
28 | Wireless Protection Setup(WPS) | |
29 | Captive Portal | |
30 | Wi-Fi MAC Filtering | |
31 | Log Rotation Support | |
32 | Firmware Upgrade Support | |
33 | Multiboot Support | |
34 | Telemetry Support | |
35 | IPV6 |
1) Log on to plume NOC, with the following URL https://piranha-osacademy.dev.us-west-2.aws.plume.tech/noc/login
UserName and Password are provided for Opensync Licencees
2) We should be able to view Plume NOC with Connected device graph (If Device is connected)
...
Turris Omnia Reference Platform: Flashing Instruction
...