e38BimmerFN

FYI, new FW is available: https://community.netgear.com/t5/Nighthawk-Pro-Gaming-Routers/New-XR1000-Firmware-Version-1-0-0-68-Released/td-p/2312239

FYI, new FW is available: https://community.netgear.com/t5/Nighthawk-Pro-Gaming-Routers/New-XR1000-Firmware-Version-1-0-0-68-Released/td-p/2312239

FYI, new FW is available: https://community.netgear.com/t5/Nighthawk-Pro-Gaming-Routers/New-XR1000-Firmware-Version-1-0-0-68-Released/td-p/2312239

FYI, new FW is available: https://community.netgear.com/t5/Nighthawk-Pro-Gaming-Routers/New-XR1000-Firmware-Version-1-0-0-68-Released/td-p/2312239

FYI, new FW is available: https://community.netgear.com/t5/Nighthawk-Pro-Gaming-Routers/New-XR1000-Firmware-Version-1-0-0-68-Released/td-p/2312239

FYI, new FW is available: https://community.netgear.com/t5/Nighthawk-Pro-Gaming-Routers/New-XR1000-Firmware-Version-1-0-0-68-Released/td-p/2312239

@FuzyThanks to ND for the little round button between the email and search icons on users profiles. 😁

Doesn't explain anything. Would need to know more about your ISP and configuration. Could have just a faulty unit from the beginning. Still hard to tell with out more info and details But sounds like you've moved on so, enjoy ASUS then. Glad mine works.

The ISP side should be checked first thing, signals and line quality and modem or ONT configurations. Cabling then configuration of the router. Factory reset set and setup from scratch. Limit making lots of changes right off the bat. I've seen others post good working XR1000s so not everyone has problems.

Might give more details on what your having problems with the XR. Iv'e not see major issues with my XR1000. Works well. Factory resets are a valid troubleshooting step. There maybe some mis-cofigurations or something that causes the router to stop working right. Seen this MANY times where a reset solves many issues. Also how the router is configured is important as well. And what the router is connected too on the ISP side can impact any router as well. There are some things can could help. But ya know, can't lead a horse. Can't always blame the router. 🙄

Ok, so successful update to most current version of the beta was done today. Got it updated and the update took Thank you both for getting the R2 back into a good working state. Will keep a better eye on FW updates. Have a good night.

Ok will give it a go. I'll let you know the results. Thank you both for getting the R2 back in a good state. Have a good afternoon.

Ok, I think I might go for last official release then try the current beta version. I presume that is v3.3.166? Any chance you could push this?

OK I see that. Came up and wifi radios were running and the setup wizard started. After I completed that and got to the home screen I see v3.0.0.205i loaded. What version of FW would be recommended? Offcial release? Should I load the last available beta after that maybe? IF so, what version specific please. Were you able to determine why the router wouldn't take a local FW update here? Thank you again.

Ok i got the R2 on a single NAT with the ISP modem. See if you can access it. I'll check on it again in the morning. Thank you,

I had remote access enabled however as I feared, when I got up this morning and checked it before work the router stopped working. Thought the WAN LED was blinkin, the DHCP service was not as when I connected a wired PC to the back of the R2, it failed to get an IP address. Same thing happened yesterday evening when I returned from Dinner. Seems like there is a short period of time when the R2 is stable while connected to the WAN but seems to fail sometime afterwards. Will probably need to set up a time time frame so we can both be online at the same time and see if we can get something to work there and when I'm at home.

I left the router on. Came back and nothing however I presume you guys were out for the evening. I played some xbox on a different network but left my wired PC connected to the R2, I found later that the PC lost internet services an I couldn't access the R2 web page. PC had no IP address. So power cycled the router with out the WAN being connected and it came to ready. Connected the WAN port and disconnected the PC. Not sure if the R2 will be stable with out user intervention. I'll check in the morning to see if anything happens. Maybe we'll have to schedule something.

Sent you a PM.

No that didn't work. Cleared caches before entering the routers web page after turn it on with a wired PC, no matter how fast afer the dashboard loads, router is not taking a FW update. Good news is that the R2 seems to be stable and connected behind another router connecting off a D-Link DGS-105 GB switch on it's WAN Port. The router hasn't rebooted or got into some odd state. Can you guys force something thru in a double NAT condition by chance? Even if I put it in a DMZ? I noticed if I reboot the R2 from the UI, and let it come to ready while connected to the LAN switch, it doesn't come to ready and begin this reboot loop here. If I disconnect the WAN port from the switch and let to come to ready, then connect the WAN cable from the switch, the R2 is stable and doesn't reboot loop. Or do you need this to be in a single NAT condtion? Current Configuration on my modem is in gateway mode on the CAX80 though I can change that back to modem mode and try to see if the R2 will be stable.

