ORBI RBK50/RBS50 Tips, Tricks, Hidden Secrets, etc.,

[SW_]

A place to share ORBI goodies/secrets.

Replace 192.168.1.1 bellow with your Orbi Router or Satellite IP:

• http://192.168.1.1/hidden_info.htm

Please don't forget to share yours.  Cheers! 🙂

[SW_]

To check out Orbi backhaul signal strength, try this:

• root@RBR50:/# wlanconfig ath2 list

root@RBR50:/# wlanconfig ath2 list
ADDR AID CHAN TXRATE RXRATE RSSI MINRSSI MAXRSSI...

14:59:c0:3b:e7:xx 1 157 780M 780M 27 0 33 ...

14:59:c0:3b:e1:xx 2 157 1300M 1300M 40 0 50 ...

Backhaul chan is 157.  One of my Satellites (-68 dBm) is near the edge, too close to -70dBm for comfort.  That also explains the reason for lower link rate of 780M.

• 27 - 95 = -68 dBm
• 40 - 95 = -55 dBm

Signal Strength	Result		Required for
-30 dBm	Amazing	Max achievable signal strength. The client can only be a few feet from the AP to achieve this. Not typical or desirable in the real world.	N/A
-67 dBm	Very Good	Minimum signal strength for applications that require very reliable, timely delivery of data packets.	VoIP/VoWiFi, streaming video
-70 dBm	Okay	Minimum signal strength for reliable packet delivery.	Email, web
-80 dBm	Not Good	Minimum signal strength for basic connectivity. Packet delivery may be unreliable.	N/A
-90 dBm	Unusable	Approaching or drowning in the noise floor. Any functionality is highly unlikely.	N/A

[SW_]

If you don't want to figure out the backhaul interface or do the math, try this:

• root@RBR50:/# cat /tmp/satellite_device_info

root@RBR50:/# cat /tmp/satellite_device_info

[{

                "mac address":  "xx",

                "ip address":   "192.168.1.9",

                "module name":  "RBS50",

                "serial number":        "xx",

                "signal strength":      "-55",

                "current version":      "V2.3.1.48",

                "backhaul status":      "2",

                "device name":  "Orbi Satellite-1"

        }, {

                "mac address":  "xx",

                "ip address":   "192.168.1.8",

                "module name":  "RBS50",

                "serial number":        "xx",

                "signal strength":      "-68",

                "current version":      "V2.3.1.48",

                "backhaul status":      "2",

                "device name":  "Orbi Satellite-2"

        }]

root@RBR50:/# 

[michaelkenward]

For the sake of completeness:

http://192.168.1.1/debug.htm

not to be confused with

http://192.168.1.1/debug.html

[SW_]

If you need telnet on your MacOS:

First you’d download the latest, inetutils-1.9.4.tar.gz, inetutils package from GNU Telnet.  To compile/install telnet locally on your MacOS, assuming you have already installed Apple Xcode, which is free from App Store:

• tar xvzf inetutils-1.9.4.tar.gz
• cd inetutils-1.9.4
• ./configure
• make
• sudo make install

[FURRYe38]

I've found ZOC works well for telnet on OSX:

https://www.emtec.com/zoc/index.html

[ekhalil]

---

@SW_ wrote:

If you don't want to figure out the backhaul interface or do the math, try this:

• root@RBR50:/# cat /tmp/satellite_device_info

...... 

---

Another command for similar information:

root@RBR50:/# cat /var/current_satellite_list

[{

                "mac address":  "xxxxxxxx",

                "ip address":   "192.168.1.2",

                "module name":  "RBS50",

                "serial number":        "xxxxxxxx",

                "signal strength":      "-55",

                "backhaul status":      "2",

                "device name":  "Orbi Satellite-1",

                "current version":      "V2.3.1.60"

        }]

root@RBR50:/#

[ekhalil]

Read your latest Orbi DNS quiries log:

root@RBR50:/# cat /tmp/dnsmasq.log

Other DNS-related commands:

root@RBR50:~# cat /etc/hosts

root@RBR50:~# cat /tmp/hosts

root@RBR50:~# cat /etc/dnsmasq.conf

root@RBR50:~# cat /tmp/resolv.conf

[ekhalil]

Orbi Radio, useful commands:

root@RBR50:~# cat /tmp/netscan_if_conf

eth1 wired 1

ath0 2G 0

ath01 satellite 0

ath1 5G 0

