The OrbiApp scanner comes with some data, and it appears we can't make any meaning out of that or change any channel settings in the web interface. See the attached file for additional information
I would think, if we are not expected make any changes in channel setting ( via web interface), it may be useful to call it out like that, to be more helpful.
The OrbiApp scanner comes with some data, and it appears we can't make any meaning out of that or change any channel settings in the web interface. See the attached file for additional information
I would think, if we are not expected make any changes in channel setting ( via web interface), it may be useful to call it out like that, to be more helpful.
The original Orbi web interface allows the user to set the 2.4G WiFi channel (1 to 11 in NA, 1 to 13 in the rest of the world) and the 5G WiFi channel 36 through 48 in NA.
Not having an AX Orbi, I have no idea if the web interface omits those choices for the AX product.
This is an example of why I find the Orbi "app" so frustrating. It is as if a team went off with great intentions to develop a smartphone version of the Orbi web interface, got started, and then..... just quit.
There are numerous Orbi features that cannot be accessed or controlled by the app: IP reservations, DHCP range specification, subnet IP specification, DNS servers, DDNS, VPN, Port Forwarding, Orbi logs, saving/reloading configuration, etc. etc.
It is even more goofy that there are some features that can only be managed with the app, such as Armor and Parental Control.
.jpg){kind=link}