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.

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.

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.

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.

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!

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?

Can you click on the server you're seeing that's appearing as being whitelisted (has the circle around the icon) and send me the ID of it? It's possible it's been whitelisted by mistake. I'm afraid there isn't currently a way to take the data you see in Ping Heatmap and apply it directly over to Geo-filter.

Welcome to the forum! Sorry to hear you're having trouble. Is your PC running Windows? If so, could you please try setting a static IP in Windows with the following information: IP address: 192.168.77.100 Subnet mask: 255.255.255.0 Default gateway: 192.168.77.1 If you're not sure how to do this, you can use this guide: https://kb.netgear.com/27476/How-do-I-set-a-static-IP-address-in-Windows After that, could you please reboot the R2 and see if you can access the interface again.

Do you have any servers in your allow and deny list? There server that's appearing in the UK is manually whitelisted, hence why you're getting connected to it.

@Bul Remove your current profile, then re-add it. Instead of selecting a service, pick 'Choose manually' when prompted to pick a service. Give that a test and see how it feels. We're updating the Ping Heatmap servers for MW2 again today. They seem to mess around with their servers a lot when the game first launches, we're also working on a solution that will affect you guys less when this happens.

We're still working on the new firmware, yes. I believe if you click the three-line menu in Device Manager you can download a list of all device names, then upload that again after the reset so you don't need to go through and rename your devices.

Maybe we're dealing with some Wireless contention here. Could you try downloading a Wi-Fi Analyser (there's one on the Microsoft store called Wi-Fi Analyser) and run a couple tests. Find which channels are least congested and switch your Wi-Fi on the R2 to use those. I know you mentioned you'd experimented with some different ones, but this test actually tells us which are the best to use. Now the R2 is back in the network, you've currently got ALL devices connected to it again, is that right? Have you still got the Traffic Prioritisation rule we added for your games console, and you're still seeing occasional stutters and ping spikes with this? Is this occuring when the network is very busy (downloads, updates, etc) or do you get this regardless of how busy the network is?

I'll let the team know the big release is today and we'll see if we can get it on Ping Heatmap! Are ALL devices on the network connected to your XR1000 or do some still connect to the upstream router/modem? What device are you playing on? How is it connected to the XR1000? Do you know anything inbetween your gaming device and the XR such as powerline extenders, Wi-Fi boosters, etc?

Yeah I think it's more a case of how HybridVPN reads the config files, it clearly has issues with the first one and not the second. We're still investigating so we hope to have it fixed for then next update. Feel free to send the config files you've got over to us, it may also help our developer in debugging the issue.