This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
Warranty ended 2 months ago. Rolled back to .114 because I still lost internet 3 times today. I'll just sell the router and go towards another company at this point if it's still continue to die on me. Thanks a lot @Netduma-Fraser and @Netduma-Liam for your help 🙂
Is .114 more stable for you then? If so, stick with it until we can release a new firmware. Netgear are well aware of the issue so we will get a fix out for it!
Seems like the 2 versions are unstable for me. Depends on the day seems like. Got 2 disconnect yesterday in the span of 20 minutes with the .114. I'll upgrade to .120 and factory reset again just for the sake of it.
Ive had the same issue since march. No fix at all.
Main feature of a router is to be able to provide DHCP...There cant even get that right. Netduma staff are spot on. there really do want to help you but Netgear are useless tbh. I called there support line and there basically said we can help but you need a support contract first which is 95 pound....Very Poor!
Sorry to hear this, the Netgear team are working on this and we are doing our best to assist them where possible. Hopefully it won't be too long before we can release an update to fix this!
Any news on this? New to the community here, I have been fighting with the constant DHCP stops (what it seems to be anyway) for a while. I've tried setting all static IPs, downgrade, upgrade, etc.. My issues seem to stem from DHCP changes, I cannot even access the router VIA a wired connection, i upgraded to .120 in hopes that it would fix my problems, but it did not, I still have to reboot the router at least once a day, sometimes twice logs aren't terribly helpful other than
[DumaOS] process '/usr/bin/dpiclass' died restart:true, Sunday, September 12, 2021 19:16:39
[DumaOS] applying qos for zone lan, Sunday, September 12, 2021 19:16:36
[DumaOS] applying qos for zone wan, Sunday, September 12, 2021 19:16:34
I just tried to change the retry attempts to 5 to see if it helps, I do appreciate the work you've put into this thus far, I'm sure it isn't an easy task. When the router is functional it is solid, and i love it, but it would be really nice to be able to find the fix, or some sort of solution, I'd settle for a heartbeat monitor to restart the software when it died. Heck, I'd even go with whatever beta of the beta you have ;).
That version should have had a partial fix, did you factory reset after upgrading? You said you've done static IPs, is that for your devices connected to the XR or the XR WAN IP or both as they should all help to an extent.
Yes sir, I factory reset after every upgrade. I did static for the devices connected to the XR, I don't have an option for static wan (using bridge mode). What's odd is it seems to correspond to wan lease change, but then others immediately after reboot, or after a new device has joined, I have the reserved range of .1-.50 for my static addresses. The devices will report unable to obtain IP address, even on the statics.
@Netduma-Fraser , That's actually what my original setup was. Out of curiosity I brought it to work with me today to test out on my test bench (1g static wan, in which i was able to pull a full 980mb/s :D), it lasted 4 hours before dhcp crashed, I had a laptop hardwired, a laptop wireless, and a cell phone; both laptops were static, cell dhcp, I left for around an hour and when the phone reconnected to the XR when I came back, the DHCP stopped, however after the reboot, I did something similar, and it worked fine. I did attempt to downgrade and then reset, then upgrade again and reset as suggested previously prior to this test. It certainly doesn't seem to have any consistency to it when it crashes, for example, it was only most of the day Saturday both on and off the network at different points in the day without issue, then when i was browsing the Internet that night it went down. Definitely nebulous.
That's actually what my original setup was. Out of curiosity I brought it to work with me today to test out on my test bench (1g static wan, in which i was able to pull a full 980mb/s :D), it lasted 4 hours before dhcp crashed, I had a laptop hardwired, a laptop wireless, and a cell phone; both laptops were static, cell dhcp, I left for around an hour and when the phone reconnected to the XR when I came back, the DHCP stopped, however after the reboot, I did something similar, and it worked fine. I did attempt to downgrade and then reset, then upgrade again and reset as suggested previously prior to this test. It certainly doesn't seem to have any consistency to it when it crashes, for example, it was only most of the day Saturday both on and off the network at different points in the day without issue, then when i was browsing the Internet that night it went down. Definitely nebulous.
That's actually what my original setup was. Out of curiosity I brought it to work with me today to test out on my test bench (1g static wan, in which i was able to pull a full 980mb/s :D), it lasted 4 hours before dhcp crashed, I had a laptop hardwired, a laptop wireless, and a cell phone; both laptops were static, cell dhcp, I left for around an hour and when the phone reconnected to the XR when I came back, the DHCP stopped, however after the reboot, I did something similar, and it worked fine. I did attempt to downgrade and then reset, then upgrade again and reset as suggested previously prior to this test. It certainly doesn't seem to have any consistency to it when it crashes, for example, it was only most of the day Saturday both on and off the network at different points in the day without issue, then when i was browsing the Internet that night it went down. Definitely nebulous.
I sure did, I turned off all of the firewall settings, and only allowed a single IP (the XR500), and shared wan ip with XR500 everytime the ARRIS would get a new WAN IP it was guaranteed to go down.
I have had this issue since march now, with no word from Negear at all. Tickets logged no reply, called netgear and got told i had to buy a support contract before there can help.
Netduma team have been amazing tho. But i would like at least something from netgear.
I have not been using the XR500 for the last month and i have had no drops at all. So quicker the firmware is out the better.
Sorry to hear that Netgear haven't been responsive on your tickets, our devs are discussing these issues with them so I can assure you it's being worked on.
Thanks for your patience though, we'll be sure to post here as soon as the next update is released!
I have had this issue since march now, with no word from Negear at all. Tickets logged no reply, called netgear and got told i had to buy a support contract before there can help.
Netduma team have been amazing tho. But i would like at least something from netgear.
I have not been using the XR500 for the last month and i have had no drops at all. So quicker the firmware is out the better.
So, I've been watching my debug (once i figured out how to turn it on), and my problem seems to stem from the something with the wifi, the false DDoS, and something consuming all of the memory and the OS is unable to recover for whatever reason. I decided to turn off WMM, and disable DDoS, so far 15hrs in no drop, not that it matters for the typical home user, but it does make me a little uneasy with DDoS being turned off.
That's interesting, keep us posted on that. If you were to get legitimately DDoSed then even with that protection enabled it wouldn't be able to counteract a big attack.
@Netduma-Fraser wrote: That's interesting, keep us posted on that. If you were to get legitimately DDoSed then even with that protection enabled it wouldn't be able to counteract a big attack.
Thats my thought, but I get like 3 pings in a row about a DDoS before WAN change, and then it drops, it's almost like its detecting a wan change as a DDoS? Ultimately, I think the underlying issue is the ram is being consumed and the system is unable to free any up, and just freezes, I sent my panic_log to TimChang, but if this is helpful for ND in anyway here ya go, .120 FW.
