NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi Wifi 6 missing config command
I just bought an AX6000/RBK852. When I go to debug mode and enable telnet, I can log in fine. But the "config" command that was there on my old Orbi is missing. I need to be able to split my wifi int...
plainblackguy wrote:I just bought an AX6000/RBK852. When I go to debug mode and enable telnet, I can log in fine. But the "config" command that was there on my old Orbi is missing. I need to be able to split my wifi into 2.4 and 5ghz ssid's or a lot of my home automation devices refuse to connect. What am I missing?
You can use the nvram set command instead of config set so:
- nvram set ....
- nvram commit
Thank you so much for your reply. I've already sent the unit back to Amazon after reading a bunch of threads and realizing that Netgear doesn't seem to think this is a problem. I get that mesh networks are supposed to all be seamless between 5 and 2.4, but the reality in the smarthome market is very different right now and for the forseeable future. So I have returned my Orbi and bought the new Velop.
It's not a NG problem. Its how NG intends to use and design there systems. It works for the most part.
The main problem is that the client or IoT device mfrs limit there setup software to only the 2.4Ghz frequency. However they fail to realized that dual band devices like phone and pads can connect to either frequency and both frequencies are ON the same side of the network. So the phone or connecting devices or Orbi doesn't care which frequency for the setup device, it's the Mfrs setup software that seems to require the setup device, ie. phone or pad, to be connected to only the 2.4Ghz radio. Orbi AC helps with this with giving users the ability to disable the 5G SSID broadcast. We are hoping the NG will do the same for Orbi AX. If the IoT Mfrs put in 5Ghz support in there setup software for the setup phone or pad, users would be happy for this and we not be talking about this.
Good Luck.
No, it is a Netgear problem, but it's not a technology problem, it's a philosophical one. They choose to design a device in a way that does not meet the current market realities. I understand that if IoT device designers were smart they wouldn't design their devices the way they do. But the fact is that they do. And dreaming that you live in a world where things are as perfect as you'd like them to be is, rather than the world that you live in, is a huge mistake. I have no doubt that the Orbi is technically the best mesh router on the market. But a lot of the people interested in paying $700 for a pair of routers are the same people who are buying a lot of IoT and home automation devices. Some people may be willing to put up with the giant hassle of disconnecting from 5ghz (if that were even an option on Orbi, which it currently isn't) and turning off the broadcast for it and then messing around with your devices. But I'm not one of those people, and looking at the comments on the Netgear forums, it appears that there are thousands of people who are not those people. So while Velop is technically slightly inferior to the Orbi, from a philosophy and market reality perspective they are miles ahead.
