Jump to content

Netduma Liam

Members
  • Posts

    7651
  • Joined

  • Last visited

  • Days Won

    131

Everything posted by Netduma Liam

  1. 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?
  2. Good point from Newfie! How did you reset the XR? In the mean time I'll have a dev look into the captured outputs.
  3. Where abouts are you located? What indicates that it's being located in Europe?
  4. In theory, yes! I'll pass on the feedback.
  5. 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.
  6. Could you perhaps try using Windows TFTP instead? https://kb.netgear.com/000059634/How-to-upload-firmware-to-a-NETGEAR-router-using-Windows-TFTP
  7. Oh awesome, thanks for letting us know and thanks to @e38BimmerFN for the great suggestion.
  8. 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.
  9. There's isn't yet I'm afraid, I'll put it on the roadmap to make sure it hasn't been forgotten though.
  10. 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.
  11. 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.
  12. Cool idea, but yeah unfortunately not supported yet as Newfie mentions.
  13. 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.
  14. Welcome to the forum! Sorry to hear you've been having this issue, were you connected directly to the R2 when you ran this command? Are you connected via wired or wireless? How did you try to factory reset the R2?
  15. I can't confirm for sure, but I know we're working on bug fixes and general improvements to the functioning of Rapps currently.
  16. OK, seems like a random one-off then. Let us know if you have any further issues.
  17. 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!
  18. Welcome to the forum! In Geo-filter - Click the three-line menu in the top left of the map and you'll find the "Re-sync cloud" button there.
  19. 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.
  20. We need to update some of our Ping Heatmap data, I've requested an update already this morning so hopefully we can get that done today! Your router will automatically pull the latest cloud update so there shouldn't be any action required by you guys. Apologies for any inconvenience caused, CoD servers specifically seem to change a lot so they require frequent updates.
  21. Welcome to the forum! So wireless devices are getting full speeds? How did you disable QoS? I'd suggest doing this from the three-line menu in Congestion Control. Have you tried using a different ethernet cable for the wired device suffering from slow speeds?
  22. I don't blame you, we're aware of this issue already and the guys internally said it wasn't present on Edge so I was just checking. We're looking to resolve this ASAP, we think it may have been caused since Chrome and Firefox had updates released. Apologies for any inconvenience caused.
  23. Yes that may be the case, you could keep your search radius the same then just set ping assist to 20 in the mean time. Do you see the same display error in Microsoft Edge?
  24. Yeah that's correct, essentially just disable filtering mode.
  25. No need to worry about that, it will work the same regardless of whether filtering mode is on or not. It's a cloud issue and isn't specific to your router, we're actually pushing some updates today that will fix it.
×
×
  • Create New...