We have recently deployed about 150 Hap AC2 (RBD52G-5HacD2HnD)
and we have several customers complaining about SSID that basically disappear.
and then come back. While the SSID’s disappear WIFI Stops and 0 traffic gets passed. I have turned on WIFI Debug and have not seen anything being logged.
Could it be that 5GHz is scanning for radars? That takes a few minutes and the SSID disappears. This will be indicated in the interface list, while it happens.
Which we just did in a few devices to see if that is a fix.
As they had a large complex with the same issue and this seemed to fix it: *) wireless - fixed incorrect wireless capability information in association response frames;
What’s new in 6.47.6 (2020-Oct-21 10:41):
*) cap - fixed L2MTU path discovery;
*) crs3xx - fixed hardware offloaded LACP bonding on Ethernet interfaces for CRS354 devices;
*) crs3xx - fixed switch rules for CRS309 and CRS317 devices (introduced in v6.47.3);
*) defconf - fixed default configuration loading on RBmAP-2nD;
*) dhcpv4-client - fixed DHCP offer packet parsing with overload option present;
*) dhcpv6-server - properly save bindings when executing “make-static” command;
*) fetch - improved SSL handshake processing;
*) ike1 - allow using “my-id” parameter with XAuth;
*) leds - fixed LED type setting;
*) lora - expose “joinEui” un “devEui” values in the log;
*) lte - fixed multiple APN passthrough on R11e-4G;
*) lte - improved EARFCN reporting in 3G and LTE modes on Sierra modems;
*) lte - limit allowed APN count to 3 on R11e-LTE;
*) mpls - fixed duplicate “LabelRelease” message sending;
*) ospf - optimized LSA printing for smaller message sizes;
*) radius - added “Service-Type” attribute to Access-Request for IPv4 and IPv6 DHCP servers;
*) smips - reduced RouterOS main package size;
*) switch - fixed Ethernet padding for small packets;
*) user - improved WinBox and The Dude authenticated session handling;
*) vrrp - made “password” parameter sensitive;
*) w60g - general stability and performance improvements;
*) wireless - added support for US FCC UNII-2 and Canada country profiles for NetMetal series devices;
*) wireless - fixed incorrect wireless capability information in association response frames;
For me this is the lottery. No control at all. At least “installation=indoor” is limiting the possible outcome.
But still you get from channel 36-48 up to channel 52-64 as possible frequency selection (5 cases) , where every of the 8 channels could be the control channel. (20 different selections possible)
Consequence:
if any of the channels 52 and up is in the selection, then the SSID will disappear for one minute (due to DFS) at startup or with any change to the interface settings.
-False radar detect will also make the SIID disappear for one minute.
-some client devices only support channel 36 till 48. If the control channel is in the 52 to 64 range they will not see the SSID.
EDIT: this cannot happen with “united states3” country selection, but I did not see that selected in the config file