NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Tenet command: not found
So ive been attmeptign to disable the 5g network or seperate the 2.4g and 5 g networks but no mater command i run its not found. For instnce: admin@CBR40:# config get wl_ssid /bin/ash: config...
I agree. The crazy thing is that logging on with "admin" and the Orbi administrative password is successful, but then (1) the prompt is not "root" and (2) BusyBox commands are not recognized. (even the error message is different from mine).
This is what I get if I run "busybox" , the commanbds listed there work. I dont see get or config
"config" is not in my BusyBox, either. My BusyBox is v1.24.1 and yours is v1.23.2 My BusyBox has 99 commands that are not in yours, while yours has 8 commands that are not in mine. There are 109 commands that are in both. Who would have thought the Netgear team developing Orbi would use entirely different versions of BusyBox for different products?
Can you log into the Orbi, change directories to /bin and list all the files? i.e.
cd /bin
ls -l
Aint that crazy right?! Abd yes I can, I did however do that and did not see the comands i was looking for:
lrwxrwxrwx 1 root root 7 Jun 26 00:34 ash -> busybox
-rwxrwxr-x 1 root root 265 Jun 25 23:25 board_detect
-rwxr-xr-x 1 root root 378781 Jun 26 00:05 busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 cat -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 chgrp -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 chmod -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 chown -> busybox
-rwxr-xr-x 1 root root 55315 Jun 27 06:41 circled
-rwxrwxr-x 1 root root 3311 Jun 25 23:25 config_generate
lrwxrwxrwx 1 root root 7 Jun 26 00:34 cp -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 date -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 dd -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 df -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 dmesg -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 echo -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 egrep -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 false -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 fgrep -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 fsync -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 grep -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 gunzip -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 gzip -> busybox
-rwxrwxr-x 1 root root 1550 Jun 25 23:25 ipcalc.sh
lrwxrwxrwx 1 root root 7 Jun 26 00:34 kill -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 ln -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 lock -> busybox
lrwxrwxrwx 1 root root 8 Jun 27 06:41 login -> login.sh
-rwxrwxr-x 1 root root 424 Jun 25 23:25 login.sh
-rwxr-xr-x 1 root root 828 Jun 27 06:41 login_telnet2
lrwxrwxrwx 1 root root 7 Jun 26 00:34 ls -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 mkdir -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 mknod -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 mktemp -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 mount -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 mv -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 netmsg -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 netstat -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 nice -> busybox
-rwxr-xr-x 1 root root 117320 Jun 26 00:14 opkg
lrwxrwxrwx 1 root root 7 Jun 26 00:34 pidof -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 ping -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 ping6 -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 ps -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 pwd -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 rm -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 rmdir -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 sed -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 sh -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 sleep -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 stat -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 sync -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 tar -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 touch -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 true -> busybox
-rwxr-xr-x 1 root root 6555 Jun 26 00:13 ubus
lrwxrwxrwx 1 root root 7 Jun 26 00:34 umount -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 uname -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 vi -> busybox
lrwxrwxrwx 1 root root 7 Jun 26 00:34 zcat -> busybox
Our systems are not anything alike. I have no idea how they can be so different and perform the same functions.
Since we are not getting very far in this direction, maybe it would be useful to open a new post and ask for advice on getting the specific device to connect to Orbi. For example, when people began complaining about their "Smart Plug" needed 2.4G to connect, I purchased a bunch of them and found that they ALL connected just fine. Even the one that complained, "Must set phone to 2.4G!!!" I simply ignored the message, hit "Continue", and the plug worked.
It is well-established that it is not the presence of the Orbi 5G signal that interferes with the actual device. The device has only a 2.4G radio and thus is blissfully ignorant of 5G, just as it isn't bothered by 900MHz wireless phones or cell phone signals. Sometimes it is the smartphone app that is written poorly.
What is this thing?
The user has a CBR40 which differs from the RBR units...The CBR40 is a built in CM700 cable modem. I presume the backend FW will differ from RBR systems. I have the CBR40 as well...
CrimpOn wrote:Our systems are not anything alike. I have no idea how they can be so different and perform the same functions.
Since we are not getting very far in this direction, maybe it would be useful to open a new post and ask for advice on getting the specific device to connect to Orbi. For example, when people began complaining about their "Smart Plug" needed 2.4G to connect, I purchased a bunch of them and found that they ALL connected just fine. Even the one that complained, "Must set phone to 2.4G!!!" I simply ignored the message, hit "Continue", and the plug worked.
It is well-established that it is not the presence of the Orbi 5G signal that interferes with the actual device. The device has only a 2.4G radio and thus is blissfully ignorant of 5G, just as it isn't bothered by 900MHz wireless phones or cell phone signals. Sometimes it is the smartphone app that is written poorly.
What is this thing?
Yes, we discovered that his model has the built-in modem. What comes as a surprise to me is how different the firmware is. It is still an Orbi. One wonders how the Netgear engineers even work on it with all the BusyBox commands that are missing (99 if I counted correctly).
Ya however the HW system and FW is different and there are two different depts working on each system. There separate systems thus there is probably a disconnect between them. The FW version have never really synced between the RBR and CBR. The CBR is based off the 40 series system. Hoever I presume they have to do things to make it all work with the modem inside. It is it's own system and shouldn't be treated as similar or same as the RBR systems.
I just purchased this modem router. And tried to configure 2.4 and 5ghz separetely. I am also facing same issue. Were you able to resolve this issue?
