...
Port forwarding entries
IPv6 LAN support
Multi-PSK passwords
Onboarding or backhaul SSID bring-up
OpenFlow rules besides the default
FSM configuration
Steering configuration
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
OpenSync 2.4 only supports cloudless router operation for WiFi clients. Support for Ethernet clients has been introduced with OpenSync 3.2. |
...
Enabling/disabling the feaure
Enabling/disabling the monitoring of OVSDB config
OVSDB interface for CM ↔ PM communication. OVSDB uses a flag for CM to trigger the gw_offline mode in PM, and a flag for PM to report:
The feature status (on/off)
Whether CM has the config available or if the config has actively been applied.
Node_Config Table
Node_Config::module/key | Values | Set by | Description |
|---|---|---|---|
Node_Config::PM/gw_offline_cfg | [false/true] (persistent) | Controller | The gw_offline on/off flag. To actually make this value persistent (done by PM), the cloud should set the persist value to true. |
Node_Config::PM/gw_offline_mon | [false/true] | Controller | Enables reading and monitoring of a subset of the OVSDB config. Also stores the config to persistent storage. It is recommended to set the values after SSID/PSK/LAN/etc. have been configured, but that's not a requirement. It can be set anytime after the gw_offline_cfg has been set to true. |
Node_Config::PM/gw_offline | [false/true] | CM | Trigger applying the stored subset of the OVSDB config (valid if Node_Config::PM/gw_offline_cfg==true && Node_State::PM/gw_offline_status==ready). |
Node_State
Node_State::module/key | Values | Set by | Description |
|---|---|---|---|
Node_State::PM/gw_offline_cfg | [false/true] | PM | Acknowledge enablement of the feature by PM. |
Node_State::PM/gw_offline_status | [disabled/enabled/ready/active/error] | PM | Provides the status of the feature, such as it is disabled, enabled but no config in storage, ready means enabled and has config in storage, and active means it has actively applied it's config. error means it failed to load&&apply stored config or failed to read&&store config or other errors. PM will indicate "ready" in Node_State::PM/gw_offline_status when the feature is enabled (Node_Config::PM_gw_offline_cfg==true -- persistent) and it has stored config available. PM will indicate "active" in Node_State::PM/gw_offline_status when the feature is enabled (Node_Config::PM_gw_offline_cfg==true -- persistent) and CM has triggered config apply by setting Node_Config::PM_gw_offline:=true and PM has successfuly applied it's config. |
...
Supported Config Parameters to be Saved and Restored
Description | Type | OVSDB Tables | Details |
|---|---|---|---|
WiFi Radios | Replay | Wifi_Radio_Config | Wifi_Radio_Config can be replayed. Device logic needs to restore the references between tables: For VIFs configured in Wifi_VIF_Config, uuid references need to be restored/added in Wifi_Radio_Config. If DFS channels were configured, they might require some additional device logic as they might not be always available. However by default driver will handle DFS automatically in the usual way, i.e., do CAC, run away to another channel, stop operation if it runs out of channels etc. |
Home SSID | Replay | Wifi_VIF_Config | HomePass example: Wifi_VIF_Config where bridge==LAN_BRIDGE is restored (replay). Device logic: Configured home-ap VIF interfaces need to be added to LAN_BRIDGE (ovs-vsctl). |
WPA Mode | Replay | The WPA mode is a setting in the Wifi_VIF_Config table. The device must ensure that the same WPA mode is used when re-creating the SSID. | |
DFS Mode | Not Applicable | ||
Network Mode: Bridge, Router, Auto | Replay | Wifi_Inet_Config | There's no corresponding setting on the device. Re-applying network setting will generally realize the last network mode. |
IP Reservation | Replay | DHCP_reserved_IP | This is a trivial replay of the DHCP_reserved_IP table. |
LAN Subnet | Replay | Wifi_Inet_Config where if_name==br-home | A replay of the Wifi_Inet_Config entry for br-home. |
...