Netduma Liam

Thanks for letting us know, we'll go ahead and get that updated!

Thanks for letting us know @Mobel, I'll speak to the team and get them to update Ping Heatmap as it needs doing again. I'll also ask that they look into the locations of the servers to make sure they're accurate.

OK not to worry, thanks for letting us know. We'll stand-by until you've got the logs!

Not currently, can you go to System Information -> click the three-line menu in 'Installed Rapps' and set the number of retries to 5. Then reboot and see if the issue occurs again.

Hey everyone, As we continue to work on improving our new DPI system, we're now looking to add as many of your favourite games/applications as possible. If you have a game you like to play or an application you use that's not classified in DumaOS' DPI system, please fill out the below form so we can get it supported for you. https://forms.gle/X4A9R4rikDMa3Wzq5 Thank you all for your help! Liam.

Not to get you all too excited, we're just assembling a small group of XR users to test out the latest firmware once it's ready. If you can send me a DM to let me know if you're interested, we'll note your name down and let you know if/when we've added you to the group.

@Dialatech @ryekye @Stilts29 @dv_boy @DMaR I've sent you all a DM.

Thanks, we'll make sure they get an update done today. Resycn cloud later on today and you should see servers again.

Can you drop download more, to around 70%? Can you also watch Network Monitor when you're playing and see if it's purely detecting CoD, or if it's detecting any other games at the same time?

We will occasionally, if we have a new version with new DumaOS changes and we want to get it to some people before it goes full release, though at the moment we don't have any firmwares that are at this stage.

Totally understand your guys feedback, we felt confident with the last firmware we tested that we would start giving it out before Christmas. Upon receiving a firmware with remaining bug fixes, there were some regressions. We've since fixed those and are testing those fixes as I write this. If the next firmware comes back with all these changes implemented and regressions fixed, I feel a release before Christmas is likely, however as you say, there's no way I can guarantee that.

Excellent, thanks for letting us know, I'll pass this onto the team.

Thanks for that, let me add that too!

Is this just over Wi-Fi, not over wired? What device were you playing on and what game specifically? How far is that device from the R2? We are aware the Wi-Fi on the R2 isn't as good as we'd like it to be so it's possible that's the problem. Of course gaming over wired is always our recommendation.

Yes, that will be in there too as far as I'm aware!

We've been testing the bug fixes since the last test internally to verify they're going to work before getting another build. It's all looking good so we're now waiting on the next build from NETGEAR. Once we're happy with this one we'll go ahead and release it here and on the NG forums as a sort of 'beta' firmware so it doesn't have to wait on NG testing. There's been some issues with the XR1000 which I need to catch up with the team on later, I'll update the firmware progress article once we've discussed that.

It should be back up again, resync cloud and check now. Good idea, though ideally we'd rather improve how we update Ping Heatmap so people don't need to be notifying us that servers are down all the time! We're working on that currently.

YouTube doesn't quite work the same way, their ads are served from the YouTube domain. If you block that, you can't use YouTube at all. We're looking into whether there's a way to do it, but so far it doesn't look like it's possible with the current solution.

Welcome to the forum! We still need to endurance test it so we don't know for sure, but it includes a lot of fixes that resolve similar issues on other units so we're hopeful it has.

Yes, that's because these devices are strictly limited to their allocation and cannot borrow from other devices. That's the only way to specifically hard limit a device though.

You can use bandwidth allocation, with Share Excess disabled from the submenu in Bandwidth Allocation. You can then limit the bandwidth to specific devices.

That's already been added, I don't know whether it'll be in the next release or the one immediately after, but it won't be long!

Of course, thank you!

We believe we're getting close now, we've fixed what we believe was the last big bug and are now awaiting more firmware. Once we've got that we'll test again and if it's all good we'll go ahead and start releasing it.

Bien, ¿entonces lo desconectas y lo vuelves a conectar con bastante frecuencia? ¿Puede enviar un correo electrónico a [email protected] con su número de pedido original y la dirección de entrega, por favor?