Moray

You have it already, you can find it here: https://forum.netduma.com/forum/144-netduma-r2-early-access/

so i swapped it over, and the internet was restored when i checked on wifi, ill let you know if it goes down after i get home.

so it appears to be still up, i cant tell if it went down at all while i was away

Having a open nat has dramatically increased the speed I can find matches in, it also resolved the issue of getting nat errors during in game voice chat while crossplaying in destiny 2.
 
And sounds good,  I lost connection to the internet here about 4 hours ago while I was asleep

edit: removing and readding the ports in my windows firewall seems to have opened my nat type in Destiny 2 without any alterations to the R2

edit2: those ports opened my nat for call of duty, but also in that time my internet cutout again with the same dns error

edit3: and it went down again just now

so originally it was on upstream, then i tried manual then i tried nothing at all under the DHCP tab, the issue persisted through all those changes, in my isp modem i have always had the dns set as 1.1.1.1/8.8.8.8

Currently(changed this morning after it went down while i was asleep) under network im using the static setting instead of DHCP, with the IP set there and DNS override set as 1.1.1.1 primary, and 8.8.8.8 secondary.

ill keep an eye on it today while i'm away and see if the connection stays up and let you know
 

I was able to get my nat to re open (for destiny 2 anyway I didn't check other stuff yet) by rebooting my isp modem and the r2 twice after reconnecting, my r2 as a static ip assigned for it so the WAN ip shouldn't have changed.
 
As for the disconnecting/dns errors I don't want to jinx it but its been working fine since I reconnected it, will update the post if anything happens, im sure there will be somthing in the logs that lets us know what went wrong.
 
Give Liam my best and hope he feels better soon 
 
Edit: the same issues happened just now, except this time I couldn't even access the page to reboot it

Edit2: just had to reboot it again, same issue.

Edit3: just happen again

No worries about that, as we've enabled remote logging we'll have detailed logs on our end, I'll pass it on for Liam to have a look.

Ah my apologies, I see. Could we perhaps setup some remote logging on your R2? That way we can see the full logs before, during and after the issue. 
To do this, please go to Network Settings -> WAN -> Enable remote access to tech support. Then Save.
Let me know when you've done so and I'll go in and setup the logging.

hey thanks for the response, I've factory reset it and will update you tomorrow if it cuts out or works

the new firmware setup is way better, i like it so far

Since updating the firmware, have you factory reset the R2? If not, I'd suggest doing this as it's a big update and we want to ensure no old low-level code is still present from the previous firmware.
Try that and let us know if you're still having these issues.