New - XR450/XR500 Firmware Version 2.3.2.134 Released

[Raf1212]

@agents no, say it of the holder of those who got kicked out 300 euros for a router that is not working properly, a long time do not use this scrap, but others that may want to because they can not afford to different hardware, so do not slacken, because it takes already two or three years .

[agent47isn1]

I 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.

[Himaro0]

Hello,

Still getting QOS error: device not found 

Things tried:

Downgrade back to version .130 and did a hard reset, upgraded to version .134

The connection benchmark does not match the actual number IPS speed number. 

Any thoughts? 

Thanks

[Netduma-Liam]

Could you please repeat the process but instead downgrade to the 114 firmware, linked below.

https://kb.netgear.com/000062867/XR500-Firmware-Version-2-3-2-114

Once downgraded factory reset either through the interface or by holding the button on the back for thirty seconds.

Then re-upgrade and don't factory reset after the upgrade.

[domino138]

Hi Liam - do you have any idea when the next version is coming out for the XR500 please?

[Netduma-Fraser]

@domino138 we post any and all potential updates on the status of firmware here: http://support.netduma.com/en/support/solutions/articles/16000132677-dumaos-firmware-progress outside of that we don't have any extra information to give

[lenbo7777]

My XR500 had a problem - documented here:

• https://community.netgear.com/t5/Nighthawk-Pro-Gaming-DumaOS-3-0/New-XR450-XR500-Firmware-Version-2-...

...where it would sporadically restart and reset.  Since upgrading to .134, I haven't experienced this again.  But I also hadn't reserved any addresses.  Earlier this week, I reserved one device and address in the LAN.  My DHCP is set to 192.168.1.2 - 254.

The morning after I made the reservation, my router restarted and reset - just like it had previously.  

Is anyone else experiencing this...and is there ever going to be any relief?

[FURRYe38]

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. 

[Netduma-Liam]

That is odd, I would suggest going through and reserving IP addresses outside the DHCP range, then see if you experience any further disconnections after that.