ath2 satellite 0

ath02 2G-GUEST 0

ath11 5G-GUEST 0

eth0 wired 2

root@RBR50:~# cat /tmp/wifi_topology

NORMAL:AP:wifi0:ath0:@wifi-iface[0]:wl

BACKHAUL:AP:wifi0:ath01:@wifi-iface[1]:wlg_ap_bh

NORMAL:AP:wifi1:ath1:@wifi-iface[2]:wla

GUEST:AP:wifi0:ath02:@wifi-iface[3]:wlg1

GUEST:AP:wifi1:ath11:@wifi-iface[4]:wla1

BACKHAUL:AP:wifi2:ath2:@wifi-iface[5]:wla_2nd_ap_bh

ath0 (Fronthaul 2.4GHz)

ath01 (Backhaul 2.4GHz)

ath02 (Guest 2.4GHz)

ath1 (Fronthaul 5GHz)

ath2 (Backhaul 5GHz)

ath11 (Guest 5 GHz)

root@RBR50:/# wlanconfig ath0 list active -l

Channel   1 : 2412    Mhz 11ng C CU                                        Channel   8 : 2447    Mhz 11ng C CU CL                                     

Channel   2 : 2417    Mhz 11ng C CU                                        Channel   9 : 2452    Mhz 11ng C CU CL                                     

Channel   3 : 2422    Mhz 11ng C CU                                        Channel  10 : 2457    Mhz 11ng C CL                                        

Channel   4 : 2427    Mhz 11ng C CU                                        Channel  11 : 2462    Mhz 11ng C CL                                        

Channel   5 : 2432    Mhz 11ng C CU CL                                     Channel  12 : 2467    Mhz 11ng C CL                                        

Channel   6 : 2437    Mhz 11ng C CU CL                                     Channel  13 : 2472    Mhz 11ng C CL                                        

Channel   7 : 2442    Mhz 11ng C CU CL                                     

root@RBR50:/# wlanconfig ath01 list active

Channel   1 : 2412    Mhz 11ng C CU                                        Channel   8 : 2447    Mhz 11ng C CU CL                                     

Channel   2 : 2417    Mhz 11ng C CU                                        Channel   9 : 2452    Mhz 11ng C CU CL                                     

Channel   3 : 2422    Mhz 11ng C CU                                        Channel  10 : 2457    Mhz 11ng C CL                                        

Channel   4 : 2427    Mhz 11ng C CU                                        Channel  11 : 2462    Mhz 11ng C CL                                        

Channel   5 : 2432    Mhz 11ng C CU CL                                     Channel  12 : 2467    Mhz 11ng C CL                                        

Channel   6 : 2437    Mhz 11ng C CU CL                                     Channel  13 : 2472    Mhz 11ng C CL                                        

Channel   7 : 2442    Mhz 11ng C CU CL                                     

root@RBR50:/# wlanconfig ath02 list active

Channel   1 : 2412    Mhz 11ng C CU                                        Channel   8 : 2447    Mhz 11ng C CU CL                                     

Channel   2 : 2417    Mhz 11ng C CU                                        Channel   9 : 2452    Mhz 11ng C CU CL                                     

Channel   3 : 2422    Mhz 11ng C CU                                        Channel  10 : 2457    Mhz 11ng C CL                                        

Channel   4 : 2427    Mhz 11ng C CU                                        Channel  11 : 2462    Mhz 11ng C CL                                        

Channel   5 : 2432    Mhz 11ng C CU CL                                     Channel  12 : 2467    Mhz 11ng C CL                                        

Channel   6 : 2437    Mhz 11ng C CU CL                                     Channel  13 : 2472    Mhz 11ng C CL                                        

Channel   7 : 2442    Mhz 11ng C CU CL                                     

root@RBR50:/# wlanconfig ath1 list active -l

Channel  36 : 5180 *  Mhz 11na C CU V VU V80- 42                           Channel  52 : 5260 *~ Mhz 11na C CU V VU V80- 58                           

Channel  40 : 5200 *  Mhz 11na C CL V VL V80- 42                           Channel  56 : 5280 *~ Mhz 11na C CL V VL V80- 58                           

Channel  44 : 5220 *  Mhz 11na C CU V VU V80- 42                           Channel  60 : 5300 *~ Mhz 11na C CU V VU V80- 58                           

Channel  48 : 5240 *  Mhz 11na C CL V VL V80- 42                           Channel  64 : 5320 *~ Mhz 11na C CL V VL V80- 58                           

