BSilverthorn

Ok I will try that for a bit, odd that both routers do it after the update. I stuck an old TP-Link in for now so they can spy on me and its been solid. Ill switch it back over the weekend, I need the stability through the week for work.

No I have that saved as a favorite and thats a no go as well. It like the thing is running a webserver, but the webserver crashes. Powering off and back does not resolve it either.

Both WAN and LAN go at the same time. I can not access it period. I start to know the problem is coming when streaming video services start to buffer or pause. For now I stuck an older netgear in there. I might try to revert to a previous firmware and see what happens. The only way I can log back in is to reflash it. Extremely strange, I can not get the logs as I can not get into snag them.

Verizon 5G, White Cube, Model:ASK-NCQ1338FA. 300 meg down 20 meg up. (Put an older netgear in place of one of XR1000 router it has run a month solid just as a test) DHCP is not running on either router, Factory reset has been done on both routers. Both routers exhibit this, doesn't matter, usually just a day or two apart. My DHCP (not running on the router, is set to start at 25 - 200) 1st 25 are reserved for my servers and DHCP server etc.. VPN is only ingress, I do not use a VPN for outgoing. Just used to connect from home.

I have two of these routers, no matter which one I use they become unresponsive every week or two. They still route packets, but you when you attempt to login it tells you the page is missing. If I try my saved pages settings etc.... no go. If I reboot the router / routers they come back route traffic, but no page is accessible to manage. I can not get to the logs etc... It's almost as if the webserver stops delivering the pages per say. Factory reset does not fix the issue either. You will recieve a page can not be displayed after a factor reset. ISP modem is a: Verizon 5G, White Cube, Model:ASK-NCQ1338FA Both routers are setup identical: DHCP off VPN on - but not used much only on ocassion but needed media share off static IPs assigned QOS enabled on one but not the other Logging off Router in DMZ Items I have tried: Reboots 2nd XR 1000 reboot and waiting 4 minutes reboot and waiting 2 hours factory defaulting Bridge mode on Verizion 5G modem Placing Router in DMZ Turned logging off as much as possible on both routers. The only fix seems to be nrmpflashing the latest firmware back to the device. Both routers will do this. Even if I leave both routers plugged in and connected to the net, but on seperate networks they both crash like above within a few days of each other. Trying to see if there was someway I could do a cron job to just reboot them every 3 or 4 days. I am going to leave for 3 to 4 weeks for travel and concerned I can not keep my cameras up and available. They are both on the latest firmware from netgear, are there any reports of issues with the latest firmware release from netgears site. Wondering if I should drop a release or two before I leave. Brett

Sorry think I fixed that above post, but I can only access via the WAN AKA yellow ports IP address of 10.1.1.152. Not 192.168.1.1 No I just wondered what the proprer login URL would be to auth and get in. I use to just be able to type 192.168.1.1 in the bvrowser and it pop a window for username an password. Could be the pihole, but its been use for 4 to 5 years. I do not see a place to tell the DHCP server on the router to use pihole as a dns server. I did change it as you mentioned, took the pihole out of the picture, atm makes no difference.

Did that, I can access it via routerlogin.net, which if pinged resolves to 192.168.1.1. But I can only seem to hit from 10.1.1.200 and routerloging.net. The 10.1.1.152 being the DMZ / Yellow internet port. Fraser whats a good url to save that would just log you in. Meaning use to be I could just type in 192.168.1.1 and get logged in. It doesnt seem to respond forward that request to what ever the actual auth page is to log into the router. Firmware: XR1000 1.0.0.68_1.0.54 Im guessing the 50 of these in my logs is because the router itself has DHCP disabled, as I use a piehole for DHCP? Thoughts? Mar 25 18:47:43 XR1000 user.warn com.netdumasoftware.ngdilsync: No DHCP device file found: /tmp/dhcp_info_for_fing/38:94:ED:BB:8E: Brett

Whats strange is everything works from a 10.0.1.153 address, AKA the WAN port when trying to admin the router from the local network. Trying to ask the router on 192.168.1.1 is a no go, no matter what PC / MAC or OS I try from. Yes it is double natted, but has always been as my ISP router locks up "firmware bug" when you put in IP pass through mode.

Well I spoke to soon. It quit again. I notice now in my ISPs router, the XR1000's name is showing up as udhcp 0.9.8 for some reason. And it then stops responds, for awhile it show as XR1000 in reserved address list.

Well, embarassing,,,,,,,,, I figured it out. My ISPs router took a firmware update, during that update it performed a so called factory reset. It placed my WAN IP of the netgear on the same network as the lan side of the ISPs router. What in the ..... It should ask before it does this garbage. I am surprised I was able to connect period. Thankfully, I was able to patiently work around time outs with what probably was IP conflicts and get every thing reset, and click on both reboot buttons of each router remotely at the same time or split second apart ;-). UGHHHHH. Thank you Fraser, sorry for the confusion. Next time I will check this, that was a first for me.

yes, recall the URL for duma settings right off.

yes it is, I did double check that.

404 Not Found The resource you have requested is not available. for 1.1

No same experience with Safari, Firefox or Chrome. I even tried Edge.

For the life of me I can not figure out why I can access the XR1000 vi routerlogin.net but 192.168.1.1. It has been factory reset as of just now and reset back up. Routerlogin.net when pinged, points to the 1.1 address. But trying to get it via https or http to 192.168.1.1/admin results in nothing or a 404. Any ideas? This occurs even if my PC is the only thing plugged into the lan port.