NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Christian_R
Jul 16, 2021NETGEAR Employee Retired
RBK750 Series - Firmware Update v4.6.3.7
Hello Orbi AX Community,
We are excited to announce that we have started to roll out new firmware which enables NETGEAR Smart Parental Controls on RBK750 Systems. Customers with RBK750 series ...
Xcelebric
Aug 23, 2021Guide
Here is the latest update from my trying:
1. Downgrade the Firmware to V3.2.10.10 for both Router and the Satellite, which is the very first Firmware version. Using the way I mentioned in previous thread that pressing F12 in the downgrade page and unhide the Yes button.
This Firmware version has Telnet option on Debug page.
2. After that, perform factory reset on both Router and the Satellite.
3. Finish basic configuration, but DO NOT connect to internet yet.
4. Enable Telnet option on both Router and the Satellite in their Debug.html page.
5. Telnet connect to both devices, and ran the following:
nvram set auto_upgrade_enable=0
nvram set ver_check_https_svr1=http.fw.updates1.aaa.com
nvram set ver_check_ftp_svr1=updates1.aaa.com
nvram set ver_check_ftp_svr2=updates1.aaa.com
nvram set ver_check_ftp_svr3=updates1.aaa.com
nvram set lang_check_ftp_svr=updates1.aaa.com
nvram set install_fw_upgrade_latest=0
nvram set ver_check_enable=0
nvram set ver_check_ftp_password=aaa@aaa
nvram set control_cloud_backend_fw_url=https://http.fw.updates1.aaa.com
nvram set promotion_server=updates1.aaa.com
nvram commit
6. Make sure the above run on both devices.
7. Go to Managment page -> Advanced -> Security -> Block Sites :
a. Keyword Block set to "Always"
b. Add the following key words:
http.fw.updates1.netgear.com
updates1.netgear.com
c. Click Apply.
8. Perform a Soft reboot from Advanced Home : -> Reboot -> Connect back to the Internet.
9. After that, my firmware update page showing this:
Status:
Router RBR750 RBR750 V3.2.10.10 Service unreachable
Satellite RBS750 Orbi Satellite-1 V3.2.10.10 Service unreachable
10, I will monitor for a day or so to see if this works.
Donsuper
Oct 09, 2021Star
Will I need to unblock those update site if I want to update the firmware one day? Or it will undo all the blocking in the update process? Thank you so much.
- ThaladorOct 09, 2021Apprentice
Donsuper wrote:
Will I need to unblock those update site if I want to update the firmware one day? Or it will undo all the blocking in the update process? Thank you so much.Don't unblock. Leave it so NG can never ever do this again. Download the firmware and do a manual.
- FURRYe38Oct 09, 2021Guru - Experienced User
IF you unblock, you can get the update automatically. If you don't block and still manually update using the FW files. IF your blocking by using a upstream router.
Donsuper wrote:
Will I need to unblock those update site if I want to update the firmware one day? Or it will undo all the blocking in the update process? Thank you so much.- gthiOct 10, 2021Guide
This is what happens when you ping rhe router during wifi drop outs.
Firmware Version
V4.6.3.16_2.0.51Time out and respons at the same time...
This is definitely a routing problem and has nothing to do with coverage.
I will return the whole 1800 euro system in te next couple of days dor a refund.
Good bye Netgear
Last login: Fri Oct 8 15:57:16 on console
ping 10.0.0.1
PING 10.0.0.1 (10.0.0.1): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=2390.607 ms
64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=1882.943 ms
64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=911.565 ms
64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=247.726 ms
64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=164.955 ms
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
64 bytes from 10.0.0.1: icmp_seq=6 ttl=64 time=4442.170 ms
64 bytes from 10.0.0.1: icmp_seq=7 ttl=64 time=3592.775 ms
64 bytes from 10.0.0.1: icmp_seq=8 ttl=64 time=2659.576 ms
64 bytes from 10.0.0.1: icmp_seq=9 ttl=64 time=1758.673 ms
64 bytes from 10.0.0.1: icmp_seq=11 ttl=64 time=446.292 ms
64 bytes from 10.0.0.1: icmp_seq=13 ttl=64 time=189.283 ms
64 bytes from 10.0.0.1: icmp_seq=14 ttl=64 time=206.045 ms
64 bytes from 10.0.0.1: icmp_seq=15 ttl=64 time=586.657 ms
64 bytes from 10.0.0.1: icmp_seq=17 ttl=64 time=879.643 ms
64 bytes from 10.0.0.1: icmp_seq=18 ttl=64 time=1997.987 ms
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
64 bytes from 10.0.0.1: icmp_seq=19 ttl=64 time=3749.005 ms
64 bytes from 10.0.0.1: icmp_seq=20 ttl=64 time=2903.914 ms
64 bytes from 10.0.0.1: icmp_seq=21 ttl=64 time=2062.794 ms
64 bytes from 10.0.0.1: icmp_seq=22 ttl=64 time=1072.782 ms
64 bytes from 10.0.0.1: icmp_seq=24 ttl=64 time=353.735 ms
64 bytes from 10.0.0.1: icmp_seq=25 ttl=64 time=256.697 ms
64 bytes from 10.0.0.1: icmp_seq=28 ttl=64 time=119.776 ms
Request timeout for icmp_seq 29
64 bytes from 10.0.0.1: icmp_seq=30 ttl=64 time=284.688 ms
Request timeout for icmp_seq 31
Request timeout for icmp_seq 32
Request timeout for icmp_seq 33
Request timeout for icmp_seq 34
Request timeout for icmp_seq 35
64 bytes from 10.0.0.1: icmp_seq=33 ttl=64 time=3801.090 ms
64 bytes from 10.0.0.1: icmp_seq=34 ttl=64 time=2798.878 ms
64 bytes from 10.0.0.1: icmp_seq=35 ttl=64 time=1981.872 ms
64 bytes from 10.0.0.1: icmp_seq=36 ttl=64 time=994.666 ms
Request timeout for icmp_seq 40
Request timeout for icmp_seq 41
Request timeout for icmp_seq 42
Request timeout for icmp_seq 43
64 bytes from 10.0.0.1: icmp_seq=41 ttl=64 time=3597.974 ms
64 bytes from 10.0.0.1: icmp_seq=42 ttl=64 time=2926.867 ms
64 bytes from 10.0.0.1: icmp_seq=43 ttl=64 time=1972.007 ms
Request timeout for icmp_seq 47
Request timeout for icmp_seq 48
64 bytes from 10.0.0.1: icmp_seq=49 ttl=64 time=70.251 ms
Request timeout for icmp_seq 50
64 bytes from 10.0.0.1: icmp_seq=50 ttl=64 time=1234.359 ms
64 bytes from 10.0.0.1: icmp_seq=52 ttl=64 time=343.502 ms
64 bytes from 10.0.0.1: icmp_seq=53 ttl=64 time=5.607 ms
64 bytes from 10.0.0.1: icmp_seq=54 ttl=64 time=250.506 ms
64 bytes from 10.0.0.1: icmp_seq=55 ttl=64 time=10.574 ms
64 bytes from 10.0.0.1: icmp_seq=56 ttl=64 time=46.056 ms
64 bytes from 10.0.0.1: icmp_seq=57 ttl=64 time=36.372 ms
64 bytes from 10.0.0.1: icmp_seq=58 ttl=64 time=77.407 ms
64 bytes from 10.0.0.1: icmp_seq=59 ttl=64 time=106.047 ms- FURRYe38Oct 10, 2021Guru - Experienced User
Please visit and post about this in the 8 series v16 forum thread:
This thread is regarding the RBK750 Series - Firmware Update v4.6.3.7 which is now superceded by v14 for the 7 series Orbi.
Thank you.
gthi wrote:
This is what happens when you ping rhe router during wifi drop outs.
Firmware Version
V4.6.3.16_2.0.51Time out and respons at the same time...
This is definitely a routing problem and has nothing to do with coverage.
I will return the whole 1800 euro system in te next couple of days dor a refund.
Good bye Netgear