NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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...
"" Using older config files from older versions of FW could cause problems with new versions of FW. ""
No - this is called a DEFECT. Software should be able to determine and parse older config files and correctly use them to update the current configuration. Anything less is laziness on the engineering team.
Posting to update that speed IS NOT capped on the CBK40 system using current FW builds of this date.
These results are with a Mac Book Pro ethernet connected behind a RBS20 v2.7.3.22 that is wirelessly connected to the CBR40 running v2.3.5.12. The system was factory reset and setup from scratch. NO saved backup configurations applied:
Saw no limiting or capping while connected at the RBS20. RBS and CBR40 ran well. I even connected my xbox to the RBS and gamed a couple of night. Saw no issues here.
If the user is using old configuration from prior version of FW, then there could be a problem with using older backups with newer versions of FW. Something NG will have to look into.
To resolve the users current problem, a factory reset and setup from scratch WITHOUT using ANY prior saved backup configurations from file will need to be performed then a NEW backup configuration created on this version of FW. Factory resets are a typical and general troubleshooting step which does help resolve these problems. Something I've seen many times.
The CBK40 system is not defective.
CBR IPAddress/debug.htm
I would avoid using channel 3. Channels 1, 6 or 11 are primary channels to use on the CBR for 2.4Ghz.
I'm thinking since the CBRs FW version is v.2.3x and the RBS is v2.7x, there maybe some inconstancies being experiences. From what I know for historical information and experiences, the RBS FW should be on same level as the CBRs. There maybe major changes down in the drivers between v2.3x and v2.7x so this maybe one area that's causing problems. I've asked NG to look at this as well.
I also factory reset my entire system and setup from scratch and did not load any saved config from file. Again, asked NG to look into this as well.
All I can do. This is in NG ball park now.
Sorry - no Orbi debug page on my kit. Can you be very specific what the URL is you are showing?
And according to my RBS and CBR status screens -- I have only ONE 2.4GHz channel working. Odd that the CBR and RBS do not agree on the bandwidth: CBR says 300M, RBS says 400M. Great software consistency.
FYI, this issue has been re-submitted to NG for review.
In mean time, you'll need to factory reset and setup from scratch and walk thru the setup wizard and be sure to set the setup wizard re-add the RBS20 to the system, then complete the setup wizard to regain the speed seen behind the RBS20. Do not change the transmit power on the CBR40 or you'll see the problem again.
The first picture is taken from the CBRs Connected Clients page. The 2nd picture is from the RBS web page. The 3rd picture is from the CBRs debug page. All of these are standard across Orbi systems.
Your pages are different than my pages ...
Those screen are taken from the RBS web page and the RBS debug page. All RBS and orbi systems have this info.
My system is circa 2017.
As you can see, my CBK42 is showing only one 2.4 channel, not 2 like your is, and that was after a full factory reset.
Also -- how did you get to an RBS20 screen that shows CPU loading. I have no such display on mine. You must have a newer hardware version.
The display seen for 2.4Ghz is for what Primary and Secondary channels that 2.4Ghz radios use. This is wifi and common standard operation and display. I've always see this on UIs. Nothing new here. No special app or modifications used here at all. MS EDGE web browser.
Again, systems is working as expected and proves it works fine when the configuration IS clean and NOT using a old backup configuration from file.
We've let NG know about your backwards configuration problem. However I've seen MANY other router mfr with same problem. Mfrs add new stuff to FW making OLDER backups incompatible. Factory rest and setup from scratch is needed to generate a new and compatible backup file that works with newer FW. This issue isn't new and is seen across the router industry for years. I personally never use older backups with new FW. I would agree, backups should work however if QA and testing isn't being done properly, then thats on NG side of things. No idea what goes on, on that side of the fence. I was a dev myself.
Im out. Will let NG handle this from here on out.
Good Luck.Furry - your test doesn't prove anything of the sort. It only shows your system with your configuration is working.
Try setting 2.4GHz power to LOW; and see if the backhaul is still working.
ps: I have never seen my RBS20 running with two 2.4G channels shown. Not sure how you got there unless you have some special app that can adjust things not in the usual UI.
pps: any software that isn't backwards compatible with configs is defective. Ask any professional software team that actually develops code. I was product manager of engineering software for a decade - and can pretty much assure you if a customer of mine said the configs broke between versions we'd be in a heap of trouble.