Jump to content

Netduma Fraser

Administrators
  • Posts

    85342
  • Joined

  • Days Won

    1800

Everything posted by Netduma Fraser

  1. In the Geo-Filter menu you can disable it there. It can happen with other games as well but due to how Fortnite filters (I alluded to it above) it's going to favor you getting into a game rather than kicking you out even if the server wouldn't be good.
  2. If it's a DDoS attack then that isn't anything we could help with but In LAN Settings, set the DHCP range to start at .50, then assign reserved IP addresses to devices between .2 & .49 so they're out of the DHCP range, apply, reboot from the interface, wait 4 minutes and see if that stops the disconnects.
  3. Good to hear, thanks for the update!
  4. It's because you have Geo-Latency enabled, though I would suggest keeping it enabled otherwise you'll block a server outside the radius and have a very long wait for it to kick you back to the lobby but you can try that if you wish by disabling it
  5. Hold the reset button in the back of the router for 30 seconds, then wait 4 minutes before accessing the interface - then use admin / password for the interface login credentials and you should get in
  6. It is yes, I've added you if you'd like to try it: https://forum.netduma.com/forum/144-netduma-r2-early-access/
  7. Are ALL devices connected to the R3? 50% is very low for Congestion Control - I'd suggest testing with downloads while following: https://support.netduma.com/frequently-asked-questions/legacyfaqs/test-your-ping/ start with a high value e.g 95%, test, decrease 10%, test, decrease 10% etc, until you get to a value that is pretty good, then try 5% either side of that value to see if it can be improved. Important to note that Download/Upload on CC don't have to be the same value & you may have a better experience with differing values. Once you've got good values check the game again.
  8. You already have it https://forum.netduma.com/forum/144-netduma-r2-early-access/
  9. It's unlikely based on how the feature works but never say never
  10. Presumably both being open is pulling a lot of the browser resources - I know for example that Chrome used to at least be super CPU intensive regardless of what you were doing
  11. NAT Type 2 is open, it just means you're behind the router, it's exactly the same as Type 1 otherwise. It will only show Type 1 when you're directly connected to your modem with the console.
  12. You've still got your set speeds at 100/100, update those to 1000/1000 and then also do a test on speedtest.net - what do you get then?
  13. There will be one server that is an authentication server being blocked when that happens, you may need to allow it a few times as there will be multiple there
  14. Disregard my last message, they tried again and were unable to connect again. It's the public IP, it's not visible on the Netduma Interface. You are using another modem/router above the R3, how did you set it, in modem or bridge mode or did you put the R3 in its DMZ? Please take a screenshot of what you did.
  15. I reported this yesterday again so we'll look into it
  16. That's not the IP but I got it from your post, please keep everything the same, they weren't able to try again today but they can try again tomorrow
  17. I was using the Hub 3 I think so I'm sure they've come a long way
  18. Hello, the same answers apply from your previous topic on this: https://forum.netduma.com/topic/57618-london-servers-won’t-stabilize
  19. IPv6 seems to be something we're constantly trying to improve so I have hope!
  20. You can try disabling the protection options in troubleshooting settings, that may boost the speeds slightly but it's unlikely to be significant. In terms of the bufferbloat it's possible you'd need different Congestion Control values for IPv6 vs without
  21. The way the filtering works in Fortnite is that it only tries to connect you when it loads in after the pre-game run around lobby and so that's the only time we can block the server so it'll just kick you back. 2 options: Disable the filter and use it to determine where you're being placed and quit if it isn't the server you want - it'll be quicker than letting it kick you Upgrade to the DumaOS 4 beta and try with Geo-Latency that might give you better results - let me know if you want access
  22. I've chased them again hopefully they will get to it soon
  23. The DHCP lease is something for NG, it's been around a long time, it's unlikely they'll resolve it now tbh. DPIclass we're looking into currently, hopefully it'll just be a cloud fix
×
×
  • Create New...