| Table of Contents | ||||
|---|---|---|---|---|
|
Minimum hardware specification
...
| Info |
|---|
The expected memory footprint does not include third-party services and plugins. To include these in your memory consumption estimations, please contact info@opensync.io. |
Hardware | Minimal requirement |
|---|---|
Flash | OpenSync: 5 MB |
RAM | OpenSync: 75 MBytes |
CPU | Single core: 750 MHz |
Temporary file system
OpenSync requires a minimum of 16 MB storage for the tmpfs (temporary file system).
...
There should be a minimum of 7 MB persist storage for features like reboot reasons, WAN configuration. For details refer to Requirements | Persistent Storage
Dependent libraries
OpenSync is optimized for Linux operating systems with kernel version 3.3 or higher. In addition, OpenSync requires minimal the following libraries:
Purpose | Library | Recommended Version |
|---|---|---|
toolchain | [libc.so.0] |
|
system | [libssl.so.1.0.0] | openssl-1.0.2k |
applications | [libjansson.so.4 | jansson-2.7 |
openvswitch | [libncurses] | ncurses-6.1 |
Device identification parameters
...
Device identification parameters (stored in AWLAN_Node table):
ID - must be unique per node
model name - Defines the node model
Case sensitive
Should not have leading or trailing spaces
Must be unique in the world
Match regex pattern:
^[A-Za-z0-9_-]*
firmware version - details below
...
Example: 1.2.4-8-ga46f46c-dev
Component | Mandatory / Optional | Value type |
Major | Mandatory | Integer |
Minor | Mandatory | Integer |
Revision | Optional | Integer |
Patch | Optional | Integer |
Build number | Optional | Integer |
Git hash | Optional | String |
Firmware profile (development or production) | Optional | String |
Secure cloud connection
One of the top OpenSync priorities is ensuring the highest level of data privacy by enforcing state-of-the-art security standards, such as client authentication and data encryption for all the nodes that connect to the OpenSync SDN contoller. These security mechanisms require node certificates and encryption keys. Connection is secure by using TLS 1.2 and two way SSL mutual authentication.
...
| Info |
|---|
Details on upgrade implementation are defined at integration time with each partner individually. |
Switching from native Linux to Open vSwitch (OVS)
OpenSync services take full advantage of the OVS networking features. The integrators should switch from native networking (such as native Linux bridge implementation) to the OVS networking (OVS bridges).
WAN information
OpenSync needs to be aware of WAN configuration and state.
LAN information
...
. |
Watchdog
OpenSync runs as embedded software and therefore requires a mechanism that detects potential malfunctions and automatically initiates the recovery procedure. One such mechanism is the Watchdog.
...
There should be 8 VAP per radio available (1 STA + 7 AP’s) for OpenSync to use simultaneously. SDN controller will orchestrate them per customer needs in runtime.
Additional Requirements
Feature Group | Feature | Requirements Document | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
Configuration and Statistics | OVS, OVSDB |
| ||||||||
Basic Telemetry |
| |||||||||
Persistent Storage |
| |||||||||
Gateway Integration | Active or Passive mode |
| ||||||||
External DB Integration |
| |||||||||
Network Protocols | IPv4, IPv6 |
| ||||||||
IPTV | IPTV Traffic Separation |
| ||||||||
WiFi Modes | 11ax (WiFi 6) |
| ||||||||
WiFi6E |
| |||||||||
WiFi Mesh | Topology Management |
| ||||||||
GRE Backhaul |
| |||||||||
Multi-AP Backhaul (4addr) |
| |||||||||
WiFi Features | Multi-psk |
| ||||||||
Dynamic Frequency Selection (DFS) |
| |||||||||
Zero-wait DFS |
| |||||||||
DPP |
| |||||||||
HaaHs Public WiFi |
| |||||||||
Band and Client SteeringAlso refer to FAQ | Band and Client Steering | Basic/Legacy, 11k/11v Steering |
| ||||||||
Advanced Features |
| |||||||||
WPS Support | WPS from App |
| ||||||||
Third Party Services | FSM Plugins |
| ||||||||
Small Business | Captive Portal |
| ||||||||
Rate Limiting |
|