NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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 is not showing any dos attacks/scans and the logs received by e-mail from RBR850 looks like this:
[DHCP IP: (192.168.0.25)] to MAC address (redacted), May 10,2020 04:31:55
[DHCP IP: (192.168.0.27)] to MAC address (redacted), May 10,2020 04:30:33
Thursday, Jan 01,1970 00:00:00
Thursday, Jan 01,1970 00:00:00
Thursday, Jan 01,1970 00:00:00
Thursday, Jan 01,1970 00:00:00
Thursday, Jan 01,1970 00:00:00
Thursday, Jan 01,1970 00:00:00
My Setup 1 Gb ONT > Orbi RBK853 V3.2.11.2_1.2.13 (Router Mode) , 20/40Mhz Coexistence disabled, CTS/RTS set to 2347
29 Replies
Has a factory reset and setup from scratch been performed since last FW update?
What is the distance between the router and satellite(s)? 30 feet is recommended in between RBR and RBS to begin with depending upon building materials when wirelessly connected. https://kb.netgear.com/000036466/How-far-should-I-place-my-Orbi-satellite-from-my-Orbi-routerUsually 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...
What are the IP addresses of .25 and .27?
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.
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?
George63 wrote:Does anyone else have these issues:
1. on satellites status 2.4Ghz for backhaul is grayed out (picture attached)My 3 satellites each display like this. It seems to be a static graphic where the gray 2.4Ghz doesn't mean anything.
Do you have any 2.4Ghz only devices connected to any of the RBS?
Mikey94025 wrote:
My 3 satellites each display like this. It seems to be a static graphic where the gray 2.4Ghz doesn't mean anything.
"What are the IP addresses of .25 and .27?" Not relevant for activity logs... the full logs received by e-mail have 230 entries and only the first 36 entries are correct, the rest of 194 entries are: “Thursday, Jan 01,1970 00:00:00” (see pic3). I`ve seen this problem before on SRR60 about a year ago, and it was fixed with a new firmware. I`m just curious if anyone else noticed that the log is broken and there`s no activity logged like dos attacks/scans
Yup, It's doing it too on both satellites and of the hundreds of logs I get eMailed to me daily, many look just like yours. The RBR shows that after its rebooted itself and devices are jumping back on and getting their IPA RESs. The "Uptime" on the RBR matches the when those events in the logs happened. But the RBSs show that they have been up and running, where I can get a Uptime of the system from them. Also when this happens there will be an RBR DeBug log waiting to be downloaded, but not from the RBSs. I have many 2.4GHz Devices connected to all APs.
I can remember that being green at one time in the early says. Or it was another device. So much has happened in such little time. But when the green went away, I gave it no mind and through that NG botched some code in the UI display, which there is a lot, WHICH was not of importance at the time for me.
So y'all aren't going "Nutz" and I see no need to get "Furry" about it. Unless it is physically impeding operation. That's the way that I look at it.
RBS and RBR both have debug log and uptime information under IP address/debug.htm
FarmerBob1 wrote:Yup, It's doing it too on both satellites and of the hundreds of logs I get eMailed to me daily, many look just like yours. The RBR shows that after its rebooted itself and devices are jumping back on and getting their IPA RESs. The "Uptime" on the RBR matches the when those events in the logs happened. But the RBSs show that they have been up and running, where I can get a Uptime of the system from them. Also when this happens there will be an RBR DeBug log waiting to be downloaded, but not from the RBSs. I have many 2.4GHz Devices connected to all APs.
I can remember that being green at one time in the early says. Or it was another device. So much has happened in such little time. But when the green went away, I gave it no mind and through that NG botched some code in the UI display, which there is a lot, WHICH was not of importance at the time for me.
So y'all aren't going "Nutz" and I see no need to get "Furry" about it. Unless it is physically impeding operation. That's the way that I look at it.
