Azsry

Thanks for yoru reply! I've only got 2 wired devices connected, and one has a static IP assigned to it. The other wasn't connected at the time. I'll try changing the LAN IP, SSID and channel and see if that makes any difference. Would a workaround be to assign static IPs to all connected devices?

Hey all, I'm not sure if this is the best place to post this, since I've been having this issue even on the original firmware, but I actually stopped using the R1 in favour of a Archer C7 with DD-WRT because the R1's WiFi kept dropping out years ago. I came back after upgrading to DumaOS, but the issue is still there. Wired connections work fine, but wireless devices can't connect to the router, and the SSID only gets broadcasted intermittently. When my phone detects the SSID and tries to connect, it just says Connecting, then goes back to Saved. I'm not sure what could cause this, but I get the feeling it's hardware related, since upgrading to DumaOS didn't fix the issue. I've attached the output log - the issue started happening at 10:53 (12:53 in the log file). I really want to keep using the R1, but if the WiFi keeps cutting out, I'll have to revert back to the C7 for stability. Any insight would be greatly appreciated. log-1540645053631.txt UPDATE: WiFi connectivity is back after around 20 minutes. I think the issue has to do with the DHCP Lease expiring, but I'm not sure why this would only affect WiFi devices. See the updated log file below for additional information following when connectivity returned. log-1540645394322.txt

Thanks for your replies! Turns out it was an issue with my modem's DHCP randomly taking precedence. I did a factory reset of both the R1 and my modem, and now I get the correct IP. To answer your question about whether I could access the UI by sole connection to the R1, no I could not. I did that when I was doing the upgrade to DumaOS, but after this started happening, the page became inaccessible completely, and the R1 wasn't allocating IP's at all. I don't have an ipconfig screenshot from that stage, but I do remember there not being a DHCP server or Default Gateway listed, and it gave me a random autoconfiguration IPv4 address.

Hey there, I recently upgraded my R1 from the original firmware to DumaOS, and simply connecting my ethernet cable to port 2 on the R1 let me connect to the original R1 interface. The update went smoothly and I logged into the DumaOS page using the default username/password combination, updated the max bandwidths in the QoS section, then went to replace my existing router with the R1. I still have internet access while connected directly to the R1, but I can no longer access the router page at 192.168.88.1.Running and ipconfig /all shows the default gateway to be 192.168.0.1, the gateway of my modem, rather than 192.168.88.1. I've checked that I'm connected to the R1 rather than my modem/router, and even tested on my phone. All devices show a gateway of .0.1 instead of .88.1. I'm assuming this is the cause of the inaccessibility, but I'm not sure what would cause this. I've tried factory resetting the router as well, but the default gateway stayed at .0.1. I have attached a picture of the ipconfig readout below. Any help would be greatly appreciated :)