Jump to content

Netduma Fraser

Administrators
  • Posts

    87507
  • Joined

  • Days Won

    1946

Everything posted by Netduma Fraser

  1. Do you see the same on http://192.168.77.1 and http://dumaos ?
  2. We suspect they're using relay servers which makes it difficult - essentially connecting you to a server you can connect to in order to then connect you to a server that would normally be outside your radius and so that means we can't block it. The main issue with this currently is that we don't even see these relay servers on the Geo-Filter, this is something I've spoken with the team about to see if we can widen the net of what the Geo-Filter shows. If we can then see the relay servers then they could then in theory be blocked to prevent the issue happening. So yes potentially but it's not necessarily a simple thing to counteract (what I've said could be correct in which case it could be simple but could be more complex)
  3. Not really, it would be the same situation on that version as well
  4. Don't use the inbuilt test, just speedtest.net. Can you provide a screenshot of the overall QoS page please?
  5. Great to hear that! Ahh yes that is probably it, good to know, thanks for the report!
  6. Are you using HybridVPN at all or have adjusted any other major settings in the Settings pages?
  7. What is the model of the modem/router the R2 is connected to and how have you set that to ensure all traffic flows to the R2? E.g R2 in its DMZ, modem/bridge mode Are ALL devices connected to the R2? Have you entered your expected speeds into the router? How have you setup Congestion Control? What firmware version are you on? What speed test are you using?
  8. So it happened after upgrading to DumaOS 4? Also how do you have that firmware as you haven't been added to the Early Access section. If you downgrade to the latest public version do you get the same issues?
  9. I don't believe it's on the R2 beta actually, it was missed off by mistake so always a chance it will still work in future - we can see how the person above gets on using it on the R3
  10. Is SmartBOOST off fully where it completely disables the page along with prevents you adjusting Congestion Control? When it initially started was it after changing settings, doing anything specific etc?
  11. What is the model of the modem/router the R3 is connected to? Reboot your main modem, wait 2 minutes then reboot the R3 from the interface, wait 4 minutes then check again Nothing for the moment
  12. Just to double check, you managed to complete the Setup Wizard? Did it say it detected internet during it? You said via WiFi does that mean you do have internet via ethernet? Do you know if you require PPPoE/VLAN for a connection?
  13. Provide a screenshot of LAN & WAN Settings please
  14. Make to set it in bridge or modem mode or with the XR in its DMZ. You don't need to allocate the PS that much upload/download, gaming barely uses any bandwidth, reset the allocation and leave it at its defaults. You can remove the CoD series on prio, it'll be covered by Games Console. Congestion Control is high, you may want to consider experimenting with the values if these other changes don't provide any further benefits.
  15. That is an R2 specific DumaOS 4 bug yes, it should have defaulted to 0-0 and not been able to be changed so not sure how you were able to do it which likely means to revert it back to that and prevent it happening you'd need to do a reset.
  16. Added - it has been removed currently https://forum.netduma.com/forum/153-xr1000-beta-forum/
  17. When did the issue start to occur, after changing settings, updating, changing your physical setup etc?
  18. Presumably a reboot will restore functionality until it happens a few days later? Does this also happen with the bands merged that everything then gets forced onto 2.4GHz? The logs would be great thanks.
  19. Follow the steps above and you'll see it, let us know how you get on
  20. Awesome setup, those PCs are a work of art!
  21. Ahh yes it is because you're using the R2, that will come later. Though now I can see it, the reason for that is because you have ping assist set to 80. Any servers under 80ms will be allowed so if you want to force specific areas you should disable this/set to 0.
  22. You already have it, it's in the Geo-Filter settings, usually enabled by default check top right of the Geo-Filter page
×
×
  • Create New...