NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Orbi Firmware Update 2.5.0.38
Does anyone have any details on this new firmware upgrade?
Release Notes:
[Bug Fix] Fixes issues with the Apple HomeKit connectivity.
[Bug Fix] Fixes the wireless crash and reboot issue when the router is under stress.
[Bug Fix] Fixes the WiFi disconnection and IOT issue.
[Bug Fix] Fixes the guest isolation issue for multicast and broadcast traffic between the main host and guest.
[Bug Fix] Fixes the Ethernet backhaul boot-sequence issue.
[Bug Fix] Updates the OpenVPN certificate from MD5 to SHA-256.
[New Features and Enhancements] Enhances the device recognition mechanism of the attached devices list.
[Bug Fixes] Fixes the compatibility issue with Sonos devices.
176 Replies
Release Notes:
[Bug Fix] Fixes issues with the Apple HomeKit connectivity.
[Bug Fix] Fixes the wireless crash and reboot issue when the router is under stress.
[Bug Fix] Fixes the WiFi disconnection and IOT issue.
[Bug Fix] Fixes the guest isolation issue for multicast and broadcast traffic between the main host and guest.
[Bug Fix] Fixes the Ethernet backhaul boot-sequence issue.
[Bug Fix] Updates the OpenVPN certificate from MD5 to SHA-256.
[New Features and Enhancements] Enhances the device recognition mechanism of the attached devices list.
[Bug Fixes] Fixes the compatibility issue with Sonos devices.Except it doesn't enhance the device recognition mechanism of the attached devices list. It completey screws them all up, randomly assigns mismatching device icons, and doesnt allow you to change/update them. It also will now only assign 1 or 2 out of 27 devices to my Satellite and had devices like Nest cameras that require high broadband assigned to 2.4g instead of 5g. Then they wont even let you contact them find a fix! I can't use my iphone now in my bedroom with my satellite 15ft away in the same room (no walls) and router directly across the hall!
Have you tried v40 FW update. A few others have said this has fixed there device naming issue. Something to try. I would factory reset the the RBS and RBR and setup from scratch and see if this works for you. If not, revert back to v30.
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(MIMO may or maynot be needed) 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).
tkrdhd wrote:Except it doesn't enhance the device recognition mechanism of the attached devices list. It completey screws them all up, randomly assigns mismatching device icons, and doesnt allow you to change/update them. It also will now only assign 1 or 2 out of 27 devices to my Satellite and had devices like Nest cameras that require high broadband assigned to 2.4g instead of 5g. Then they wont even let you contact them find a fix! I can't use my iphone now in my bedroom with my satellite 15ft away in the same room (no walls) and router directly across the hall!
- This firmware update has destroyed all my Device List name and icon configuration. It creates a new device list with cryptic names that may include device network names, and names with portions of the device's MAC address. If you try to edit the names and icons, it resets them. There are new icons.
Ditto for me, but I can't edit and apply any subsequent changes. It wasn't quite as extreme for me as the experience you describe. Only some were 'randomly' changed. Also I got the 'new' icons which may be deliberate as part of th the new firmware upgrade.
And the setting for different SSID has been gone and can't be set again.
As well for me it changed my settings in the portal and on the iOS apps.
When I try to change it, it will only stand until a restart of the app.Some other divices get a name not even close to what it is.
I hope Netgear will fix this soon.
Naming of devices and saving changes is confirmed:
Please contact NG support and let them know about it.
I concur with this. Most of my network attached devices custom names/attributes have been replaced by what appears to be a sub-par attempt at Netgear to automatically determine what a given device is. Sure, good luck with that effort, but at least give us the option to use our own naming convention, so we aren't subject to what your software thinks it should be.
It's just a new bug with the new detection feature. NG is aware of it and hopefully will fix it.
Please be patient.
LSStream wrote:I concur with this. Most of my network attached devices custom names/attributes have been replaced by what appears to be a sub-par attempt at Netgear to automatically determine what a given device is. Sure, good luck with that effort, but at least give us the option to use our own naming convention, so we aren't subject to what your software thinks it should be.
I applied this firmware update today. Took about 3 minutes, no problems after system rebooted.
dnonnema wrote:I applied this firmware update today. Took about 3 minutes, no problems after system rebooted.
Nice....check back in a few days. I think the record is 5 days.
Thanks for letting us know. Let us know if you have any problems. Mines been solid since updating as well. No issues besides the device naming problem which NG is aware of.
Be sure you do a back up configuration to file for safe keeping.
Enjoy. :smileywink:
dnonnema wrote:I applied this firmware update today. Took about 3 minutes, no problems after system rebooted.
FURRYe38 wrote:Thanks for letting us know. Let us know if you have any problems. Mines been solid since updating as well. No issues besides the device naming problem which NG is aware of.
Be sure you do a back up configuration to file for safe keeping.
Enjoy. :smileywink:
Don't forget to perform a factory reset....
dnonnema wrote:I applied this firmware update today. Took about 3 minutes, no problems after system rebooted.
Same here... Updated and took about 10 mins at best, but a slew of issues popped up!
First was the SSIDs... I had them changed manually via Telnet to indicate 2.4 GHz vs. 5.0 GHz's SSIDs... After the update, the 5.0 GHz SSID came in and out and a third one popped up as well. Tried manually correcting the SSIDs and rebooting the router... worked for 10 mins... and then the issue repeats. Tried like 5 times and each time with the same result. Since you don't let us change it within the router's GUI/website, this was the only way via Telnet. Now your firmware overrides this somehow? Really Netgear???
Also, I've noticed things really weird with my connect. Videos at the beginning have a hard time buffering initially, and just not smooth like normal as before the update. Is there a way to backtrack and use the previoius firmware?Then... the new icons and names for device is a nice touch... but some of the devices cannot be changed for some reason... Tried via the router GUI/website... chagned for 30 seconds... then reverts. Tried via the Orbi app... same result.
Fixing this via an subsequent update will take a while form Netgear... and I don't think we should be subjected to sub-par performance on a unit that many people forked out over $400 for... We really didn't spend this amount to have these issues that we would have compared to other routers...
Netgear... please help... please help ASAP!!!
My guess is that you can do a "Manual" firmware install to go back to 2.3.5.30. Just download the files for router and satellite from the Netgear support web site: https://www.netgear.com/support/product/RBR50.aspx#download Do the satellite first by connecting directly to the satellite's web interface, then do the router last.
Did you separate the SSIDs? This isn't supported on any FW version.
I factory reset my RBK50 series and setup from scratch. Set the SSID name during the set up wizard walk thru and has been online since.
Naming of devices is a known issue and NG has acknowleged they are looking into it.
chingwa14 wrote:Same here... Updated and took about 10 mins at best, but a slew of issues popped up!
First was the SSIDs... I had them changed manually via Telnet to indicate 2.4 GHz vs. 5.0 GHz's SSIDs... After the update, the 5.0 GHz SSID came in and out and a third one popped up as well. Tried manually correcting the SSIDs and rebooting the router... worked for 10 mins... and then the issue repeats. Tried like 5 times and each time with the same result. Since you don't let us change it within the router's GUI/website, this was the only way via Telnet. Now your firmware overrides this somehow? Really Netgear???
Also, I've noticed things really weird with my connect. Videos at the beginning have a hard time buffering initially, and just not smooth like normal as before the update. Is there a way to backtrack and use the previoius firmware?Then... the new icons and names for device is a nice touch... but some of the devices cannot be changed for some reason... Tried via the router GUI/website... chagned for 30 seconds... then reverts. Tried via the Orbi app... same result.
Fixing this via an subsequent update will take a while form Netgear... and I don't think we should be subjected to sub-par performance on a unit that many people forked out over $400 for... We really didn't spend this amount to have these issues that we would have compared to other routers...
Netgear... please help... please help ASAP!!!
You're able to "Manually" sets up the two SSIDs that designate the two bands... (2.4 and 5.0 GHz) via loggin into the router settings via Telnet.
Giving the router a few commands to rename the wl_ssid (2.4 GHz) and wla_ssid (5.0 GHz) will allow the router to broadcast their individual bands via the SSID you designate.
But after this update, it seems like Negear took the liberty to force the existing labeling to be removed, and utilize some type of mysterious convention to take your exisitng 2.4 GHz name, and just take like the first 4-6 characters to name the 5.0 GHz... which is completely bizzare...
With the naming of the devices completely haywired... I've lost granularity on my devices... and now have to make a separate list on all of their MAC addresses to ensure I can rename them in the future WHEN Netgear will offer an update to correct this issue...
Installed this update yesterday, and then spent the next 6 hours attempting to have a workable network, factory resetting twice in the process. Issues are:
- Random blocking of devices when access control is switched on – including at times Orbi satellites. This includes devices being blocked while attempting to carry out actions on the web interface (e.g. it let me log in but then blocked the device I was using when I went to the factory reset page) and reblocking devices 5 min after being added to allowed list.
- Internet connection constantly dropping out until factory reset for a second time
- Web interface not functioning properly, e.g. the button to confirm factory reset would not work
- The renaming issue that others have experienced
This is the worst update I have experienced to date (and this is my third fourth Netgear router), and totally unacceptable. I know some recommend a factory reset every time you update, but why should we have to spend time reinputting settings every time?
porlockweir wrote:Installed this update yesterday, and then spent the next 6 hours attempting to have a workable network, factory resetting twice in the process. Issues are:
- Random blocking of devices when access control is switched on – including at times Orbi satellites. This includes devices being blocked while attempting to carry out actions on the web interface (e.g. it let me log in but then blocked the device I was using when I went to the factory reset page) and reblocking devices 5 min after being added to allowed list.
Have you set IP address reservations for each device you are attempting to control BEFORE you engage any access controlls?
- Internet connection constantly dropping out until factory reset for a second time
What is the MFr and model# of the ISP modem/ONT your using with the RBR?
Something I haven't seen yet with mine connected to a C7800 thats in modem only mode. No drops.
- Web interface not functioning properly, e.g. the button to confirm factory reset would not work
I'm using Opera and have not see any issues with the RBR or RBS web page. Be sure to clear out ALL browser caches before going to the web pages.
- The renaming issue that others have experienced
NG is aware of this, Please be patient.
This is the worst update I have experienced to date (and this is my third fourth Netgear router), and totally unacceptable. I know some recommend a factory reset every time you update, but why should we have to spend time reinputting settings every time?
Its only recommended if you experience issue after any update. There are configurations that may become problematic as new FW comes out. So to check this, a reset is needed to see if the problems still continue or not. Some have been able to update with out. Some have had to. I just make it a habit to reset after loading and setup from scratch. My choice.
System Uptime 02:18:45:09
FURRYe38 wrote:
porlockweir wrote:Installed this update yesterday, and then spent the next 6 hours attempting to have a workable network, factory resetting twice in the process. Issues are:
- Random blocking of devices when access control is switched on – including at times Orbi satellites. This includes devices being blocked while attempting to carry out actions on the web interface (e.g. it let me log in but then blocked the device I was using when I went to the factory reset page) and reblocking devices 5 min after being added to allowed list.
Have you set IP address reservations for each device you are attempting to control BEFORE you engage any access controlls?
Yes, and had to reinput twice before giving up and disabling access control until bug is fixed
- Internet connection constantly dropping out until factory reset for a second time
What is the MFr and model# of the ISP modem/ONT your using with the RBR?
Something I haven't seen yet with mine connected to a C7800 thats in modem only mode. No drops.
I'm using a Netgear DM200 - the second factory reset seems to have resolved this
- Web interface not functioning properly, e.g. the button to confirm factory reset would not work
I'm using Opera and have not see any issues with the RBR or RBS web page. Be sure to clear out ALL browser caches before going to the web pages.
Did that, and tried a different browser. Was also taking 5+min to load a page before second factory reset. Fortunately has not reoccured since I was ready to throw it out the window at well past midnight last night, having done the update at 6pm.
- The renaming issue that others have experienced
NG is aware of this, Please be patient. Only noted for confirmation to others.
This is the worst update I have experienced to date (and this is my third fourth Netgear router), and totally unacceptable. I know some recommend a factory reset every time you update, but why should we have to spend time reinputting settings every time?
Its only recommended if you experience issue after any update. There are configurations that may become problematic as new FW comes out. So to check this, a reset is needed to see if the problems still continue or not. Some have been able to update with out. Some have had to. I just make it a habit to reset after loading and setup from scratch. My choice.
Don't disgaree, but when you are having to reinput IP reservations etc it is really rather annoying to have to keep doing so.
System Uptime 02:18:45:09
Same problem! Not only do my device names not change, or if i can get them to change they revert back on their own later, but my Access Control keeps randomly blocking allowed devices even though they are listed in the Allowed Devices list. Netgear, please fix this! I literally did a factory reset several times and redid all my settings and port forwarding from scratch in an attempt to reset everything, but the problem keeps happening!!!!
Did you update your system to v2.5.1.8 yet? This seems to fix the device naming issue. I checked mine and it is working now.
TeslaRMP wrote:Same problem! Not only do my device names not change, or if i can get them to change they revert back on their own later, but my Access Control keeps randomly blocking allowed devices even though they are listed in the Allowed Devices list. Netgear, please fix this! I literally did a factory reset several times and redid all my settings and port forwarding from scratch in an attempt to reset everything, but the problem keeps happening!!!!
I have an RBR50 with one RBS50 satellite with a separate cable modem, and everything has been running smoothly until I upgraded to firmware version 2.5.0.38 yesterday. Since then, my iPhone (11 Pro Max iOS version 13.2) has been experiencing intermittent loss of connectivity issues where it will just stop being able to connect to the Internet and requires a reboot to fix. I noticed in my Orbi logs that it does seem to be doing DHCP requests quite often, but based on older posts, this seems to be normal behavior and shouldn't be an issue. I replaced the last six digits of my MAC address with xx:
[DHCP IP: 192.168.1.21] to MAC address 7c:a1:ae:xx:xx:xx, Wednesday, October 30, 2019 08:34:34
[DHCP IP: 192.168.1.21] to MAC address 7c:a1:ae:xx:xx:xx, Wednesday, October 30, 2019 08:22:29
[DHCP IP: 192.168.1.21] to MAC address 7c:a1:ae:xx:xx:xx, Wednesday, October 30, 2019 05:29:08
[DHCP IP: 192.168.1.21] to MAC address 7c:a1:ae:xx:xx:xx, Wednesday, October 30, 2019 05:13:07
It appears that the DHCP requests are coming in after the phone wakes from sleep after it's been sitting idle for awhile.
My Macbook Pro laptops don't seem to have this issue. Anyone else run into this? Is Netgear aware of it and working on a fix? Thanks!
What is the Mfr and model# of the ISP modem the NG router is connected too?
Has a factory reset and setup from scratch been performed since last FW update? Power OFF The ISP modem for 30 seconds then back on then walk thru the setup wizard after doing a factory reset?
mtowle wrote:I have an RBR50 with one RBS50 satellite with a separate cable modem, and everything has been running smoothly until I upgraded to firmware version 2.5.0.38 yesterday. Since then, my iPhone (11 Pro Max iOS version 13.2) has been experiencing intermittent loss of connectivity issues where it will just stop being able to connect to the Internet and requires a reboot to fix. I noticed in my Orbi logs that it does seem to be doing DHCP requests quite often, but based on older posts, this seems to be normal behavior and shouldn't be an issue. I replaced the last six digits of my MAC address with xx:
[DHCP IP: 192.168.1.21] to MAC address 7c:a1:ae:xx:xx:xx, Wednesday, October 30, 2019 08:34:34
[DHCP IP: 192.168.1.21] to MAC address 7c:a1:ae:xx:xx:xx, Wednesday, October 30, 2019 08:22:29
[DHCP IP: 192.168.1.21] to MAC address 7c:a1:ae:xx:xx:xx, Wednesday, October 30, 2019 05:29:08
[DHCP IP: 192.168.1.21] to MAC address 7c:a1:ae:xx:xx:xx, Wednesday, October 30, 2019 05:13:07
It appears that the DHCP requests are coming in after the phone wakes from sleep after it's been sitting idle for awhile.
My Macbook Pro laptops don't seem to have this issue. Anyone else run into this? Is Netgear aware of it and working on a fix? Thanks!
FURRYe38 wrote:What is the Mfr and model# of the ISP modem the NG router is connected too?
wow....I believe this has been covered.
Is there a way to downgrade FW to the previous version and wait until there will be a fix?
Waiting for the next FW upgrade, will that solve the problem?
Raymonddeniet wrote:Is there a way to downgrade FW to the previous version and wait until there will be a fix?
Waiting for the next FW upgrade, will that solve the problem?
You can visit the 'download' area for your equipment to see what's available.
Waiting is always an option, that would be entirely up to you.
I had the same problems as others have posted in this thread, so downgraded back to 2.3 manually. I did the satellites first and then the router. Seems ok so far and connectivity back to how it was before.
Next time, try a factory reset on the RBR and RBS after upgrading FW if you see problems after a FW update as a last resort. Others have had good operation after a reset of the system.
Mine ran solid for over 5 days with out issues aside the device naming issue.
webbo73 wrote:I had the same problems as others have posted in this thread, so downgraded back to 2.3 manually. I did the satellites first and then the router. Seems ok so far and connectivity back to how it was before.
- Just checking to see if anything is gotten fixed so I can update my firmware
Check the release notes. It will list what is in v38.
There is a known issue with naming of devices on v38. NG is aware of this.I manually updated my RBK50 and factory reset and setup from scratch. No problems seen side the device naming problem. You don't have to update if you don't want to as well. Up to you.
Tchalk wrote:
Just checking to see if anything is gotten fixed so I can update my firmware
Tchalk wrote:
Just checking to see if anything is gotten fixed so I can update my firmwareRevert back or suffer. Once fixed STOP doing manual updates.
Having terrible connectivity problems since this FW upgrade as well as the device naming bug. Going to have to (reluctantly) reset orbi system according to this thread. Disappointed to say the least. Suggest that when updates are realised for the system that it should state 'Optional' together with a caveat notice. (Frustrated user)
My issue with the Orbis is that after iOS13, HomeKit has been extremely buggy, with devices constantly cycling between updating and no response, only occassionally actually working. When I saw Firmware Update 2.5.0.38 with fix for HomeKit issues, I truly hoped it would fix my problems (like an update a couple of years ago did), but if anything, there is only a slight improvement. Especially my iPhone will take forever to get an updated device status, with the iPad/Macs being somewhat faster.
Is there anything that can be tweaked on my end, or is the answer simply to get a different mesh system?
bjornand1 wrote:My issue with the Orbis is that after iOS13, HomeKit has been extremely buggy, with devices constantly cycling between updating and no response, only occassionally actually working. When I saw Firmware Update 2.5.0.38 with fix for HomeKit issues, I truly hoped it would fix my problems (like an update a couple of years ago did), but if anything, there is only a slight improvement. Especially my iPhone will take forever to get an updated device status, with the iPad/Macs being somewhat faster.
Is there anything that can be tweaked on my end, or is the answer simply to get a different mesh system?
Try to revert back to an eariler firmware version
Nixerr wrote:Suggest that when updates are realised for the system that it should state 'Optional' together with a caveat notice. (Frustrated user)
Or better yet.....DON'T upgrade.
Have you tried a facory reset and setup from scratch? Others have v38 working:
Mine was solid for more than 5 days after updating and resetting. No issues other than the device naming issue.
Try a reset.
https://kb.netgear.com/31486/How-do-I-reset-my-Orbi-system-to-factory-default-settings
https://www.youtube.com/watch?v=ePZSc7vnRlQ
Nixerr wrote:Having terrible connectivity problems since this FW upgrade as well as the device naming bug. Going to have to (reluctantly) reset orbi system according to this thread. Disappointed to say the least. Suggest that when updates are realised for the system that it should state 'Optional' together with a caveat notice. (Frustrated user)
- This update is nothing but a headache. Named devices fall off and it is breaking my HomeKit devices. Would like to roll back to 2.5.30
Try a factory reset as a last resort. If this fails, you can downgrade. NG is ware of this issue after we confirmed it. This doesn't effect other operations.
Orbiman2222 wrote:
This update is nothing but a headache. Named devices fall off and it is breaking my HomeKit devices. Would like to roll back to 2.5.30
FURRYe38 wrote:Try a factory reset as a last resort. If this fails, you can downgrade. NG is ware of this issue after we confirmed it. This doesn't effect other operations.
Orbiman2222 wrote:
This update is nothing but a headache. Named devices fall off and it is breaking my HomeKit devices. Would like to roll back to 2.5.30Yes as a last resort
