Netduma Liam

Thanks for posting this. It would be good if you could create a new topic with this information so we can look into this further with you. In the new topic, could you please include the below: When the connection drops, are you able to access the DumaOS interface from a device connected via wired? Do you need to reboot the R2 to get the connection back, or will it eventually restore itself? Do you recall if the disconnections occurred after a particular device started generating some traffic? Are you using any wireless extenders, powerline adapter or access points for example?

@ahmedkI've responded to your new topic, let's continue there.

@CJArthur Could you perhaps let us know the specific Traffic Controller rules you currently have configured? We'd like to replicate them internally to see if we can reproduce the bug.

Excellent, thanks for letting us know. We'll relay this info to the devs and get back to you.

Could you please try hitting 'Resync cloud' now in Ping Heatmap and see if that's better?

A few users have reported this with the XR500, we'll get the team to look into it and see why it's not updating.

Thank you for this. I've forwarded these logs on to a developer to investigate. I'll get back to you ASAP.

Can you grab us a new log file since disabling Network Priority? Hopefully that will now provide a little clearer insight.

No, it shouldn't have an affect like that. To confirm, are you simply using the default lists in the 'Adblocker lists' panel, or have you added any of your own? When navigating to the Logitech website, for example, does the bubble chart next to your device show that it's blocking domains? Can you check the Top Blocked Domains chart and see if there's anything getting blocked that shouldn't be? URL's relating to Logitech for example? If you find anything, you can create a whitelist with these domains and that should resolve the problem. You could also send them over to us here so we can add them in to the default whitelist for the next update.

Thanks for letting us know, we're working on this DNS issue currently so if you could continue to set DNS manually on your devices, we'll keep investigating and get it fixed.

OK, we're currently working on reproducing the issue so if you could set a static address on the device we'll keep working to troubleshoot the issue ourselves.

There may have been a firmware update for example that's introduced this issue for you. If disabling these rules doesn't help, could you please experiment with having QoS completely disabled from the three-line menu in Congestion Control, then see if the issue re-occurs after that? We realised this isn't a long term solution, we just need to further narrow down the problem to find a solution.

Do you have any Traffic Controller rules currently configured? Are you using Adblocker at all?

To confirm, are you noticing slow matchmaking/any other side effects of the moderate NAT type in games? I'm currently looking into the issue of remote logging with a developer, I do believe this is going to be really helpful in working out the cause of the problem so as long as you're happy to still try that I'll update you once we've come up with a solution.

Thanks for confirming, you could pin the logs to the Dashboard, however if you're now unable to load the dashboard at all that won't help. You may now need to reboot the modem in order to re-gain access. Once you've got access again, could you please go to System Information and let me know which DumaOS version you're currently using?

The IP the R2 is getting from the modem may have changed, double check that and put the new one in the ISP DMZ if it has. That should resolve any NAT issues.

Can you try completely disabling QoS from the three-line menu in Congestion Control and see if it works then?

Yeah we're definitely able to access the R2 because we use your WAN IP to do so, we're just not then getting any logging back from that IP. Unfortunately those logs are related to any issues, we've noticed their frequency on the R2 but investigated and deduced that they are not caused by any particular issues as such. I can understand your decision not to use the R2 for now, however you could also perhaps revert back to the old firmware and factory reset? It wouldn't necessarily help us solve the issue but at least it would improve your experience?

Hey, sorry to hear this! Which page are you trying to load when this occurs, is it simply the Dashboard or are you trying to navigate to a specific page? After the issue occurs, can you go to System Information -> Logs and download the log file. You either send it over to us via email at [email protected], or upload to somewhere and share a link with us via DM.

OK, could you please test if it still occurs straight to the modem?

Does this still occur if you are connected directly to the modem instead of the R2? Have you set your own DNS settings on the R2 or on your PC at all?

Apologies for the delay, I'm back, thank you! I'm not sure what's going on here, we're not getting any logging from your R2. I'm going to get some developer input on this and see if we can work out why. After we enable logging etc, are you then changing/reverting anything in your setup that could potentially cause your WAN IP to change? Are you for example removing the R2 from the modem DMZ, or re-enabling any port forwarding rules?

I would suggest setting it to Auto-enable. That way, it will only limit bandwidth to background services if priority traffic is detected.

Unfortunately the logs only tell us what happened after the reboot. We don't appear to have any remote logs from your unit either so I've gone in and double checked everything, then re-enabled it. Please let me know again next time the issue occurs.

OK thanks for letting me know. I've enabled remote logging now so please let us know if this occurs again and we'll have the full logs for it.