NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
FURRYe38
Apr 12, 2022Guru - Experienced User
New - XR450/XR500 Firmware Version 2.3.2.134 Released
Enhancements: 04/12/2022
Remove Funjsq for PR SKU
Various security enhancements
Bug Fixes:
Fixes an issue where the name of an attached device cannot be changed in the device manager th...
- Jul 27, 2022
I recommend that you leave the DHCP IP address pool range set to a smaller range. You don't have to use the default range. I personally never use the factory range on any NG router. Also this provides room for static IP addressed devices as well. I use .100 to .150 as I only have around 30 devices. Plenty of room for additional devices if and when that happens.
We hope so, however don't have that info.
FURRYe38
Apr 14, 2022Guru - Experienced User
v.130: Taken 20211105
Also downgrading to v.130, factory reset, then update back to v.134 doesn't resolve the "Device Not Found" message seen in QOS. Still appears for me. Though only seen once after entering into QoS.
Ran the Connection Test after downgrading to v.130, reset then back up to v.134:
QoS disabled. A bit better results on the down. Still not near 900Mpbs.
Netduma-Fraser wrote:
We haven't made any changes in this version so Benchmark still needs to be improved, did you see full speeds on Benchmark on the previous version?
Netduma-Fraser
Apr 14, 2022NetDuma Partner
domino138 go back to using the ISP DNS, Google DNS maybe too slow for you, it would be better to be on the latest for the security updates.
FURRYe38 You'll have to downgrade to a non 3.0 version, factory reset then upgrade so .114 or .120 for example. Okay so it's actually improved a little weirdly. As mentioned we haven't made any changes so bugs on the DumaOS side of things that were present on .130 are very likely to be on this version as well. Don't worry though, it's just a reporting issue, you're getting the speeds Ookla says.
FURRYe38 You'll have to downgrade to a non 3.0 version, factory reset then upgrade so .114 or .120 for example. Okay so it's actually improved a little weirdly. As mentioned we haven't made any changes so bugs on the DumaOS side of things that were present on .130 are very likely to be on this version as well. Don't worry though, it's just a reporting issue, you're getting the speeds Ookla says.
- FURRYe38Apr 14, 2022Guru - Experienced User
I see. OK. Well the message only appears once and doesn't seem to both anything. I'll leave the router at .v134 for now. I'll get this going live on a 2ndary network tomorrow and let it run over the weekend with WiFi enabled. WIll monitor.
- mathmath51Apr 15, 2022Apprentice
Hi, Does this version include fixes related to the DHCP issue please ?
No I'm not going to test it for the Netgear "QA" 😉
- Netduma-FraserApr 15, 2022NetDuma PartnerThe change log does not mention it so it is very unlikely unfortunately
- FURRYe38Apr 15, 2022Guru - Experienced User
Currently running v.134 and not seeing any DHCP issue. I have left the DHCP server configuration at default.
mathmath51 wrote:
Hi, Does this version include fixes related to the DHCP issue please ?
No I'm not going to test it for the Netgear "QA" 😉
- domino138Apr 19, 2022Guide
As per the previous posts above I went from .120 --> .134 --> .130. Gaming latency has been unacceptable on both .134 and .130 so I've downgraded to .120 again. I'll wait until the next release to try again.
- Netduma-LiamApr 19, 2022NetDuma Partner
You mentioned previously that things were fine on .130, how long did it take for you to start noticing that latency got worse? For example, after a couple of days uptime? If you rebooted the XR through the front-end did things get better temporarily?
- domino138Apr 19, 2022Guide
Hi Liam - when I said .130 was fine I hadn't really given it enough time to see what was happening. Can you tell me what the proper upgrade path is from .120 to .134. I'd obviously like to be on the most secure version but perhaps I didn't follow the correct steps when upgrading? A step by step list of actions would be good and I don't mind doing complete resets and configuring from scratch.
- Netduma-LiamApr 19, 2022NetDuma Partner
There shouldn't be an upgrade path as such, however some users have had an error in QoS so until that's fixed I'd suggest the following to be safe:
- Downgrade to the last 2.0 firmware (2.3.2.114)
- Factory reset the XR500
- Upgrade to the latest full release 3.0 firmware (2.3.2.134) without factory resetting
Let me know if you're still having issues after that.
- domino138Apr 19, 2022Guide
Thanks Liam - just to confirm the process for this: "Factory reset the XR500"
Is it:
Settings / Administration / Backup Settings / Revert to factory default settings / Erase
- Netduma-FraserApr 19, 2022NetDuma Partnerdomino138 yes that's correct!
- domino138Apr 23, 2022Guide
I've been running on .134 for 3 days now - performed the upgrade as per the steps set out by Liam. Just not happy. General internet performance is poor. All three of my kids are independently saying their games are lagging. I need to go back to a version prior to .130.
.120 was working fine for me for months - I will go back to that but before I do is there anything you'd like me to do?
- Netduma-FraserApr 23, 2022NetDuma PartnerYou may just need to re-adjust your QoS settings but if you need to go back that's absolutely fine, nothing you need to do. Once our planned update goes out everything should be a lot more stable and bring it in line with other platforms.
- satinghostriderApr 24, 2022Tutor
Is this a bug on the latest firmware 134 where under system information it still shows 130?
Anyone else can confirm?
Thanks!
- Netduma-LiamApr 25, 2022NetDuma Partner
Unfortunately I can't see the image as it's not been moderated yet.
Are you referring to the DumaOS version field? Perhaps try attaching the image rather than pasting it, I should be able to see it then.
- FURRYe38Apr 25, 2022Guru - Experienced User
Your picture shows v.134...
satinghostrider wrote:
Is this a bug on the latest firmware 134 where under system information it still shows 130?
Anyone else can confirm?
Thanks!
- Netduma-FraserApr 25, 2022NetDuma PartnerClear your browser cache/cookies and then it will update correctly
- satinghostriderApr 25, 2022Tutor
Actually, this issue occurs when using remote connection to the router but locally it seemed to reflect the correct version under system information. Oddly, I tried clearing the cache/cookie data this morning from my office before logging on to the router at home and it now shows the correct version.
Thank you for reconfirming. ***SOLVED***
- Netduma-LiamApr 26, 2022NetDuma Partner
That's great to hear, let us know if you have any other issues.
- Netduma-FraserMay 08, 2022NetDuma PartnerOf course not, that's something that will be fixed. I'll reply to your other comment in your topic.
- Netduma-FraserMay 15, 2022NetDuma PartnerI wouldn't suggest upgrading to a different OS, you may struggle to re-upgrade back to DumaOS and if you have any warranty left that would invalidate it.
- agent47isn1May 15, 2022GuideDude chill out it's not that serious there's stable firmware out there. If it affects your life so bad buy a different router.
- Retired_MemberMay 16, 2022And luckily the 134 update is not broken. The 130 update completely crapped itself after a while when I updated to that, I'm glad you guys fixed most of every bug in 134 on 130 most of everything wouldn't connect. After a while I updated I had to format it to factory default and now it all works
- agent47isn1May 16, 2022GuideI did this is a public forum plus I have the xr450 which is just like the xr500 minus small differences. Ive only had a few hiccups but for the majority of 2 years this router has been nothing short of amazing.