NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
George63
May 10, 2020Tutor
RBK853 issues with: activity log, 2.4Ghz backhaul & poor wifi
Does anyone else have these issues: 1. on satellites status 2.4Ghz for backhaul is grayed out (picture attached) 2. poor wifi speeds while using 2.4Ghz (less that 10mbs) 3. the activity log i...
George63
May 10, 2020Tutor
Factory reset done using web GUI : Revert to Factory Default Settings -> Erase
The distance between the router and satellite(s) is about 25-30 feet. I had ORI RBK50 and ORBI SRK60 installed in same positions and I know that the distance or building materials are not the problem. The slow wi-fi on 2.4Ghz could be fixed with a new firmware: if a 5Ghz capable device will connect to 2.4Ghz then the router should push it to 5Ghz
"Usually means that you don't have any 2.4Ghz clients connected to the RBS thus the RBS will not use 2.4Ghz until something needs that radio..." . I don`t agree with you: look again at the screenshot taken from RBS850 (pic1), you can see that 2.4G is already used by IOT devices, only the backhaul 2.4Ghz is grey. I`m attaching a screenshot taken from RBS50 (pic2) as reference: backhaul 2.4Ghz is not grey.
FURRYe38
May 10, 2020Guru
Confirmed. Mines doing the same. Wow. Guess someone missed this. Even with 2.4Ghz clients connected, the 2.4Ghz link icon is grayed out. Someone wanna make contact with NG support?
- George63May 10, 2020Tutor
Thank you for confirming this issues regarding 2.4Ghz backhaul.
BTW from previous experiences with Netgear support I`ve learned that it`s a waste of time trying to solve “software” issues.Is your log activity normal?
- FURRYe38May 10, 2020Guru
Yes.
I'll see if I can get this submitted.
Do you see any changes in the icon or logging if you revert back to v3.2.9.2 on the RBR and RBS?
- George63May 10, 2020Tutor
I got ORBI RBK853 about two weeks ago and from factory firmware V3.2.8.5_1.2.3 was installed. I kept that firmware for a few hours when I noticed the logging issue and wi-fi disconnects. I don`t recall checking the backhaul status on satellites…
After upgrading to 3.2.10.11 I saw the 2.4Ghz backhaul greyed out and same log issues and wi-fi disconnects. I manually installed 3.2.11.2_1.2.13 and no joy: the 2.4Ghz backhaul is still grey, the log is still broken and my IOT & cctv cams using 2.4Ghz are still disconnecting randomly.
I just don`t have the time and will to test older firmwares. I lost to much time on research in the past with RBK50 & SRK60…. For the price of 1,200USD (975 pounds in uk) I was expecting a flawless product. I will keep RBK853 for another 2-3 weeks and if Negear won`t fix those problems then I will return it back to amazon.uk
- TuckerReviewerMay 11, 2020Guide
This is actually normal behavior - the 2.4GHz or 5GHz channel from the router to the satellite indicates whether it is using 2.4GHz or 5GHz backhaul - 5GHz is normal and expected, 2.4GHz should be greyed out unless you have them quite far apart. That is my experience on previous firmware, I don't have this latest version installed yet - but I have never seen it show both channels active betwen the router and the satellite.
If you have them connected wired, both will be greyed out.
The 2.4 GHz devices are communicating over 2.4GHz to the satellite, but there is no reason to stick to those limited bandwidthcongested channels to forward the packets back to the router.
Which still says nothing about the other issues being mentioned in the thread, just wanted to comment on that piece.
FURRYe38 wrote:Confirmed. Mines doing the same. Wow. Guess someone missed this. Even with 2.4Ghz clients connected, the 2.4Ghz link icon is grayed out. Someone wanna make contact with NG support?
- George63May 11, 2020Tutor
- TuckerReviewerMay 11, 2020Guide
I did see the two pictures, and I see the double blue for the older Orbis. But the RBK850s have never shown that for me, it has always been only one side (bottom, 5GHz) showing blue - or none if wired. That was across multiple versions of the firmware, and I assumed it was by design.
If it is a bug, it has been around since I have had this router. Or I have an ongoing issue that I was not aware of.