I wish I could, the R2 enters into a boot loop when it's WAN port is connected to any ethernet connection, modem or otherwise.

Checked and cleared before and after sending the FW file. Version remains at v.205. One item I noticed is that the FW upgrade window never cleared or refreshed and updated after the router seemed to process the FW file.

HI Fraser, Just downloaded fresh copy of DumaOS-R2-3.0.123-Release.sig and applied it using MS Edge. The ethernet LED turned off for a few seconds then back ON after the file was sent. I can see it being sent in a network montoring app I have. Then the two WIFI LEDs turned off for several seconds, then back ON. I cleared browser caches as well. I refreshed the page and v.205 was still loaded. I tried a factory reset thru the UI and after getting to the home screen after the setup wizard, I sent the FW file again. Samething observed. v.205 remains on the router. Seems like maybe the FW staging area is not working right or the router is in some unknown bad state and not accepting or processing any new FW files. Thoughts?

Will do...

So I had left my R2 on the shelf since last testing and operation was on v.205 months ago. After seeing a post about a closed betaopportunity, I asked for access too and thought lets get the R2 updated and do some more testing on it. I was curious and updated from 3.0.205 to the most current beta seen here? https://forum.netduma.com/forum/144-netduma-r2-early-access/ I can access this page however can't post anything...I attempted to load v3.1 and router was acting really funny and not working as expected after sending the 3.1 file down and after doing a reset and power cycle, the router seem to fall back to 3.0.205 afterwards. Kept rebooting in a boot loop or the ethernet kept reporting connected then disconnected. Ok, Let me try the newer official release then go to the beta. ok so there seems to be a problem with my R2. 1. I'm connecting the R2 behind another router XR500 thats connected to my modem. XR is using 192.168.0.1 for LAN. R2 is on 77.1 so should not conflict. When I have the R2 connected to the XR and send down the FW file, v.394, it seems to load however after the R2 reboots it begins to boot loop and never comes to ready. I can disconnect the R2 from the XR router and this stops the boot loop and then I can access the R2. AT this point the FW version is still on v.205 and v.394 never took or was applied. I can see that the router seems to take the FW File as i see behind the popup that the connection is lost. But after this and the reboot with out the R2 being connected to anything accept the 1 wired PC, never gets the new version of FW. Historically I've been able to connect the R2 behind another router while testing or with out being connected to anything and doing FW updates prior before going live to the ISP modem. Something I normally do as I have the main system running until I can test and check out new stuff. I was able to do a factory reset from the UI as well and got in..I had the R2 disconnected from the other router and when I got to the setup screen I then connected the R2 to the XR router and was able to complete the setup process. It was meantioned that Duma could send a forced update from there side. Just wanted to see if I could get my R2 online and ready for you to attempt a force FW update from your side of the fence. Seems like this R2 is in some bad state. After leaving it offline, powering it on and connected to a working CAX80 in modem mode so it gets a public IP address on the R2, one ethernet connected PC behind the R2 is not getting any IP address whatsoever. Pressing the reset buttons seem to be not working as well as only the power, internet and ethernet LED are ON or blinking. I don't see the two WIFI radio LEDs turn on after a reset. PC is not getting any form of a IP address sans the 169 APIPA. Is there TFTP support on the R2? I did some more digging and I finally got access to the R2s web page. What seems to be the R2 stuck in a reboot loop, it would give me a few seconds to wait for the UI to appear in the web browser. I had to wait past two-3 reboots to finally get in to the UI and do a Factory Reset from the UI. That took and after it reset and rebooted, the two Wfi LEDs came on. I waked thru the setup wizard again here and completed it. Heres the kicker, the R2 rebooted and seems to start the reboot loop again as I saw the wifi LEDs turn OFF and the PC lost it's ethernet connection. I got the idea of disconnecting the R2 from the modem so I unplugged the cable from the WAN port behind the R2. Low and behold the R2 came to ready and no longer rebooted on the boot loop. I did another factory reset and this time walked thru the setup wizard with out the WAN being connected and go to the dashboard. I attempted to load v.394 on it and the file seemed to take. However, after the router rebooted, v.205 was still loaded. I rebooted the router again and after it was ready I turned OFF all features that I could to see if anything would help with the reboot loop with the WAN connected. That didn't work out. Wondering if that FW staging partition got corrupted or changed to a READ ONLY state... Seems that if the R2 is connected to any internet or ethernet source on it's WAN port, this causes the R2 to enter into a reboot loop. No idea what would have caused this or if it can be fixed. I presume this will prevent any FW updates from you guys. There any JTAG ports in side maybe? Any other possible method to bring this unit back to a good working state or is this one toast? Let me know what your thoughts are. Thank you for your time.

So I powered the router OFF for 30 seconds then back ON after updating FW. Didn't work. Factory reset and setup from scratch worked. The app is now accessing the XR1000.