NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
New - RBR750 / RBS750 Firmware Version 4.6.5.14 Released
Enhancements:
Adds support for the RBS350
Security Fixes:
Fixes security vulnerabilities.
For more information about security vulnerabilities, visit https://www.netgear.com/about/secu...
WOW, this morning about 2am i decided to update my two ORBI RBS satillites first. and that went ok, till a fantom ORBI showed up in my Orbi App. i then proceeded to update the RBR750, that went well till it said it was online but it wasnt. i followed the directions according to Furrye38, (ty) and i unplugged the sats and then the router, waited 2-3 minutes then i plugged in the router and then the sats and waited........it took a few minutes and the router came online then the sats followed. it still took some time for all my devices to get back on line (about 60), which is normal thing that has been happening. then today was the test. we had some heavy thunderstorms roll in, these south florida storms alway knock out some power or damages some weak transformers to were the power goes on and off real quick. it happened 3 times in a half hour i also have the comcast modem and the RBR750 plugged into a surge and battery back up. the weakest like here is the sats, no battery-back up for them and they used to take forever to re-sync but after the upgraded firmware last night, WOW, the ORBI's came right back online which shocked me, i thought i would need to reboot the sats. but no input from me and the whole system came back online quick. i am no IT guy here but this is a major inprovement from the previous firmware that almost killed the ORBI system. thanks to all here on this forum, i have learned alot from here.
FURRYe38
Are you seriously suggesting to allocate fixed IP to every single device on the network!? That's crazy!! What does this resolve?
What's the logic for turning ofd AX for 2.4Ghz? Doesn't that mean devices capable of connecting using AX won't be able to do it anymore? Sounds like a degradation to me.
Are you seriously suggesting to allocate fixed IP to every single device on the network!? That's crazy!! What does this resolve?
What's the logic for turning ofd AX for 2.4Ghz? Doesn't that mean devices capable of connecting using AX won't be able to do it anymore? Sounds like a degradation to me.
Setting IPs for each connected device is not such a crazy idea. I did this on my own network (around 40 devices) and was a bit of a pain initially but it makes it easier to know what devices are doing what on a network. Since the host-name isn't always visible knowing by IP makes things easier. That said, you shouldn't have to and its not a solution. I also don't do this on the Orbi. I disabled the router and put a separate router in place because the Orbi is a pretty mediocre router especially for the price. It doesn't support DHCP option 61 (though the RBK50 did so not sure why that was taken away) and it doesn't do any QoS which meant I got a lot of buffering and ping issues in games.
Turning off AX is not a solution either, although I'm not entirely sure its that useful of 2.4ghz anyway (caveat that I'm no network expert so maybe there is a good use for it). However if there is a bug in the firmware it could well cause an issue with satellites disconnecting if they are using that. When I look at network diagnostic tools despite having my backhaul over 5ghz, there are still backhaul for 2.4Ghz there too, I guess as a failover. The RBK50 did not do this. Turning if off might help, but you shouldn't need to.
The other suggestion of changing the CTS setting is essentially disabling the RTS/CTS feature by specifying a frame size that won't ever be higher. I'm not really an expert here, but having RTS/CTS should theoretically give a more stable network with a minor cost in performance. Again though it shouldn't be causing the issues it does, but it is definitely possible a bug lies in netgears implementation of it.
What is frustrating is these tips have been known and mentioned throughout this thread, for the best part of 6 months. If those are the fix, I'm at a loss to understand why we are waiting so long for a genuine fix.