NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
New Orbi RBR50/RBS50 Firmware Version 2.3.1.44
Netgear is pushing out yet another a new Orbi firmware update.
Hopefully it's better than the last version v32.
Please share your experience.
Firmware Update
...
Was the FW updated thru the autoupdate? If so, try a factory reset and setup from scratch on both RBR and RBS.
SkolViking wrote:
Yup several times. I even power cycle my cameras and they just go back to the main RBR50 everytime. Wonder if I can remove the satellite and re adding it will do anything ?
Got Frustrated with Verizon's recent firmware update to their Quantum router bringing up certificate errors for login and decided to take the plunge and release the DHCP lease on the Verizon router and move the Ethernet connection directly to the Orbi. ** You have to put the Orbi in Router mode first or you will kind of get stuck and have to start the process over. Otherwise, it just works.
No issues so far. 2.3.1.44 is the first release I have tried the Router mode versus AP I had been using. Performance/signal strength/speed has actually improved a bit in my limited testing.
The traffic meter seems broken now - at least in the iOS app. Doesn’t show anything since .44.
Seems to be a known issue.
Revert back to v210 if you need TM working or wait for NG to fix it.
Funtastico wrote:
The traffic meter seems broken now - at least in the iOS app. Doesn’t show anything since .44.
Good to hear. Thanks for letting us know.
Enjoy. :smileywink:
orbilov wrote:
Got Frustrated with Verizon's recent firmware update to their Quantum router bringing up certificate errors for login and decided to take the plunge and release the DHCP lease on the Verizon router and move the Ethernet connection directly to the Orbi. ** You have to put the Orbi in Router mode first or you will kind of get stuck and have to start the process over. Otherwise, it just works.
No issues so far. 2.3.1.44 is the first release I have tried the Router mode versus AP I had been using. Performance/signal strength/speed has actually improved a bit in my limited testing.
It's working for me.
Funtastico wrote:
The traffic meter seems broken now - at least in the iOS app. Doesn’t show anything since .44.
Apparently, if you uncheck the box on the NTP page for automatically adjusting for daylight saving time, the traffic meter works properly. I had the same issue, unchecked the box, and now my usage appears about what I'd expect the traffic meter to show. The only thing that really changes adversely from doing that is that your logs will all be time-stamped an hour off, since they'll be showing the time in standard time.
randomousity wrote:
Apparently, if you uncheck the box on the NTP page for automatically adjusting for daylight saving time, the traffic meter works properly. I had the same issue, unchecked the box, and now my usage appears about what I'd expect the traffic meter to show. The only thing that really changes adversely from doing that is that your logs will all be time-stamped an hour off, since they'll be showing the time in standard time.
I was one of the users who was surprised to find the Traffic Meter had quit working. Well, like the Terminator, "it's BACK." First noticed it yesterday on the Android app and confirmed it just now. And.... my Orbi observes Daylight Saving Time and my log entries have the correct time (not an hour off). If Netgear pushes a software update without changing the version number, would anyone be able to tell?
What the hell man. Orbi has been rock solid for months. Noticed random reboots today and yesterday. Sure enough, logged in a saw V2.3.1.44. was on V2.2.1.210 and everything was running smoothly.
Just tried to install V2.2.1.210 and got the error that this was NOT the right firmware for this model. Tripled check and I indeed have the RBR50 firmware. NG FAQ says in order to go from .210 to .44, we had to go to v2.2.1.212. How in the world did mine go from .210 to .44. Now, router keeps rebooting. Jesus Netgear...... you literally suck.
Manually download the RBR v44 file and re-load it on the RBR. Use IE11 or Firefox browser. After it loads and the RBR is ready, factory reset the RBR and setup from scratch.
I set this up on a RBK50 system two days ago, just got 1 satellite ethernet backhaul configured last nite. Zero problems.
bowmah wrote:
What the hell man. Orbi has been rock solid for months. Noticed random reboots today and yesterday. Sure enough, logged in a saw V2.3.1.44. was on V2.2.1.210 and everything was running smoothly.
Just tried to install V2.2.1.210 and got the error that this was NOT the right firmware for this model. Tripled check and I indeed have the RBR50 firmware. NG FAQ says in order to go from .210 to .44, we had to go to v2.2.1.212. How in the world did mine go from .210 to .44. Now, router keeps rebooting. Jesus Netgear...... you literally suck.
Yes, this is a known issue. Seems to have come in on v32 we think. NG is aware of it.
randomousity wrote:
Apparently, if you uncheck the box on the NTP page for automatically adjusting for daylight saving time, the traffic meter works properly. I had the same issue, unchecked the box, and now my usage appears about what I'd expect the traffic meter to show. The only thing that really changes adversely from doing that is that your logs will all be time-stamped an hour off, since they'll be showing the time in standard time.
Yeah, I had assumed the time would be an hour off during standard time, but I was wrong. I looked last night, myself. So, given that the Orbi shows the correct time without the box checked, I'm not really sure what the point of the box is in the first place? Maybe not all time servers automatically adjust between DT and ST? But it's definitely true that the box causes the traffic meter to not display properly (though the usage is, apparently, logged properly, either way, and it's only a display issue triggered by checking the box).
I think if Netgear didn't version increment a patch, nobody would notice, but also, nobody's routers would pull the update, since they'd think the update matched their current firmware. Only people whose routers updated after the superseded patch was published, or who decided to download and manually reinstall the current firmware, would get the "new and improved" 2.3.1.44 firmware. I can't decide whether publishing a minor patch to fix this (e.g., 2.3.1.45) would be better or worse than just including it in the next major patch. On one hand, we'd know they were responsive to problems and were quickly tackling them. On the other hand, updates are a pain, and sometimes break things for no apparent reason, so maybe daily/weekly updates would be more hassle than it's worth?
At any rate, publishing new firmware with the same version number would be poor form on their part, since some people's traffic meters would work properly, and others' wouldn't, but they'd think they had the same version firmware when, in fact, they only nominally did. Troubleshooting would be a mess, even just for the traffic meter, never mind if anything else were changed and not documented.
CrimpOn wrote:
randomousity wrote:
Apparently, if you uncheck the box on the NTP page for automatically adjusting for daylight saving time, the traffic meter works properly. I had the same issue, unchecked the box, and now my usage appears about what I'd expect the traffic meter to show. The only thing that really changes adversely from doing that is that your logs will all be time-stamped an hour off, since they'll be showing the time in standard time.
I was one of the users who was surprised to find the Traffic Meter had quit working. Well, like the Terminator, "it's BACK." First noticed it yesterday on the Android app and confirmed it just now. And.... my Orbi observes Daylight Saving Time and my log entries have the correct time (not an hour off). If Netgear pushes a software update without changing the version number, would anyone be able to tell?
Yep this!! Not getting reboots but connection keeps dropping off. So pi$$ed off!!!
This firmware is amateur garbage. Incredibly poor quality control forced on customers by Netgear. Destroyed my network and costing me money. And no reply from the moderators in this thread:
I have an RBR50, an RBS50 and an RBS30, linked with wireless backhaul.
My system auto updated to .44 and everything works fine except for wireless to wired routing.
When a device is attached to a satelite, it cannot connect to any devices that are hardwired to the router. Internet access is fine though.
I would do a full factory reset and setup from scratch. Let us now if this resolves your problem. If it doesn't, you might try reverting back to v210 on the RBR.
So far the system I have has been working well with v44 for the past 3+ days.
bym051d wrote:
I have an RBR50, an RBS50 and an RBS30, linked with wireless backhaul.
My system auto updated to .44 and everything works fine except for wireless to wired routing.
When a device is attached to a satelite, it cannot connect to any devices that are hardwired to the router. Internet access is fine though.
