RBK750 Series - Firmware Update v4.6.3.7

[Jlhardwick]

---

I have on migrated devices back yet. Waiting to make sure the changes I made work and it does not upgrade it's self.

Will report back after a day or so and I migrate if it does not update.

@FURRYe38 wrote:

Glad it worked. 

How is your system working now? 

---

@Jlhardwick wrote:

So I finally downgraded the firmware successfully on Router and Satellite.

I also discovered if you are willing to risk leaving telnet active that after you downgrade to V3.2.10.10 active telnet so you can disable the auto update, you can upgrade to the last V3 firmware before this all went to hell and still have telnet work. Unfortunately I see no way to turn it back off but will to take that risk until Netgear finally fixes this total failure with Firmware V4

---

---

[titaniumrx8]

@Theobuck

Netgear has their hands full these days. Google Netgear and Disney. Major fubar.

They're also in deep with their commercial grade products.

I get the feeling that Orbi is at the tail end of the support and development triage that they're facing.

[titaniumrx8]

For everyone who would like netgear to stop forced firmware updates, please kudo and comment in this discussion:
https://community.netgear.com/t5/Idea-Exchange-For-Home/Stop-unscheduled-firmware-updates-in-Orbi-AX...

[Jlhardwick]

---

Latest update:

While I was able to upgrade to the last V3 firmware I question what will happen after a day or too. The interface knows that a newer firmware is available for router but not for satellite. Checking NVRAM still shows that it will not automatically update. Time will tell.

@Jlhardwick wrote:

---

I have on migrated devices back yet. Waiting to make sure the changes I made work and it does not upgrade it's self.

Will report back after a day or so and I migrate if it does not update.

@FURRYe38 wrote:

Glad it worked. 

How is your system working now? 

---

@Jlhardwick wrote:

So I finally downgraded the firmware successfully on Router and Satellite.

I also discovered if you are willing to risk leaving telnet active that after you downgrade to V3.2.10.10 active telnet so you can disable the auto update, you can upgrade to the last V3 firmware before this all went to hell and still have telnet work. Unfortunately I see no way to turn it back off but will to take that risk until Netgear finally fixes this total failure with Firmware V4

---

---

---

[FURRYe38]

and your on V10 and did the telnet configuration? 

---

@Jlhardwick wrote:

---

Latest update:

While I was able to upgrade to the last V3 firmware I question what will happen after a day or too. The interface knows that a newer firmware is available for router but not for satellite. Checking NVRAM still shows that it will not automatically update. Time will tell.

@Jlhardwick wrote:

---

I have on migrated devices back yet. Waiting to make sure the changes I made work and it does not upgrade it's self.

Will report back after a day or so and I migrate if it does not update.

@FURRYe38 wrote:

Glad it worked. 

How is your system working now? 

---

@Jlhardwick wrote:

So I finally downgraded the firmware successfully on Router and Satellite.

I also discovered if you are willing to risk leaving telnet active that after you downgrade to V3.2.10.10 active telnet so you can disable the auto update, you can upgrade to the last V3 firmware before this all went to hell and still have telnet work. Unfortunately I see no way to turn it back off but will to take that risk until Netgear finally fixes this total failure with Firmware V4

---

---

---

---

[Jlhardwick]

---

Started with V3.2.10.10 to enable telnet then upgraded to V3.2.18.1 which was the last v3 before v4 destroyed my router.

@FURRYe38 wrote:

and your on V10 and did the telnet configuration? 

---

@Jlhardwick wrote:

---

Latest update:

While I was able to upgrade to the last V3 firmware I question what will happen after a day or too. The interface knows that a newer firmware is available for router but not for satellite. Checking NVRAM still shows that it will not automatically update. Time will tell.

@Jlhardwick wrote:

---

I have on migrated devices back yet. Waiting to make sure the changes I made work and it does not upgrade it's self.

Will report back after a day or so and I migrate if it does not update.

@FURRYe38 wrote:

Glad it worked. 

How is your system working now? 

---

@Jlhardwick wrote:

So I finally downgraded the firmware successfully on Router and Satellite.

I also discovered if you are willing to risk leaving telnet active that after you downgrade to V3.2.10.10 active telnet so you can disable the auto update, you can upgrade to the last V3 firmware before this all went to hell and still have telnet work. Unfortunately I see no way to turn it back off but will to take that risk until Netgear finally fixes this total failure with Firmware V4

---

---

---

---

---

[FURRYe38]

Ok, let us know how it goes. 

I contacted ther user who posted how to downgrade the RBR and his is working fine. 

---

@Jlhardwick wrote:

---

Started with V3.2.10.10 to enable telnet then upgraded to V3.2.18.1 which was the last v3 before v4 destroyed my router.

@FURRYe38 wrote:

and your on V10 and did the telnet configuration? 

---

@Jlhardwick wrote:

---

Latest update:

While I was able to upgrade to the last V3 firmware I question what will happen after a day or too. The interface knows that a newer firmware is available for router but not for satellite. Checking NVRAM still shows that it will not automatically update. Time will tell.

@Jlhardwick wrote:

---

I have on migrated devices back yet. Waiting to make sure the changes I made work and it does not upgrade it's self.

Will report back after a day or so and I migrate if it does not update.

@FURRYe38 wrote:

Glad it worked. 

How is your system working now? 

---

@Jlhardwick wrote:

So I finally downgraded the firmware successfully on Router and Satellite.

I also discovered if you are willing to risk leaving telnet active that after you downgrade to V3.2.10.10 active telnet so you can disable the auto update, you can upgrade to the last V3 firmware before this all went to hell and still have telnet work. Unfortunately I see no way to turn it back off but will to take that risk until Netgear finally fixes this total failure with Firmware V4

