NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
XR700 Constant Issues with DHCP
Running the latest Firmware with the hotfix and still having issues with this router. It refuses to give out IP addresses after a reboot. Devices cant connect due to no IP given. If I set one static ...
Retired_Member - helpful; thanks for this - you're describing some of the other symptoms perfectly (I had one device / mac address the NetDuma has assigned SEVEN IPs to) - still running the Linksys WRT1200AC in the meantime, but I would really love to use my XR700 - if for nothing else the extra anntenas === way better range and connection for devices (when it worked).
Was that upgraded to the .24 version?
.24 solves nothing. It does not change the problem with DumaOS: DHCP / DNS Server is broken, causing R-App(s) and Device Manager to not load as well.
When you actually fix this issue, let me know and I may try to take it out of Access Point mode. Either way, a lot of $$$ spent for just an access point or an inoperable router.
- Everything in Settings is Netgear, we've already made them aware but if you're still in contact with them let them know you're still encountering the issues.
Netgear support feigned ignorance as to what you are saying and wanted to collect more information to send to engineers that I cannot talk to directly. They have no clue how many have returned this router they say. They also say they are not getting many calls about this router. I think the agent is misinformed or trying to mislead. Netduma blames Netgear --> Netgear states they need more info --> Netgear says they have all the info they need, and that they will send a new XR700 --> Netgear sends you "new" XR700 without latest firmware (that way you know they tested it with the latest firmware before sending, right?) --> Same issues arise --> Netgear states they cannot give you a refund, Amazon or wherever you purchased the router has to do that --> Netgear states they cannot give you a newer model, as it is not their policy (What is their recall policy? This thing should be recalled!) --> Netgear states they need more info (logs and more) before they escalate your case to an engineer --> WHEN THIS ROUTER FAILS YOU CANNOT ACCESS IT - IF YOU DO NOT HAVE YOUR LOGS BEING OFFLOADED, HOW WILL ANYONE EVER GET THE INFO THEY NEED?! I pretend to be a sheep on that last statement that just follows the herd, believing that Netgear and Netduma do not know what is going on with this $400 box of ______.
I was able to telnet into the router and run:
tail -f -s 10 /var/log/log-message
I think when this log file is rotated, the tail -f stops reading. tail -F solves this read after log rotation issue in Linux, but it appears that option is not available in BusyBox. Was wondering if this portion of the output I am getting from /var/log/log-message means anything?:
39664:[wifi0] FWLOG: [40638859] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x1, 0x0 ) 39666:[wifi0] FWLOG: [40640907] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x2, 0x0 ) 39670:[wifi0] FWLOG: [40645003] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x1, 0x0 ) 39671:[wifi0] FWLOG: [40646027] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x2, 0x0 ) 39676:[wifi0] FWLOG: [40651148] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x3, 0x0 ) 39677:[wifi0] FWLOG: [40652172] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x2, 0x0 ) 39684:[wifi0] FWLOG: [40659340] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x1, 0x0 ) 39690:[wifi0] FWLOG: [40665484] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x2, 0x0 ) 39691:[wifi0] FWLOG: [40666508] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x1, 0x0 ) 39693:[wifi0] FWLOG: [40668556] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x0, 0x0 ) 39700:[wifi0] FWLOG: [40675724] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x1, 0x0 ) 39702:[wifi0] FWLOG: [40677772] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x0, 0x0 ) 39704:[wifi0] FWLOG: [40679820] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x1, 0x0 ) 39706:[wifi0] FWLOG: [40681868] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x2, 0x0 ) 39707:[wifi0] FWLOG: [40682893] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x1, 0x0 ) 39712:[wifi0] FWLOG: [40688013] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x2, 0x0 ) 39713:[wifi0] FWLOG: [40689037] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x3, 0x0 ) 39714:[wifi0] FWLOG: [40690061] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x2, 0x0 ) 39715:[wifi0] FWLOG: [40691085] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x1, 0x0 ) 39719:[wifi0] FWLOG: [40695181] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x2, 0x0 ) 39721:[wifi0] FWLOG: [40697229] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x1, 0x0 ) 39722:[wifi0] FWLOG: [40698253] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x2, 0x0 ) 39723:[wifi0] FWLOG: [40699277] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x1, 0x0 ) 39726:[wifi0] FWLOG: [40702349] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x2, 0x0 ) 39729:[wifi0] FWLOG: [40705421] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x1, 0x0 ) 39731:[wifi0] FWLOG: [40707469] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x2, 0x0 ) 39734:[wifi0] FWLOG: [40710541] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x1, 0x0 ) 39747:[wifi0] FWLOG: [40723854] WAL_DBGID_XCESS_FAILURES ( 0xffff, 0x2, 0x0 )