root@RBR50:/# wlanconfig ath2 list active

Channel 100 : 5500 *~ Mhz 11na C CU V VU V80-106 V160-114                  Channel 124 : 5620 *~ Mhz 11na C CU V VU V80-122 V160-114                  

Channel 104 : 5520 *~ Mhz 11na C CL V VL V80-106 V160-114                  Channel 128 : 5640 *~ Mhz 11na C CL V VL V80-122 V160-114                  

Channel 108 : 5540 *~ Mhz 11na C CU V VU V80-106 V160-114                  Channel 132 : 5660 *~ Mhz 11na C CU V VU                                   

Channel 112 : 5560 *~ Mhz 11na C CL V VL V80-106 V160-114                  Channel 136 : 5680 *~ Mhz 11na C CL V VL                                   

Channel 116 : 5580 *~ Mhz 11na C CU V VU V80-122 V160-114                  Channel 140 : 5700 *~ Mhz 11na C V                                         

Channel 120 : 5600 *~ Mhz 11na C CL V VL V80-122 V160-114                  

root@RBR50:/# wlanconfig ath11 list active

Channel  36 : 5180 *  Mhz 11na C CU V VU V80- 42                           Channel  52 : 5260 *~ Mhz 11na C CU V VU V80- 58                           

Channel  40 : 5200 *  Mhz 11na C CL V VL V80- 42                           Channel  56 : 5280 *~ Mhz 11na C CL V VL V80- 58                           

Channel  44 : 5220 *  Mhz 11na C CU V VU V80- 42                           Channel  60 : 5300 *~ Mhz 11na C CU V VU V80- 58                           

Channel  48 : 5240 *  Mhz 11na C CL V VL V80- 42                           Channel  64 : 5320 *~ Mhz 11na C CL V VL V80- 58 

[ekhalil]

The artmtd commands are useful:

Usage: artmtd -r name [<arguments> ...]

************* SN Usage:

SN read:

artmtd -r sn

SN write:

artmtd -w sn number

For instance: artmtd -w sn 1ML1747D0000B

SN should be 0~9 or A~Z

************* REGION Usage:

REGION read:

artmtd -r region

REGION wirte:

Usage: artmtd -w region region name

For instance : artmtd -w region NA

The REGION name only is "NA,WW,GR,PR,RU,BZ,IN,KO,JP,AU,CA"

************* LANGUAGE Usage:

Language read:

artmtd -r language

************* SSID Usage:

ssid read:

artmtd -r fronthaul_ssid

ssid write:

artmtd -w fronthaul_ssid SSID

ssid read:

artmtd -r backhaul_ssid

ssid write:

artmtd -w backhaul_ssid SSID

************* PASSPHRASE Usage:

passphrase read:

artmtd -r fronthaul_passphrase

passphrase write:

artmtd -w fronthaul_passphrase PASSPHRASE

passphrase read:

artmtd -r backhaul_passphrase

passphrase write:

artmtd -w backhaul_passphrase PASSPHRASE

************* WPSPIN Usage:

wpspin read:

artmtd -r wpspin

wpspin write:

artmtd -w wpspin 12345670

*************HW MODEL ID Usage:

HW MODEL ID read:

artmtd -r board_hw_id

artmtd -r board_model_id

artmtd -w board_hw_id HW_ID

artmtd -w board_model_id MODEL_ID

*************MAC Usage:ssid read:

artmtd -r mac

ssid read:

artmtd -w mac_lan 00:11:22:33:44:50

ssid read:

artmtd -w mac_wan 00:11:22:33:44:51

ssid read:

artmtd -w mac_5g  00:11:22:33:44:52

ssid read:

artmtd -w mac_2nd5g  00:11:22:33:44:53

ssid read:

artmtd -w mac_bt  00:11:22:33:44:54

*************BOARD DATA Usage:board data read:

artmtd -r board_data

board data write:

artmtd -w board_data 1102

*************BOOT PART Usage:board data read:

artmtd -r boot_part

board data write:

artmtd -w boot_part [01|02]

*************HW REVISION Usage:hw_revision read:

artmtd -r hw_revision

hw_revision write:

artmtd -w hw_revision 01

root@RBR50:/#

[ekhalil]

To see the events when Orbi detects radar signals you can check this in Orbi log:

> root@RBR50:~# cat /var/radardetect.log

