Netduma Fraser

There are too many servers listed in that config so the router won't know which one you want to connect to. Remove all but one of the router line entries and try again.

Added

That's good to hear, thanks for the update!

It does work as a PC but the thing is the game changes so often that the service becomes out of date and so its a bit of a chase to keep it updated that's why I usually suggest the console method as that always works

It might be a scenario where it gets worse before it gets better - we'd be allowing them so probably a good idea to try allowing them all and see if it stops the issue completely

I'll try to get an ETA for you

That would be helpful thanks! If you're clicking allow on them then you can go back and re-name/ping them later so you don't need to try to rush a screenshot

If you click on the console on the Geo-Filter, is filtering actually toggled on?

That may be an error caused by Adblocker on your browser, disable that for the interface and then refresh

And it's still allowing everything outside? Have you made a traffic rule to allow ALL traffic to the console?

On the System Information page go to the Rapp panel, click the 3 lines option menu and change the retries to 5, reboot the router from the interface, wait 4 minutes then access and see if it loads please. Also: Disable Armor Ensure the browser isn't forcing HTTPS for the interface

We've removed the cloud we pushed on Friday, reboot and resync then check if it works better again please

Geo-Latency needs to be disabled, the Geo-Filter should be enabled before launching the game and don't change Geo-Filter settings when you're on the game already. Enter your expected speeds in manually and try again - ignore the built in speed test. I've given you access https://forum.netduma.com/forum/151-netduma-r3-early-access/

Good to hear. Yes the built in option on EE would be a good option too, you'll still have full use of the Geo-Filter on that one

It could be yes, directly connected to your ISP modem under the same conditions (same network usage etc) do you see the same?

Added - it has been removed temporarily. Added - it has been removed temporarily. Please make a new topic for your issues and we can help you there. Added - it has been removed temporarily.

Thanks for the report, I've passed it onto the team who have now removed that cloud update which will hopefully resolve it, please reboot the router from the interface, wait 4 minutes and then resync the cloud and let us know if that has resolved it. I've also given you Early Access to the DumaOS 4 beta, if it continues please see if this version stops it happening.

Thanks for the report, I've passed it onto the team who have now removed that cloud update which will hopefully resolve it, please reboot the router from the interface, wait 4 minutes and then resync the cloud and let us know if that has resolved it. I've also given you Early Access to the DumaOS 4 beta, if it continues please see if this version stops it happening.

@mr_kfed thanks for the kind words about me! I totally appreciate it's a frustrating issue, I wish I could say it was an issue on our side that we could have fixed but I can't unfortunately. If it's continuing after raising the bottom of the range then I would suggest giving every single device connected to the router a static/reserved IP in DHCP settings. Once you've done that then disable the DHCP server, reboot the router from the interface, wait 4 minutes then confirm you still have access to the interface and internet. Then in theory, the DHCP issue should not longer pose a problem as it's disabled and devices will continue to function with their permanent IP address.

Yes that is correct as far as I am aware. Everything should still work fine if you choose to go the PPPoE route. If not let us know and we'll look into it, then in the meantime you could switch to the other setup (if you're not returning the hub) - maybe best if you are planning to return that to have a grace period just to check everything works as you expect with the R3 handling PPPoE.

If you actually pay them for a static IP then I'm surprised you're still not getting an Open NAT. Are you in a country that may have more stringent restrictions on your network? If so then yes probably your only hope is a VPN, however, usually using a VPN won't allow you to get an Open NAT either but you may be able to get moderate which could be an improvement. Overall NAT really matters when it comes to connecting to people, as most games are server based now it shouldn't be too much of an issue. If you're playing with others it could pose a problem if they don't have an Open NAT either. PPPoE we're aware of that issue so we're working on it. Work around would be to have a different router handle PPPoE for the moment.

Do you get an Open NAT with your console connected directly to your modem?

Okay thank you!

Can't see the video, broken how exactly?

It's fine, if you were actually seeing packet loss it would appear as red bars on the bottom graph so you can ignore that. CPU hitting 100 isn't unusual unless it stays at 100 constantly