NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
GWild
Jan 16, 2022Guide
Firmware upgrade capped satellite bandwidth at 50Mbps
Checked for firmware update via Orbi web interface, showed everything current. Visited Netgear CBK40 download page, showed new firmware for the RBS20 (two newer versions). Both updates related to se...
GWild
Jan 16, 2022Guide
I can add that the router/satellite link is now reporting it is in CONFIG SYNC ... where it use to say GOOD.
Seems there are many reports of the backhaul sync status getting messed up, and no clear way to resolve the issue once it happens.
FURRYe38
Jan 16, 2022Guru - Experienced User
Any thing releated to this?
- GWildJan 16, 2022Guide
Other than horrid Netgear Software Quality controls, probably something they introduced when trying to fix the DNS bug.
After a dozen resets, resyncs, and power cycles with and without 1000bT wires connected to the slave, and reloading the CBR40 setup from a few days ago, the slave finally reconnected and created a working backhaul. In other words, it is a random event that allows it to work.
I am reluctant to do a test power cycle or reboot... I just don't feel like screaming right now.
- FURRYe38Jan 17, 2022Guru - Experienced User
Well FYI, worked with NG support and enginnering last year on this and even sent me a new RBS, problem still happens and I believe its a CBR issue in FW. I reverted back to first version of FW on both CBR and RBS and the problem didn't reproduce. I sent NG all the debug logs and such. I'll reach out again and see what happened to our troubleshooting event from last year.
- GWildJan 18, 2022Guide
I had only updated the satellite firmware. CBR was unchanged. So I seriously doubt it is a router issue.
I also tried a direct downrev back to known working firmware. Problem remained. I then moved back to the latest patch and kept trying things until random events got it to work again.
My guess is just poor coding practices with some uninitialized variables that get trashed with the new firmware. Stack overflow, pointer errors, etc. Until Netgear takes the time to do a QC pass on their code the issue will remain. Lord knows what new "features" they have introduced with this most recent "bug fix."
I'm probably going to revert back to the RBS firmware I had been using - at least it appeared to be somewhat stable.
I can say with some certainty this was my last Netgear product - and I'll restate that my attempt back in February to install the CBK752 kit was also a disaster and was the last straw. The fact Netgear can't even keep simple firmware stable and reliable and safe means most of their products are also full of such holes and just waiting for an opportunity to fail on users.