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
|
|||||||||||||||||||||
| Check if a new firmware version is available on the Internet. | |||||||||||||||||||||
|
|||||||||||||||||||||
383 Replies
My Orbi/Satellites performance with v44 are almost back to normal. Download speeds from Satellites are relatively close to v210.
Wired speed (LAN) from Router is also good with v44.
If you are still on the fence and haven't tried v44, give it a shot. Be ready to invest time to deal with unexpected issues with your particular setup. It took me about 2 weeks to iron out the wrinkles in my setup. YMMV.
- All of this feedback on 44 almost makes me try it again BUT there are lots of steps and stuff to try if the easy stuff does not work!!
That could be very very time consuming and that alone is a major negative.
I am still running on 210 perfectly, matter in fact better than any other router I have ever had, that alone says a lot for 210. I am 5 days 9 hours in with 210 an no problems AND no factory default and reconfigure from scratch AND no resetting of satellite and no playing around with this or that.
I really hope my router never auto updates
BUT if it did a full actual list of steps for all would be nice instead of sifting through all these pages pulling pieces out. Like download and flash, factory default router and satellite but satellite you must default with button and how to etc.
this way others can just do all the steps up front instead of piecing it together taking up days then finding out if 44 or whatever version works for them.
If all these steps are nicely written in order them maybe even I would try 44 again, when I get time of course and no one needs internet. This way all is done up front and if it don’t work then 210 is the only way to go for them.
In the mean time 210 is my recommended way to stay, or you could be spending days trying this and that then this , etc.....
if your going to recommend 44 them please compile a list of all things to do to get there up front, this way others are not off the wall because they don’t have the current time to read all these posts and try one at a time.
For now 210 is just outstanding without all the BS one might have to try to get 44 to work and then it’s a if.
Thanks to all
I've gone ahead and done a full reboot of the Orbi network on the 10th (not a reset, as I had done the factory reset when the firmware was first applied), along with disabling auto update via telnet on both the router and the satellite. Yes, the RBS50 also needs to have its auto update function disabled. Daisychain was also disabled. If you log into the satellite's debug page, there is a ghosted setting that indicates whether daisychain is disabled or not. I made sure all wired and wireless devices were off the network during the reboot process. Because of OCD, I used address reservation to pin the RBS50 to x.2 address, although it should be said bringing up the network the way I described with no devices active will allow the satellite to grab the x.2 address on its own.
Verified the additional backhaul channel is not active using WiFi Analyzer. Here it looks like the system is using channel 157 and 161 for backhaul based on the MAC address I see, in addition to the main 44, which I changed from 48. I don't care what the 2.4GHz is doing and is set to Auto. The 5GHz channel is a bit of a challenge because my neighbor's wifi keeps stepping on mine so I move mine to be safe.
I'm in agreement with SW_ WiFi is able to run at full bandwidth.
Oh, and I did all of the testing on .44 as opposed to downgrading.
I had good operation with v44 in router and AP mode on v44. Zero issues including using a single SSID.
System Uptime 07:23:35:01 - I’m seeing this topic come up over and over again. Why run the Orbi in AP mode over native router?
- I choose AP mode because I have Verizon Fios with DVR. I had setup Orbi in router mode to simulate how the DVRs are handled, but would quite often have connection issues where a movie would just pause for not apparent reason and remotely accessing the DVR was iffy at best. Playing on demand movies was also problematic, most times it would work flawlessly, but at the seemingly wrong times it cause pixelation. So now the Verizon router handles the DVRs and dhcp. Wifi is turned off on the Verizon router and Orbi handles Wifi. In this fashion there is peace in the house when it comes to TV time...
I scratched my RBR50 and RBS50 on 3/23/19 and installed the initial release configured for no updates and blocking downloads.netgear.com. The initial release ran fine for 10 days without autoupdates and without detecting any new releases.
On 4/13 installed 2.0.0.74, the first daisy chain release and then patched that up to 2.0.1.4 fixing the memory leak. This ran nicely all day but the firmware update page was now reporting a new release available. I didn't click the new version link but did notice that orbi_auto_upgrade was changed from 0 to 42689245989537. I set it back to 0 but....
On 4/14 at oh-dark-thirty i was autoupgraded to 2.3.1.44. I did not manually install it nor did I manually install the prereq - I was hoping to stay on 2.0.0.74 and then proceed cautiously.
After disabling daisy-chain it's been fast and stable, today.
Well I can confirm the telnet blocking does not work, it works for some days them bam orbi updates. I am back on .44 from the auto update again that happened let’s say 3 days ago now. The good thing is SO far .44 is going good with no reconfigure or anything so far. This just does not make sense , 44 working that is, just by orbis auto updating, and my cameras have the same good WiFi signal. Now I ran 44, 2 times before with no success and poor WiFi speeds, with orbi updating on its own. You can’t make this stuff up, oh well now let’s see if it holds up.
I have to say this forum thread has been enlightening. I have an unopened RBK50 sitting next to me, but after reading about the various issues several people have had with the most recent firmware update, I plan on returning it. It sounds like Netgear has difficulty adequately testing and debugging their updates. The main reason I will be returning the RBK50 is that having to do a factory reset and/or downgrading to previous version(s) of firmware to resolve many/most issues is NOT my idea of how I want my wireless/wired network to operate. I want stability/reliability and performance at a minimum. It doesn't sound like Netgear is able to provide those core functions consistently across firmware update(s). When I worked in the IT field as a UNIX/Linux System Manager if I had to tell my boss(es) that it is likely that we'd have to restore the operating system and applications from scratch (i.e., "factory reset with Netgear") if say any patching operation(s) had issues, I would not likely have lasted very long in the field.
binventive wrote:
I have to say this forum thread has been enlightening. I have an unopened RBK50 sitting next to me, but after reading about the various issues several people have had with the most recent firmware update, I plan on returning it. It sounds like Netgear has difficulty adequately testing and debugging their updates. The main reason I will be returning the RBK50 is that having to do a factory reset and/or downgrading to previous version(s) of firmware to resolve many/most issues is NOT my idea of how I want my wireless/wired network to operate. I want stability/reliability and performance at a minimum. It doesn't sound like Netgear is able to provide those core functions consistently across firmware update(s). When I worked in the IT field as a UNIX/Linux System Manager if I had to tell my boss(es) that it is likely that we'd have to restore the operating system and applications from scratch (i.e., "factory reset with Netgear") if say any patching operation(s) had issues, I would not likely have lasted very long in the field.
Apples and oranges I think. Routers seem to have more of a need to be factory reset based on my limited sampling. If you believe another product does a better job of it, would be good to know, but I suspect most all of them will have forums with posts in them saying to do a factory reset at the first sign of trouble.
I had purchsed my RBK-53 from Costco last month. It was on firmware version 1.4.0.18, and would never find new updates. I had not disabled auto-updates. I began checking into updates, and found a recommendation to go to 2.0.0.74, then follow Netgear's release notes to update to 2.2.1.212 prior to the latest 2.3.1.32 or .44 updates.
I updated the satellites, then the router to 2.0.0.74. The administration page showed a small banner that a new firmware was available. I didn't think at the time to disconnect from the Internet, though I'd already downloaded all the necessary firmware packages. I then began the install on one satellite to 2.2.1.212. However, after the update on that first satellite completed, I was not able to reach the router or either satellite for a few minutes. When it finally came back online, the router and both satellites displayed 2.3.1.44.
So far, everything seems stable despite the router not following Netgear's own "required" step of going to 2.2.1.212 before the current version. I'll have to monitor and see what changes.
AlienMindBender wrote:
So far, everything seems stable despite the router not following Netgear's own "required" step of going to 2.2.1.212 before the current version. I'll have to monitor and see what changes.
The requirement to upgrade to version 212 first was directed at users who wanted to manually update Orbi firmware. When Netgear performs firmware upgrades themselves, we have no idea how many "steps" they went through. All we see is that a while ago the Orbi was on one firmware and now it is on a newer one. How they got there is invisible to us.
So I have been wondering has anyone else been getting multople Temporary IPV6 addresses on thier computers or IPV6 randomly dissapering since this update. I'm asking since I have begun noticing that on my ASUS ROG WIndows 8.1 laptop I will get multiple Temporary IPV6 adresses and the IPV6 dissaperars as well. It happens on my Desktop sometimes too though its WIndows 10 and after awhile things get back to normal. It only happens on a fresh start up.
so i am having the same issue and some of you guys. Recently purchased a refurb RBK50 unit with a satellite. At the initial setup, everything works fine, i see the satellite online and all the devices connected to it. Then when i log into the app again the next day or so the satellite shows offline. I logged into the orbi web portal and it does show that the satellite is online and even shows the devices connected to it.
Functionality wise, i can confirm that the wired devices connected to the satellite work without any issues. I also see the wireless devices connected to the satellite on the website but on the app i see them connected to the main router.
So what's going on? Should i just leave it be or get another unit? Can this issue be fixed? I am trying to figue out what my optimum (service provider) modem address is. I don't think i have access to that....anyone with Optimum online experience please chime in.
Thanks !
What Firmware is currently loaded?
What is the Mfr and model# of the ISP modem the NG router is connected too?Is the Orbi system operating in Router or AP mode?
Logging to the mobile Orbi app or the Orbis web page with a browser?
Try disabling the following and see:
Daisy Chain
Dan407 wrote:
so i am having the same issue and some of you guys. Recently purchased a refurb RBK50 unit with a satellite. At the initial setup, everything works fine, i see the satellite online and all the devices connected to it. Then when i log into the app again the next day or so the satellite shows offline. I logged into the orbi web portal and it does show that the satellite is online and even shows the devices connected to it.
Functionality wise, i can confirm that the wired devices connected to the satellite work without any issues. I also see the wireless devices connected to the satellite on the website but on the app i see them connected to the main router.
So what's going on? Should i just leave it be or get another unit? Can this issue be fixed? I am trying to figue out what my optimum (service provider) modem router is. I don't think i have access to that....anyone with Optimum online experience please chime in.
Thanks !
both devices show version 2.3.1.44 on the app.
modem is Arris TM822
Orbi is in router mode. I tried the AP mode before and all hell broke loose. I finally had to reconnect my old router to get internet access and then redid the Orbi setup.
Im loggin into both the app and website. Website shows online with connected devices. App shows offline.
Daisy chain is off
Hi,
i updated to v.48 for my RBK50. Do I have to do a factory reset even if I have done it on the previous v.44? Thanks
Zephyr3200 wrote:
Do I have to do a factory reset even if I have done it on the previous v.44?
I wouldn't.
I reserve that move for when things go wrong.
If your system sails on smoothly after the uodate, I would leave well alone.
Hi,
I have a RBR50 with one RBS50 that has been running great for 6+ months after initial setup.
I was running RBR in AP mode with default settings except for SSID.
A couple of weeks ago i noticed regular drops in WIFI connectivity (WIFI connection lost entirely) on my devices and RBS showing Magenta and then changing to Blue after some time. No indication on RBR. WIFI scanner showed that WIFI SSID was available at all times. There was no difference depending on whether or not i was connected to RBR or RBS, WIFI connection was lost on all devices.
I then noticed that i was running 2.3.1.44 so i guess i have been autoupdating without hassle since release (which is the way a premium product like this should work).
I came across this thread and started to test the different tips but nothing helped. After a number of factory resets (and after .48 was applied) i got the RBR to function when RBS was not added without disconnects. Disconnects appeared however as soon as i added the RBS no matter what settings i tried.
I then tried with a long ethernet cable for ethernet backhaul and it then seemed stable. After som rearrangement in my patch panel i am now running stable (as long as i know, family is fast to inform about WIFI disconnects...) for 2+ days.
It really bugs me though since one of the reasons for bying the Orbis was that i did not want to use my ethernet when extending the WIFI and it doesnt really give me a noticable performance gain.
Just my 2 cents.
BR,
/Ramp
Perhaps the order of steps in bringing up the hardware after a factory reset makes a difference. I like to use the paperclip method myself and let the hardware come up and establish first connectivity to internet for the router, and then the satellite link via wireless backhaul. No devices are connected either wired or wireless during this time. Once I see the blue rings, I'll use a Windows PC connected via Ethernet to get into the management console and make whatever changes are needed such as activating advanced wireless features, disabling daisy chain among others. I've also gotten into the habit of using address reservation for the satellite. I like it to be on x.2 address.
By doing the bringup in this manner, the Orbi is also able to adjust its LAN subnet to avoid conflict with the subnet of the host router. The change is made immediately upon entering the management console (or web GUI as some call it).
Once these basic steps are done, and granted they do take time, I'm now in a position to start onboarding devices.
Nothing but trouble with 2.3.1.44, spent another 6 hours getting useless support from Netgear. After almost two years spending significant amounts of time with support trying to get Orbi to run properly, I finally gave in and purchased Google Wifi. Set up in 30-45 minutes, been rock solid for two weeks, faster than Orbi and not a SINGLE drop or reboot. Orbi has had some weeks/months without issues over the past two years but they release new firmware and completely mess it up. I don't have enough time to deal with inferior, untested releases and support that knows less than I do. I just want a system that works. Anyone want my old system? $450 down the drain.
What trouble are you having? More details would be more helpful to us. v44 is out of date now. Try v60. Once downloaded, factory reset the Orbi and setup from scratch. Be sure to load the RBS first then update the RBR lastly.
https://community.netgear.com/t5/Orbi/Orbi-Firmware-2-3-1-60/m-p/1747642/highlight/true#M61205
What is the Mfr and model# of the ISP modem the NG router is connected too?
Is the Orbi system operating in Router or AP mode?
What is the size of your home? Sq Ft?
What is the distance between the router and satellite(s)? 30 feet is recommended in between them to begin with depending upon building materials when wirelessly connected.What channels are you using? Auto? Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz.
Any Wifi Neighbors near by? If so, how many?Try enabling Beamforming and MIMO and WMM. Under Advanced Tab/Advanced Settings/Wireless Settings
Try disabling the following and see:
Daisy Chain, Fast Roaming, IPv6 and Set 20/40Mhz Coexistence to 40Mhz only. Save settings and reboot the router and satellite(s).
bsorrent wrote:
Nothing but trouble with 2.3.1.44, spent another 6 hours getting useless support from Netgear. After almost two years spending significant amounts of time with support trying to get Orbi to run properly, I finally gave in and purchased Google Wifi. Set up in 30-45 minutes, been rock solid for two weeks, faster than Orbi and not a SINGLE drop or reboot. Orbi has had some weeks/months without issues over the past two years but they release new firmware and completely mess it up. I don't have enough time to deal with inferior, untested releases and support that knows less than I do. I just want a system that works. Anyone want my old system? $450 down the drain.
