NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Upgraded XR500 to V2.3.2.130 and shortly after all LAN ports not connecting to my devices
Hello, I recently purchased the XR500 a few weeks ago, upgraded FW to .114 and everything was working well. Then FW V2.3.2.130 was released so I upgraded and again everything seemed to be operati...
mpsalkin not sure why there was so much trouble there with the reset, that is certainly odd - for not resetting everything we will be investigating that. If you have Armor enabled I would recommend disabling it, this has helped other peoples issues previously. For the WiFi, I'd suggest doing this now as it has helped to make it more stable in the long run - disable WiFi completely, apply, reboot from the interface, wait 2 minutes then access, enable WiFi, apply, reboot from the interface, wait 2 minutes then connect. Whenever you do a factory reset or reboot always wait 2 minutes after doing so before attempting a connection or accessing - it is booting up during this time and so interacting with the interface for example could lead to an error if said feature hadn't loaded at that time.
We're from Netduma, the creators of DumaOS, this is Netgear's community forum so it's mostly community members and us helping out, for official responses from them you would need to contact them directly.
We're from Netduma, the creators of DumaOS, this is Netgear's community forum so it's mostly community members and us helping out, for official responses from them you would need to contact them directly.
Last night after playing Xbox (connected via LAN) all devices connected to the XR500 LAN went offline. Looking at the Device Manager the LAN did not show up. Not sure why they all dropped again. Went ahead and did the workaround that fixed the issue last time and set the LAN devices to a static IP then rebooted. Router came back up and LAN devices are now connected with static IPs. Also, under the LAN Setup page all of my "named" devices were not displayed with their assigned names from Device Manager and instead have their default names.
Is this issue happening to other XR500 users on FW V2.3.2.130? Is my router defective? Just doesn't seem like this should be happening on a brand new router (or even an old router).
How did you access the interface when the LAN devices were down, via a Wi-Fi device? Or are you still able to get to the DumaOS interface via a LAN device when this occurs?
Can you assign these LAN devices IP addresses that are outside of the DHCP pool? So for example, set the DHCP range to be from .50-.250, then assign LAN devices IPs from .2-.49?
I accessed the interface via WiFi when the LAN was down.
I have my LAN connected under x.50, then I changed DCHP starting IP to 50, applied, and my devices stayed connected. I then changed one of my devices above x.50, applied, and it stayed connected. I changed that same device to under x.50, applied, and it stayed connected. So it seems that the DCHP LANs are able to connect outside the IP range. What does this mean?
The address range is just the range of IPs that the DHCP server will give out when renewing a lease or starting a new lease. If you reserve IPs for devices outside of the range, we should then eliminate DHCP from the equation and you shouldn't have any further issues.
I came home from work today and all my LAN devices were disconnected again. They are configured with static IPs under x.50. I set the starting IP in the LAN setup for DCHP to x.50 as you suggested, hit apply, and they seemed to connect as I had internet on my apple tv, but they did not show in the Device Manager. I then restarted my router and none of them can connect to the internet, nor does the LAN show up in Device Manager. I went back and forth from x.1 to x.50 and hit apply, and they never connected again. Restarted my router, and they're still not working.
Is there a bug in the firmware or is my router defective? It doesn't seem like I should have to do this. On all my previous routers I never had to set the LANs to have static IPs and change the the DCHP IP range. Also, I've heard you're less secure if you set your devices to a static IP as repeate attacks on devices will become easier. I'd prefer not to have to have my LANs on static IPs nor have to change the DCHP range. It should work out of the box.
You may need to reboot the devices themselves to ensure they get their new IPs, though to be fair I would've thought rebooting the router would've helped with that.
This is different from any issues we've seen on the XR500 as far as I'm aware. I would suggest now that you reach out to Netgear via support.netgear.com and see if they can assist further. We're now into the Network settings which isn't something we at Netduma had a part in, so we're a little limited in the advice we can offer.
- I am having the same exact issue for over a month since upgrading to V2.3.2.130. When is the next FW release coming out? My family is not happy, I have to reboot the router multiple times a day in order to have even static devices connect. This is definitely a FW bug..
- Bans25 you've done all the suggestions made so far and the reserved IPs are outside the DHCP range? They wouldn't renew that much so it might be the IP the XR is getting is changing frequently, if you can set that as static it may reduce the issue. ETAs are not provided as they're always subject to change, we're doing our best to get one out as soon as we can.
If you're comfortable with it, I'd recommend installing DD-WRT instead of the terrible firmware 2.3.2.130 until they sort the issues.
I've been running DD-WRT for the last month and while the UI isn't as flashy, IPV6, QoS, etc all work as intended and I've yet to have to reboot bar me fiddling with settings to get the best Wi-Fi bandwidth.
My speeds are the same, and my bufferbloat scores (QoS on a maxed out connection) are now A+. The congestion control on DumaOS never worked for me from .56 to .114 or .130. The DHCP issues are the worst. .130 should be pulled and recommended for deletion. It's an awful firmware.