09-10-2019 09:14 AM
09-20-2019 01:06 PM
Hello,
Thank you for your help.
The whole network/wireless architecture is OK now.
Thank you for your help.
Best regards,
09-12-2019 09:24 AM
Correct, some devices don't support the UNII-3 band.
Essentially yes, the client wouldn't see that the AP is broadcasting on the UNII-3 channel and only on the 2.4GHz so the client would connect to this (unless there was another AP nearby it wanted to connect to instead!)
If the client supports the UNII-3 channels then yes they wouldn't have to connect to the 2.4GHz, but it is a client decision as to which interface they connect to - unless you have band steering enabled for example.
09-12-2019 09:17 AM
Hello,
So some clients devices may not support the fact that UNI-3 is including, right ?
And in the case of a client who can't support these channels, he would've to connect on the 2.4GHz ?
So if he supports these channels (UNI-3) he wouldn't have to connect on the 2.4 GHz ?
Thanks in advance.
Best regards,
09-11-2019 03:10 PM
The only issue you may run into is that not all devices (see your insights > devices > max client capabilities) support these channels (in particular 165). But from what I've seen the majority of clients do support this band. Clients would then connect on the 2.4GHz instead.
Just a note on the error, it looks like it may be a bug - Aerohive support are investigating and replicating.