Added to OpensyncAPConfig
Added Profiles for Static.
Added handler in OvsdbClient to process.
Currently not applying the values, uses the defaults still, but
remaining functionality will come in subsequent updates.
Adding set of dtim_period on AP in Wifi_VIF_Config if value exists > 0.
Need to obtain value from RadioConfig or SSID config, looking at cloud
model to see if value exists already for DTIM_PERIOD ( i.e. what nth
becaons have TIM )
WIFI-829: Cloud BE: support configuration of RTS/CTS threshold
WIFI-830: Cloud BE: support configuration of fragmentation threshold
Set frag_threshold on AP in Wifi_VIF_Config table per ssid based on
Cloud equipment configuration advance radio map value for fragThresholdBytes
Averaging of values in Channel report to align with ApNode report, based
on Survey data, and converting to percentage used, based on duration.
This may change going forward as Ap could end up sending average
based data.
Extract Bonjour Profile from OpensyncApConfig if present when
configuring ssids on Ap
Profile is only logged during SSID configuration if it is present as
waiting on AP support for Bonjour Gateway and services.
Add Bonjour Profile support to OpensyncApConfig
Add static files for static and static-docker versions.
Refactor of OpensyncExternalIntegrationCloud. Separate concerns, move
MQTT message processing and stats events to new class.
JUnit tests updated based on refactor
Add schema check for "captive_portal" and "captive_allowlist" in
Wifi_VIF_Config table, if present, set values from CaptivePortal profile
if they are present. To facilitate designer testing. When the schema
actually contains these in a formal Ap load, remove the check.
Handle the start and stop of the debug engine REST commands coming
via gateway controller.
Change gateway controller to use new method to handle redirector change.
NB. Ap commands being sent via the command config in OvsdbDao are not
finalized and will change.
Should have noise floor sent as a signed value, is currently coming as an uint32
I believe the AP actually translates the signed value to that.
ON channel reports more than just the channel in use on the radio which is making a mess as well, I have added a filter on the OSGW as a workaround which will prevent OFF channel values being used during calculation of channel info for on channel reporting. This may become unnecessary when the AP fix comes in but for now might clear things up a bit. After we change to a signed value, combined with correct channel survey reporting, we should have a better value.