Radar Detected at [Wed Jan 23 23:19:55 CET 2019 ] on channels [116,120,124,128]

Radar Detected at [Wed Jan 23 23:26:20 CET 2019 ] on channels [100,104,108,112]

Radar Detected at [Wed Jan 23 23:26:30 CET 2019 ] on channels [132,136]

Radar Detected at [Wed Jan 23 23:42:35 CET 2019 ] on channels [140]

Radar Detected at [Wed Jan 23 23:45:52 CET 2019 ] on channels [116,120,124,128]

Radar Detected at [Wed Jan 23 23:50:52 CET 2019 ] on channels [100,104,108,112]

Radar Detected at [Wed Jan 23 23:51:58 CET 2019 ] on channels [132,136]

Radar Detected at [Wed Jan 23 23:53:04 CET 2019 ] on channels [140]

Radar Detected at [Wed Jan 23 23:59:20 CET 2019 ] on channels [116,120,124,128]

Radar Detected at [Thu Jan 24 00:00:06 CET 2019 ] on channels [100,104,108,112]

Radar Detected at [Thu Jan 24 00:00:53 CET 2019 ] on channels [132,136]

Radar Detected at [Thu Jan 24 00:07:56 CET 2019 ] on channels [140]

Radar Detected at [Thu Jan 24 00:09:39 CET 2019 ] on channels [116,120,124,128]

Radar Detected at [Thu Jan 24 00:09:49 CET 2019 ] on channels [100,104,108,112]

Radar Detected at [Thu Jan 24 00:12:19 CET 2019 ] on channels [132,136]

Radar Detected at [Thu Jan 24 00:23:17 CET 2019 ] on channels [140]

Radar Detected at [Thu Jan 24 00:28:47 CET 2019 ] on channels [116,120,124,128]

Radar Detected at [Thu Jan 24 00:33:19 CET 2019 ] on channels [100,104,108,112]

Radar Detected at [Thu Jan 24 00:33:57 CET 2019 ] on channels [132,136]

Radar Detected at [Thu Jan 24 00:34:25 CET 2019 ] on channels [140]

Radar Detected at [Thu Jan 24 00:36:27 CET 2019 ] on channels [116,120,124,128]

Radar Detected at [Thu Jan 24 00:37:14 CET 2019 ] on channels [100,104,108,112]

[SW_]

To restore default configs and force Satellites to refresh/pull new settings from main Orbi Router,

try this:

• config default
• config commit
• reboot

- or -

Going nuclear, Factory Reset, with paper clip method.

[SW_]

A practical solution that seems to resolve Satellite connection issues for users.

• @Bullyterrier wrote: I’ve found you need to do this to ‘clean out’ a satellite config.

User's testaments:

• @StCanard 's post
• @ekhalil 's post

I've not tried this myself, but it's worth a shot if you're facing similar issue.

[SW_]

If you don't want to install old-style telnet on your Mac, you can also telnet from a terminal with 'nc' command.

• nc <ip-address> <port>

Just replace the IP address with your ORBI's IP address.

• nc 192.168.1.1 23

For Windows, you can enable telnet client here.

[SW_]

---

@ekhalil wrote:

---

@SW_ wrote:

If you don't want to figure out the backhaul interface or do the math, try this:

• root@RBR50:/# cat /tmp/satellite_device_info 

---

Another command for similar information:

root@RBR50:/# cat /var/current_satellite_list

Well, if you really don't feel comfortable with telnet,

try this:

Replace 192.168.1.1 with your ORBI IP address.

• http://192.168.1.1/online_upgrade_info.html

Unfortunately, the text is raw, not formatted properly.  However, you should be able easily find Orib/Satellite Backhaul "signal strength" value along with other goodies regarding Backhaul status.

[FURRYe38]

Check FW release notes:

https://http.fw.updates1.netgear.com/<model string>/ww/stringtable.dat

<model string> = rbr## or rbs## or rbw##, etc

[SW_]

To get 2.4Ghz/5Ghz bands steering default value, type this cmd:

1. config get enable_band_steering

To disable 2.4Ghz/5Ghz bands steering, type these cmds:

1. config set enable_band_steering=0
2. config commit
3. reboot

To enable 2.4Ghz/5Ghz bands steering, type these cmds:

1. config set enable_band_steering=1
2. config commit
3. reboot

If you've tried, please share your experience here.

[FURRYe38]

Direct web page access to RBS web page

