NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
cmftblynu
Jan 19, 2018Star
The 2.1.2.18 nightmare
I won't bother going through how angry I am at Netgear for this firmware MESS (I already have in several posts) since they don't bother offering ANY customer support after they screw you out of your ...
linkwrt
Jan 23, 2018Guide
cmftblynu wrote:I won't bother going through how angry I am at Netgear for this firmware MESS (I already have in several posts) since they don't bother offering ANY customer support after they screw you out of your money. I just wanted to tell everyone if you hate 2.1.2.18 as much as I do (well hate isn't the word, it just physically BREAKS my entire wired network... nothing wired has a connection NOTHING. I verified it 2 times because I reverted back to 2.1.2.16, when it was all working ok. Then it decided last night to RE-DOWNLOAD 2.1.2.18. You would think if you manually tell a product to revert back it wouldn't just re-do it. This is so dumb, my computer is hooked to a switch, that is connected to Orbi... when it updates to 2.1.2.18 I have to disconnect my computer from the switch because it breaks EVERYTHING on the switch nothing gets an ip... I have to connect directly to the orbi from my computer, I have to disconnect all the other wired connections to the orbi. Then I downgraded the firmware ONCE again, then I telnet into the router to change the NVram to not let this piece of crap update itself. That is my solution Netgear. A consumer had to do all that stuff because your firmware BREAKS everything. This started with me being angry at Google for breaking everything, now I blame netgear. It isn't my switch or any of my wired stuff, because it all magically works perfectly on 2.1.2.16. But the second I upgrade it all breaks, I even did the factory reset 2x, nothing wired works.. the funny thing is my switch is a netgear switch too... I have NEVER in my life had such a complicated product to keep running. In case anyone else is dealing with the same problems, below is how to telnet and stop it from updating. This is my only solution, I have absolutely 0 ZERO confidence in any firmware update from Netgear... based on a 100% failure rate:
1) Launch your favorite web browser and go to <Router IP Address>/debug.htm
2) Login <username> <password> when prompted
3) Check Enable Telnet
4) Start a Telnet session. I use Putty. Enter the <Router IP Address> Telnet is using port 23
5) You can skip this step if you like. I am calling it out for illustration purposes only...
Type nvram show | grep auto_* <ENTER>
You will see a list similar to this:
root@RBR50:/# nvram show | grep auto_
vpn_access_mode=auto
wl_auto_antenna=1
set_auto_agreement=0
orbi_auto_upgrade=1
ipv6_autoConfig_dns_assign=0
ipv6_autoConfig_dns1=
ipv6_autoConfig_dns2=
upnp_enable_autoScan=0
ipv6_auto_dns_assign=0
bas_auto_conn_flag=0
orbi_auto_upg=0
autofw_port0=
ipv6_auto_dns1=
ipv6_auto_dns2=
qos_auto_bandwidth=0
green_enable_autorefresh_status=0
enable_dev_auto_refresh=1
wl_rate=auto
auto_check_for_upgrade=1
auto_update=1
root@RBR50:/# root@RBR50:/#
The 3 configurations highlighted above you will want to update the value from =1 to =0
orbi_auto_upgrade=1
auto_check_for_upgrade=1
auto_update=1
6) To update run the following commands:
nvram set orbi_auto_upgrade=0 <ENTER> (no spaces after set)
nvram set auto_check_for_upgrade=0 <ENTER> (no spaces after set)
nvram set auto_update=0 <ENTER> (no spaces after set)
7) Type the following commands to confirm the 3 configurations are set to =0
nvram show | grep orbi_auto_upgrade <ENTER>
nvram show | grep auto_check_for_upgrade <ENTER>
nvram show | grep auto_update <ENTER>
8) After you confirmed the 3 configuration values are set to =0 then type nvram commit <ENTER> (this step will save the changes)
9) Type exit to terminate the telnet session
10) Go back to the <Router IP Address>/debug.htm web page and uncheck Enable Telnet
Please note within a day or so the Orbi will know there is an updated firmware release available but it will not automatically install it. If you do go back into a Telnet session after the Orbi knows there is an updated firmware release the configuration orbi_auto_upgrade will have a value greater than 1. That is okay. Do not change the value back to =0
You are doing complicated this.
You need to setup using next next next, and orbi will do the best for you.
I dont' have any issue, i use default settings.
- linkwrtJan 23, 2018Guide
I have RBK50 kit for EU.
So RBR50 router is ok, no issue, but when i connect RBS50 using Europe country i have issue with 2.4Ghz /5Ghz.
What it did to fix satellite:
- i set RBR50 (router) to United States
- i set 2.4Ghz and 5Ghz channels to AUTO
- i checked Enable Daisy-Chain Topology
- i enabled BEAMFORMING
- i enabled MU-MIMO
- Fast-Roaming can be enabled or disabled as you wish.
- i did a reset to default factory satellite, then after reboot it connected automatically to RBR50 router.
What i saw:
- if satellite is close to router , it select 5Ghz
- if satellite is in same room but not near router, it select 2.4Ghz
- if satellite is in other room, it select 5Ghz , after i did previously steps.
What we need from netgear team is to let user separate 2.4Ghz and 5Ghz SSID and also a option where user can select bandwith between satellite and router:
for example Auto will select 2.4ghz if signal is lower than 5Ghz, 2.4ghz if user want 2.4ghz and 5ghz if user want 5ghz.
I get using satellite connected to router using wireless, then lan on satellite almost 700-800mbps on speedtest.
-----------
I tested this firmware using RBS50 on next room, between 1 wall, and i get also using wireless 650-700mbps.
So this is very good.
I don't see where i can reboot RBS50 satellite.
Next test was latency: between RBS50 satellite and RBS50 router i aget 0.4-0.7ms, but latency is between 0.5-0.7ms, and can get lower.
Note that MU-MIMO and beamforming is enabled.
--------
Name (SSID) yourname
Region United States
Channel 36(P)+40+44+48
Mode Up to 866.7 Mbps
2.4Ghz channel auto
5Ghz channel 36
WPA2-PSK [AES]
WMM enabled
20/40 Mhz Coexistence enabled
CTS/RTS 2347
Preamble automatic
Enable Daisy... checked
Beamforming -- enabled
MU-MIMO -enable
For me , this is working.- rhester72Jan 23, 2018Virtuoso
You don't ever want the wireless backhaul to go over 2.4GHz, because there's no radio dedicated to it.
- linkwrtJan 23, 2018Guide
Maybe is something wrong with firmware, because it display 2.4Ghz for europe on satellite.
If router is set to united states or other country , it display 5ghz.