Netduma Liam

I've responded to your other post, I'll leave this open for now in case any members of the community want to chip in.

As mentioned above, it's not the intended purpose of DumaOS and it's not something we've tested. Unfortunately you're not going to find the answer you're looking for on our forum. We'd suggest setting a radius in Geo-filter around your local country and ensure you're always getting connected to the lowest ping servers possible, that's how you'll get the best performance in game. Check out this guide for a detailed setup for Geo-filter: http://support.netduma.com/support/solutions/articles/16000077072-dumaos-optimal-settings-guide-geo-filter

There will be yes, though I don't have an ETA I can share unfortunately!

That's really odd, I don't see how that could possibly affect this but I'll certainly be testing it out. As a test, could you switch to device mode and put the slider for the device you're playing on up to 100% and hit 'Update Distribution'. After this check if you're still getting consistent games.

OK sure, thanks for the feedback! You too.

What game are you playing where you're not seeing anything? Could you send a screenshot of what you see in Geo-filter when you're actively playing a game?

We're still planning on releasing a fix to this in the next firmware, apologies that it's still not working for you!

Good work! So now you're running .10 after a factory reset, correct? Realistically, you should be able to update the firmware using the GUI like all other users can, if your troubleshooting does not enable you to do this, I'd still suggest pursuing the RMA route as Newfie mentioned.

No ETA I'm afraid, it's an old Rapp and will need a lot of looking into to bring up to speed with the rest of DumaOS 3.0. I did take a look into it a little while ago, the frontend needs a lot of changing. We don't have anything like this in the roadmap as yet, do you have any ideas for Rapps you'd like to add?

Good point from Newfie! How did you reset the XR? In the mean time I'll have a dev look into the captured outputs.

Where abouts are you located? What indicates that it's being located in Europe?

In theory, yes! I'll pass on the feedback.

Well done! It's very odd that only .56 will stick though. Did you factory reset between installing .56 and trying to upgrade again? If not I'd certainly suggest this as it means you can then start from a clean slate before the next upgrade.

Could you perhaps try using Windows TFTP instead? https://kb.netgear.com/000059634/How-to-upload-firmware-to-a-NETGEAR-router-using-Windows-TFTP

Oh awesome, thanks for letting us know and thanks to @e38BimmerFN for the great suggestion.

Good response from @e38BimmerFN, let us know and we can assist further! Do you still have remote support enabled? I'll need to chase up the dev again as they were so busy last time we requested it. I understand it's been some time since you reported this so I'll request it's looked at on a priority.

There's isn't yet I'm afraid, I'll put it on the roadmap to make sure it hasn't been forgotten though.

Welcome to the forum! Do you see the same issue in an incognito window? It may be best to create your own topic so we can help you there.

Not at all! It's a cool idea and I've just put it on our roadmap so you may see it added in future, but it's currently impossible to assign an ETA to that I'm afraid.

Cool idea, but yeah unfortunately not supported yet as Newfie mentions.

This is something we've been pondering ourselves and we've been exploring some of these ideas somewhat recently. Geo-filter and Ping Heatmap have a close relationship and this is certainly something we want to take advantage of in upcoming firmware. While there's nothing concrete yet, I can say that we are planning on making some big changes to the two in terms of usability and functionality.

I can't confirm for sure, but I know we're working on bug fixes and general improvements to the functioning of Rapps currently.

OK, seems like a random one-off then. Let us know if you have any further issues.

Thanks for reporting this, has the error re-occured since rebooting? It's likely a tiny error and DumaOS just got caught up on itself, it shouldn't happen again but if it does please do get back to us!

I've chased up the dev but he's not in today so I won't know for certain whether he's been able to take a look or not, we'll let you know when he's responded.