Milkweed79

The modem is dynamic. And I used the dhcp in the router for connected devices. I changed the r2s gateway to 77.2 and the solved that redirect issue for me. I disabled the 2.4 wifi to force connection to 5 and now wifi is making available whatever the r2 has. Only issue left is the half bandwidth. Tv has 100mb cable but everything else including the wan has new cat 6. I don't know what the problem could be. It's not allowing me to login to call of duty servers again. Reboot seems to solve this where as before the firmware rollback it wasn't. Modem is brand new as well. When I rolled back the firmware I had spectrum send a new one.

I havent configured anything yet. I anticipated factory resets while this is getting resolved. Everything is at factory settings besides the admin and wifi password. I cleared the cache and cookies and still get the netduma redirect. Not really a concern for me as I circumvented my way around it into the interface. Im still only pulling a little over 200 of my 400 bandwidth and about only 3mbps on the wifi for some reason. I took some pictures if theyre helpful. Maybe I should enable the remote connect and let you and your team poke around? I feel like a component in the router is going out.

So I'm back to firmware 3.2.453 with a factory reset. For some reason when I type the gateway 192.168.77.1 it redirects to 192.168.77.1/dumaweb where it displays no such file or directory. I have to use a dashboard address from one of the Rapps to have access to the interface. For now it is allowing me to login to cod servers. Doing speed speeds tests through the benchmark testing on the R2 and through Google I'm pulling about half of my bandwidth. Even when bandwidth allocation is even through all devices I've noticed longer than usual load times with the wifi. I do have 1 system log taken from a couple weeks ago right before I rolled back from Duma os 4 if you want me to upload that. Everything seems to be functioning right except the slow loading times on the wifi and half bandwidth through the wan on the r2

No way freaking way. I literally had given up all hope. I kept pushing the reset button. Like 15 times in a row spamming it and then unplugged it for 15 seconds and plugged it back in. The interface finally came back.

Downloaded the app. Can't connect to wifi. Says incorrect password. Factory reset with the button on back of unit to use the default factory password and still said incorrect password.

Wasn't aware there was one. I will download it and attempt to use it when I get home from work.

no I havent. it was factory reset after the early access to os 4.0 and never even set up any of my static routes or port forwarding. then it stopped getting an ip issued from my modem. after on the phone with spectrum we determined my modem was malfuctioning. got a new one and it was still having issues. it was only detecting half my bandwidth as well. I never got a notification from gmail that i had a reply from netduma. so i tried rolling back to a previous update hoping the problems were from the 4.0. after it installed the older firmware it became bricked. when I enter the gateway address the page just displays no such file or directory.

the wan port keeps failing and not pulling an ip from modem when I restart it. finally got it to work again. I tried to roll back to a different firmware and now cant login into the system. tells me no such file or directory. should of never upgrade to 4.0. its been a nightmare since

Having the same issue. Got internet connectivity on my ps5 but call of duty won't let me login into the servers. Wierd stuff been happening with my r2 every since I went to 4.0

I purchased the r2 a couple of years ago. I recently was given early access for the 4.0 os. Since updating and doing the factory reset the r2 has been only been pulling 200mbs when my bandwidth is 400mbs. Is there a reason for this. I understand it's still in development and functions are being polished

thank you

any updates for netduma os 4.0 for r2?

I have spectrum and their modems are finicky on getting the gateway handshake to the router. Unplug both the modem and the R2. wait 30 seconds. Plug in the modem. wait for it to fully boot. then plug in the r2. if you plug them both in at the same time the r2 boots before the modem and the handshake is not made