---

---

---

---

---

---

[Jlhardwick]

Ok, so updating to the last V3 version did not work. Despite double checking the NVRAM settings the RBR updated to V4 last night. The RBS is still holding at V3. Guess I start again and stick with the first V3 since it has been proven to work.

[FURRYe38]

I presume the last v3 over wrote something that v10 seems to keep stable. 

---

@Jlhardwick wrote:

Ok, so updating to the last V3 version did not work. Despite double checking the NVRAM settings the RBR updated to V4 last night. The RBS is still holding at V3. Guess I start again and stick with the first V3 since it has been proven to work.

---

[CH-Syd]

Thanks FURRYe38 for your instructions. I'm in IT so probably would not recommend for soemone not tech savy to perform. Pretty rubbish and I feel for people struggling with recent upgrades.

I have a RBR850/RBS850 and the only firmware version that still has the telnet option is RBS850-V3.2.10.11_1.2.12. I have downgraded and blocked upgrade sites. All seemed to go as per instructions. 

It does concern me that by stopping updates we may leave ourselves vulnerable by not updating firmware. However, Netgear have done such an disgraceful job in the v4.6 update, what option do we have. 

It appears now and with downgrading, I now have internet speeds to what I had before (200-240Mbps). 

I've also reinstated my secondary wifi network (not Orbi which works and is now backup), compared speeds and they are the same. Tested from 4 different devices. 

I'll run with this for now but likely to move off this expensive rubbish product to something better. It sh!ts me to have to waste good money on rubbish infrastructure!

Likely move to a business grade kit for home network, such as Meraki or Ubiquiti.

Good luck everyone.

BTW - does anyone know the billing department details for Netgear, invoice them for lost earnings?

[Thalador]

---

@Xcelebric wrote:

Here is the latest update from my trying:

.....

10, I will monitor for a day or so to see if this works. 

---

@Xcelebric 

Thank you for this info. Since Netgear won't fix this I wanted to thank you for doing what they couldn't. My system was rebooting multiple times a day and I just finsihed downgrading it. Not easy, but nothing with NG is. I did have 2 questions 

1. I assume I cannot import my saved config from a higher version is that correct?
2. Is 3.2.10.10 the version you are sticking with? I had considered upgrading to the 2nd latest 3.x version that seemed to work well for me, but I thought maybe it would allow the auto update to happen again. Thoughts?

Thanks again for all your hard work on this fiasco!

[FURRYe38]

---

@Thalador 

Thank you for this info. Since Netgear won't fix this I wanted to thank you for doing what they couldn't. My system was rebooting multiple times a day and I just finsihed downgrading it. Not easy, but nothing with NG is. I did have 2 questions 

1. I assume I cannot import my saved config from a higher version is that correct? Coirrect. 
2. Is 3.2.10.10 the version you are sticking with? I had considered upgrading to the 2nd latest 3.x version that seemed to work well for me, but I thought maybe it would allow the auto update to happen again. Thoughts? v10 was the last version of FW  that had telnet support. All others stopped supporting telnet so if you update to something past v10, your telnet modifications to block the autoupdate will no longer work. 

---

[gthi]

In order to prevent the router and satelites to auto update:

in Advanced Security, I blocked 2 sites in the firewall:

www.updates1.netgear.com

updates1.netgear.com

Now the router is unable to download the FW update as you can see in the log files:

[site blocked: www.updates1.netgear.com] from source 192.168.2.5 Thursday, Oct 07,2021 12:54:26

Auto update is impossible now!

Personally I managed to roll back to Firmware Version V4.6.3.9_2.0.50

Keep my fingers crossed the WiFi network is stable now

At the same I invested EUR 1800 in a high end wifi system finding myself in this situation. Pretty scandalous Netgear!

[Phil_T_AU]

After multiple issues, I just returned my 4 week old orbi system to the place I bought it for a refund. Disappointing that such a premium priced orbi doesn't give stable trouble free wi-fi. I bought an ASUS mesh system now and it's been flawless...

[FURRYe38]

FW v7 is now old and not used anymore. There is more recent FW version for Orbi 7 series. 

Good Luck. 

[FURRYe38 · Accepted solution]

https://community.netgear.com/t5/Orbi-WiFi-6/New-RBR750-RBS750-Firmware-Version-4-6-5-14-Released/m-...

[Donsuper]

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.

[Thalador]

---

@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.

[FURRYe38]

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.

---

[gthi]

This is what happens when you ping rhe router during wifi drop outs.

Firmware Version
V4.6.3.16_2.0.51

Time 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

[FURRYe38]

Please visit and post about this in the 8 series v16 forum thread:

https://community.netgear.com/t5/Orbi-WiFi-6/New-RBR850-RBS850-Firmware-Version-4-6-3-16-Released/td...

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.51

Time 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

[TimCakir]

Thanks Ive done all your steps about downgrading to v3 and all the blocking + the telnet. the telnet for me was super difficult on mac but I have achieved that with brew. Let's see if my system is back to what it was it was super solid for about 8-9 months, I hope Im going to be back on that rock solid mesh I had. Thanks again, it took me couple of hours but if it works, its worth it!

[FURRYe38]

👍

I use ZoC on Mac. 

[jamacphoto]

So any tips for mac as might try it Sunday as so miss. The set up as the wifi speeds so much quicker

[ddkumar]

Looks like new firmware v4.6.5.14 is released. It was not pushed to my Orbi 7xx, but it was shown as available as an online update. No data yet on whether it fixes my issues, but the release notes claim it is supposed to address them.