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 wrote:Bug Fixes:
- Fixes issue where the satellite LED continuously switches between white, blue, and off state.
- Fixes some stability and connectivity issues.
- Fixes other various bugs.
First, glad to see that NG is trying to resolve these issues, albeit with little transparency. Although the number of firmware updates in so little time is fairly telling... I have to chuckle at calling out "Fixes issue where the satelltie LED continuously ...", surely this wasn't the title of the bug being tracked internally, was the fix to just disable the LED, LOL? This came at a good time, when everybody needs it, and on the weekend when we all can kick the family off the WiFi, maybe... I'll be testing this out ASAP, even if it means wasting another Saturday...
Most helpful, as always. Any sight to equiavalent update for RBR850 series? Can this be used for the RBR850 as well given it's all the same issues?
Really appreciated, @FURRYe38 - I have read dozens of your posts over too many issues and you've always brought practical guidance and usually resolution.
orbiuser1975 wrote:First, glad to see that NG is trying to resolve these issues, albeit with little transparency. Although the number of firmware updates in so little time is fairly telling... I have to chuckle at calling out "Fixes issue where the satelltie LED continuously ...", surely this wasn't the title of the bug being tracked internally, was the fix to just disable the LED, LOL? This came at a good time, when everybody needs it, and on the weekend when we all can kick the family off the WiFi, maybe... I'll be testing this out ASAP, even if it means wasting another Saturday...
Initial (working) setup with v3 in router mode:
FiOS -> RBR750 -> unmanaged switch -> RBS750
Current setup with v4.6.5.14 in AP mode:
FiOS -> pfSense -> RBR750 -> unmanaged switch -> RBS750
Since this mess started, I was forced to change my primary router (RBR750) to something else (pfSense). Per this, I'm now operating in AP mode, so my findings are for AP mode only.
After initial upgrade and with the RBS750 in the same room (optimal) about 25 ft away, the backhaul connection reported as 5 GHz initially and then randomly changed to 2.4 GHz. I then moved the satellite to other side of the house (original location) and the the backhaul connection reports 2.4 GHz, appears to be working (need more time), but the LED will still randomly go through cycles of blinking white and ending on amber all while the web interface reports that the connection is "Good" @ 2.4 GHz.
I then tried to go back to the original "wired" backhaul, and the satellite is no longer seen by the router. The satellite is on the network as I can reach its admin page showing the following.
It appears that some things have been fixed, but allowing a backhaul connection through an unmanaged switch is certainly still broken. The LED cycling on the sattelite is still occuring, but the connection seems to work during these cycles. There is a new annoying issue, the connection to the RBR750 admin page times out, requiring frequent logins.
How was your system updated?
Did you power OFF the RBR and RBS for 5 minutes then back ON after v14 was applied.
Does the RBS appear connected to the RBR while ethernet connected to the back the RBR with out the unmanaged swtich?
What was the brand and model# of this 'unmanaged' switch again?
Id do a full factory reset on the RBR and RBS if nothing else resolves this...
orbiuser1975 wrote:
orbiuser1975 wrote:
First, glad to see that NG is trying to resolve these issues, albeit with little transparency. Although the number of firmware updates in so little time is fairly telling... I have to chuckle at calling out "Fixes issue where the satelltie LED continuously ...", surely this wasn't the title of the bug being tracked internally, was the fix to just disable the LED, LOL? This came at a good time, when everybody needs it, and on the weekend when we all can kick the family off the WiFi, maybe... I'll be testing this out ASAP, even if it means wasting another Saturday...
Initial (working) setup with v3 in router mode:
FiOS -> RBR750 -> unmanaged switch -> RBS750
Current setup with v4.6.5.14 in AP mode:
FiOS -> pfSense -> RBR750 -> unmanaged switch -> RBS750
Since this mess started, I was forced to change my primary router (RBR750) to something else (pfSense). Per this, I'm now operating in AP mode, so my findings are for AP mode only.
After initial upgrade and with the RBS750 in the same room (optimal) about 25 ft away, the backhaul connection reported as 5 GHz initially and then randomly changed to 2.4 GHz. I then moved the satellite to other side of the house (original location) and the the backhaul connection reports 2.4 GHz, appears to be working (need more time), but the LED will still randomly go through cycles of blinking white and ending on amber all while the web interface reports that the connection is "Good" @ 2.4 GHz.
I then tried to go back to the original "wired" backhaul, and the satellite is no longer seen by the router. The satellite is on the network as I can reach its admin page showing the following.
It appears that some things have been fixed, but allowing a backhaul connection through an unmanaged switch is certainly still broken. The LED cycling on the sattelite is still occuring, but the connection seems to work during these cycles. There is a new annoying issue, the connection to the RBR750 admin page times out, requiring frequent logins.
FURRYe38 wrote:How was your system updated?
Did you power OFF the RBR and RBS for 5 minutes then back ON after v14 was applied.
Does the RBS appear connected to the RBR while ethernet connected to the back the RBR with out the unmanaged swtich?
What was the brand and model# of this 'unmanaged' switch again?
Id do a full factory reset on the RBR and RBS if nothing else resolves this...
FURRYe38 Thanks for the suggestions.
It was updated via the web interface Advanced -> Administration -> Firmware Update -> Online Update "UpdateAll" (noting the missing space...).
Yes, both RBR and RBS were turned off for more than 5 minutes, the RBS turned on first for at least 10 minutes, followed by the RBS.
I didn't test connecting the RBS and RBS directly, as that had worked in the past as advertised by NG, but ultimately doesn't help me as the final (and original) install won't be able to use a direct cable. I expect it does work, but again not helpful.
The unmanaged switch is a TrendNet TEG-S16Dg, the same switch that was in the mix with v3 that worked. I have a couple of NG 5 and 8 port switches that I'll try and see if it matters.
I haven't done a complete factory reset yet, but will take that under advisement. I hope if NG is going to continue forcing updates, they ensure that a factory reset isn't required...
