...
On loss of internet access for any length of period, the node will continue to work on the LAN side. The node keeps the network in the same state which means any possible leaf connections are kept.
On a single or multiple reboots of a node with no internet access, the node configures itself using a stored subset of teh OVSDB config (provisoned by the SDN controller when the node was still connected). This config provides a limited set of functionalities. It sets up the default home LAN, so that the node continues to work on the LAN side:
Further use of the previously active bridge/router configuration
Home SSID & primary PSK (only a single zone and no other zones)
Existing static DHCP reservations and user-configured subnet
User-configured primary/secondary DNS servers
Features that are not supported (including but not limited to):
Port forwarding entries
IPv6 LAN support
Multi-PSK passwords
Onboarding or backhaul SSID bring-up
OpenFlow rules besides the default
FSM configuration
Steering configuration
...
Info |
---|
OpenSync 2.4 only supports cloudless router operation for WiFi clients |
...
. Support for Ethernet |
...
clients has been introduced with OpenSync 3.2. |
Implementation Details
When the gw_offline feature flag is enabled and when a GW node is normally connected to the controller, the node monitors a subset of the OpenSync OVSDB, and actively stores it to persistent storage if the node detects changes in the subset of the monitored config. The OpenSync 2.0 osp_ps persistent storage API is used. For optimization and saving of flash cycles, the actual saving to persistent storage is done only if the new config differs from the saved config. The config is saved in JSON format.
...