Jump to content

Netduma Fraser

Administrators
  • Posts

    86480
  • Joined

  • Days Won

    1864

Everything posted by Netduma Fraser

  1. I think you may have the wrong place but if not it would be better to contact them directly for support
  2. https://forum.netduma.com/forum/144-netduma-r2-early-access/
  3. Added, if it continues please make a new topic and we can help you there
  4. Either way, it's up to you, there won't be any conflicts
  5. No there won't be a conflict and has you don't have IPv6 there is no need to enable it
  6. That's simply incorrect It's a beta firmware that's why, if you upgrade to the latest public version that is based on this version you can do so without going to an intermediary firmware. If you go to DumaOS there I'm sure it'll work correctly
  7. We have it disabled by default on the Early Access version and I would suggest doing so generally if you're not using IPv6 but no it doesn't need to be disabled to prevent a conflict.
  8. Glad to hear you managed to resolve it, thanks for updating with your solution!
  9. So you're bypassing the normally provided AT&T ISP modem/router with the WAS SFP module correct? The Router speed test reported that but have you entered your actual expected speeds into it? What do you mean Congestion Control never works for you? SmartBOOST prioritizes devices, there are no servers involved. Where are you testing the speeds though, speedtest.net? Can you provide one of the specific sites you're trying to block ads on, not the tester please so I can attempt to reproduce?
  10. What is the model of the modem/router the R3 is connected to and how have you set that to ensure all traffic flows to the R3? E.g R3 in its DMZ, modem/bridge mode Are ALL devices connected to the R3? What are the speeds you pay for/receive? Have you entered those speeds into the router? How have you setup Congestion Control? How have you setup SmartBOOST? Where are you testing Adblocker on Apple devices? What speeds are you getting on devices when they're slow and where are you testing? Are they connected via WiFi or ethernet?
  11. What precisely are all the issues you're having? You mentioned a couple in other topics but I want to ensure you've put them all here so we can go through them properly
  12. No DNS doesn't have an impact on game performance
  13. Good to hear! DNS won't make a difference for gaming so unnecessary to change it. There isn't a backup settings function currently but it has been requested so may come in future.
  14. It's using servers provided by: https://speed.measurementlab.net/#/ As is shown on their site: "We are temporarily running multiple tests back to back to calibrate new measurement protocols. This means results may take a little longer to appear than usual." and generally their servers are not always available/the closest to you. I'd suggest adjusting Congestion Control manually instead to achieve the same effects (Ping Optimizer just changes these percentages). You can find it in Ping Optimizer > Advanced. We suggest starting at 70% and fine tuning based on your experience.
  15. I'll pass your comments along to the team for when they consider new hardware. We do like to keep the price point around the same though so it really depends on hardware cost.
  16. What is the firmware version you're on currently?
  17. Added https://forum.netduma.com/forum/151-netduma-r3-early-access/
  18. What's your exact physical home setup and how is it set to allow the XR to have direct access to the internet? This is a NTGR feature so we're not as knowledgeable on it but we'll do what we can to help
  19. There won't be no. It'll just be security fixes then, it's unlikely it's based on 3.3, I think it probably reached end of service before they did it.
  20. Good to hear, don't forget the Early Access firmware as well
  21. Thanks for the report, I'll pass it on to the team to update it
  22. That's normal, follow this guide to see if you have a CG-NAT https://support.netduma.com/docs/dumaos-3/open-nat/#cg-nat
  23. You shouldn't have a double NAT if the R3 is in the EE hub DMZ so I'd suggest checking the WAN IP on the R3 is the same as the IP entered in the DMZ. In that scenario if you need PPPoE for example then yes you can just put those details in and leave everything else the same. You may need to fine tune your Congestion Control settings a little more to get the same results you're used to but otherwise it would be fine. I would look into the DMZ thing though first as you can see reduced speeds and there is also a disconnect issue with PPPoE we're looking into. The R3 won't change any settings unless you change them so no need to screenshot. If you have a double NAT even after connecting to the ONT then you have a CG-NAT in which case you only have these options to resolve it: Get a static public IP from the ISP (usually a charged extra) Use a VPN (using a VPN generally gives you a moderate/strict NAT anyway, also an extra charge) Change ISP to one that doesn't use CG-NAT
×
×
  • Create New...