A little mentioned method to connect to a RBS if FW is out of date or the RBS fails to sync due to FW not being in sync or on same FW version as RBR. 

Users can do a factory reset on there RBS. Connect a LAN cable connected PC to the back of the RBS and wait 5 minutes approx, the PC will receive an IP and Gateway addressing on the PC. Look at the network status on the PC and you see that the Gateway should be 192.168.1.250. User can input this IP address into a web browser while the PC is connected to the RBS and access the RBSs web page. Default log in is admin and PW is password. 

Old FW or Out of Sync FW on or between RBR and RBS

Recommended intermediate migration FW version is v2.0.0.74 for users who have RBR/RBS with old or first released (v1.x) versions of FW. To get from old versions of FW, prior v2.1 or v1.x, users need to first load v2.0.0.74 on both RBS and RBR. Then users can update to v2.3.x versions of FW. 

[RussFogg]

Thanks for the quick response..

Would a wired connection be needed for your solution of below or can it be done via WiFi connection?

Old FW or Out of Sync FW on or between RBR and RBS
Recommended intermediate migration FW version is v2.0.0.74 for users who have RBR/RBS with old or first released (v1.x) versions of FW. To get from old versions of FW, prior v2.1 or v1.x, users need to first load v2.0.0.74 on both RBS and RBR. Then users can update to v2.3.x versions of FW.

[FURRYe38]

Wired is preferred however wireless should work fine. Besure to update the RBS first, then RBR as you graduate versions.

---

@RussFogg wrote:
Thanks for the quick response..

Would a wired connection be needed for your solution of below or can it be done via WiFi connection?

Old FW or Out of Sync FW on or between RBR and RBS
Recommended intermediate migration FW version is v2.0.0.74 for users who have RBR/RBS with old or first released (v1.x) versions of FW. To get from old versions of FW, prior v2.1 or v1.x, users need to first load v2.0.0.74 on both RBS and RBR. Then users can update to v2.3.x versions of FW.

---

[RussFogg]

Wow thanks for that tip...”Besure to update the RBS first, then RBR as you graduate versions.”

Will give it a go in the morning, thanks.

[FURRYe38]

Let us know how it goes back on your OP:

https://community.netgear.com/t5/Orbi/Upgrading-from-V1-4-0-18/m-p/1749054#M61484

---

@RussFogg wrote:
Wow thanks for that tip...”Besure to update the RBS first, then RBR as you graduate versions.”

Will give it a go in the morning, thanks.

---

[ekhalil]

You can check and change the transmission power in the different interfaces in Orbi with the following telnet commands:

1) To print the current transmission power levels:

root@RBR50:~# iwlist ath2 txpower

ath2 8 available transmit-powers :
0 dBm (1 mW)
6 dBm (3 mW)
10 dBm (10 mW)
14 dBm (25 mW)
18 dBm (63 mW)
22 dBm (158 mW)
26 dBm (398 mW)
30 dBm (1000 mW)
Current Tx-Power:30 dBm (1000 mW)

2) To change power levels:
root@RBR50:~# iwconfig ath2 txpower 3mW

root@RBR50:~# iwconfig ath2 commit

Where the interface names are as follows (for RBR50/RBS50):

ath0 (Fronthaul 2.4GHz)

ath1 (Fronthaul 5GHz)

ath02 (Guest 2.4GHz)

ath11 (Guest 5 GHz)

ath01 (Backhaul 2.4GHz)

ath2 (Backhaul 5GHz)

[2022]

I have Orbi RBR50 but its rebranded and controlled by the ISP and I can't upgrade the software without ISP's concent.

Usually the ISP will release the upgrade

Many new firmware released and i still using 2.1.4.16

there is any way to re-flushing the device and install original NG firmware woithout the ISP branding

Please help

Regards,

Adnan.

[FURRYe38]

If the Orbi system is operated and controlled by the ISP, then you'll need to contact the ISP for help and support as they are repsonsible for that unit under there system. Theres nothing we can do here. I recommend getting in to a retail version of Orbi then you'll have better control over it and NG will be officially supporting of it. 

---

@2022 wrote:

I have Orbi RBR50 but its rebranded and controlled by the ISP and I can't upgrade the software without ISP's concent.

Usually the ISP will release the upgrade

Many new firmware released and i still using 2.1.4.16

there is any way to re-flushing the device and install original NG firmware woithout the ISP branding

Please help

Regards,

Adnan.

---