Jump to content

Netduma Liam

Members
  • Posts

    7651
  • Joined

  • Last visited

  • Days Won

    131

Everything posted by Netduma Liam

  1. Could you please set the two sliders in Congestion Control to 70% and then select 'Auto-enable'? Check that the DumaOS classified games rule is also enabled. Could you also please share a screenshot of a completed Connection Benchmark? Temporarily set Congestion Control to 'Always' before running the test.
  2. OK, would you mind if we repeat the process again but this time I'll enable some remote logging on your R2? Then, next time it happens, you can report what time it occurred and we should then be able to see something around the time the error occurred. Let me know and I'll get ahead and enable that, it will reboot your router in the process.
  3. Apologies for the delay, just had a look around, everything looked to be running properly. I've restarted DNS and rebooted the router afterwards, can you let me know if you're still having the same problem?
  4. Could you please completely disable QoS from the three-line menu in Congestion Control, then run a Connection Benchmark and post the results? With the Wi-Fi, were you using SmartConnect, or did you have the networks separated? Are the devices struggling to connect IoT or smart home devices by chance? I had a similar issue recently and the best solution is to disable SmartConnect so you then have two separate networks.
  5. All good, always will work great too! Let us know if you have any other questions.
  6. Destination IP will be the IP address of the device you're gaming on. Select TCP and UDP for the protocol.
  7. I'd suggest auto-enable so your bandwidth isn't affected when you're not gaming.
  8. Do you have DNS configured in Windows? If so, please remove it from your adapter options. Otherwise could you please enable 'Remote access to tech support' from the WAN settings and I'll take a deeper look at what might be happening.
  9. Use it in conjunction with Congestion Control. Have that set at around 70% for both sliders and see how you get on.
  10. Sure! So Google "Halo Infitinite ports" and find the ports that Halo uses for whichever platform you're playing. Then, go to DumaOS and under QoS -> Traffic Prioritisation, add a new rule. Switch to the advanced tab and add source ports 1-65535, then the destination ports will be the range of ports you found from your search. Select TCP and UDP as the service and see how that works for you. Any other questions, just ask!
  11. You might find more luck manually adding the ports for Halo on your platform to Traffic Prio, if you're currently using DumaOS classified games that is.
  12. Maybe set Ping Assist back to zero and try again, that could be causing the issue.
  13. How strange! If you just enable 'Use upstream DNS' does it then work again? Could you clarify on which firmware you're having this issue?
  14. That's odd, can you double checking the Network settings are still configured this way? Have you added any devices or made any changes since?
  15. I've responded to your own topic on this issue.
  16. Check out this guide and follow the advanced section to see how to do this correctly: http://support.netduma.com/support/solutions/articles/16000087492--dumaos-optimal-settings-guide-hybrid-vpn Let us know if you have any other questions.
  17. Are you filtering servers in your area? Is filtering mode enabled? As Fraser mentioned, a screenshot might be easier. We don't know exactly when the new firmware will be released, we're working with our beta testers currently to iron out a few issues. After that it should be good to go!
  18. Sorry to hear this, if you're able to in future it may be worth TFTPing the current firmware to the router, this is about as close as you can get to a re-flash so it may resolve issues you're having. I'll leave the article for this below. https://kb.netgear.com/000059633/How-do-I-upload-firmware-to-my-NETGEAR-router-using-a-TFTP-client-on-Microsoft-Windows
  19. The cloud gets updated as and when it needs it really. We've got an internal tool that monitors how many servers are still responding and we update it when that gets too low.
  20. Welcome to the forum! Sorry to hear you're having these issues. Could you please reboot the XR1000 from the three-dot menu in the interface? Once you've done this, it shouldn't factory reset when it loses power and hopefully it'll resolve your issue of the error message too.
  21. Does that PC have a Wi-Fi card? It may be that it connected over both interfaces and has separate IPs for each. You wouldn't be able to remotely reboot a device from Device Manager, but maybe it'd be useful if you could force a new lease renewal or something. Thanks for the suggestion!
  22. Two IPv4 addresses, or one IPv4 and one IPv6? It may have renewed the IP and changed, but the old one is still visible in the Device Manager. Is this causing any problems? If so what are the symptoms?
  23. We're not sure yet I'm afraid, we'll keep you up-to-date.
  24. Hey everyone, In case you're not subscribed, we've just announced our new mobile view for DumaOS over on our YouTube channel. This now means that DumaOS is optimised for mobile web browsers, with the welcome addition of some really cool new features. We'll first be releasing this on the R2 in the form of a new firmware, shortly followed by the NETGEAR Nighthawk Pro Gaming and Telstra platforms. Here you'll be able to use mobile view from the web browser. The long term plan is then to integrate it into our own App as well as the native Apps of our partners, such as NETGEAR and Telstra. Check the video out here:
  25. Sorry to hear that, we fixed an issue which was causing disconnections for most people in the latest firmware.
×
×
  • Create New...