Netduma Fraser

Give it a factory reset as it'll be a big change from the version you were on then check again please

It does work, you most likely need to adjust your settings. How have you set up the x82 to ensure all traffic flows to the R3? E.g. R3 in its DMZ, modem/bridge mode. Are ALL devices connected to the R3? Can you provide a screenshot of your Geo-Filter page please?

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

HybridVPN is available on the update - it's in the Settings menu

I'll see if the team can do it this week

If you disable Steady Ping on the Geo-Filter your ping will likely go back to normal. Could you provide the logs when you notice that happening please?

We actually released it publicly today, see if that resolves your issue https://forum.netduma.com/topic/55635-new-r3-firmware-40219/

Browser based tests aren't necessarily the best way to test I'd suggest testing with downloads while following: https://bit.ly/bufferbloat-test 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. This is more of a real world test as you're actually doing traffic you would normally do.

I can't see how that would affect it at all honestly but I will pass that onto the team to have a look at.

Get access again and then upgrade as soon as possible, the goal is to get off that firmware version as it should be more stable for you on the latest

I'd suggest upgrading to the latest firmware we just published here: https://forum.netduma.com/topic/55635-new-r3-firmware-40219 and see if you still get the same issue

I'll add it to the list for the team to look into, thanks for the request!

I can get the team to take a look at the eth delay. It might be you need to re-adjust your QoS settings on this version as it's a bit of a jump from .170 so the same settings may not apply. If you haven't factory reset in awhile as well that would likely help

Yeah it's going to take a bit of time for that as they're using proxies/relays so we need to try and work around it

Thanks for the feedback: By taking ages to register do you mean if you turn on a device it takes a little while for it to get a connection? If so how long? Can you get the logs when you get a disconnect please? We're aware we need to do more work on IPv6 What is your ping to these games? Did you do a factory reset after upgrading to this one?

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 2 minutes and see if that stops it.

Remove the R3 from the modem so just your PC and power is connected to it then try to access it

Upgrade to the latest firmware and see if you get the same issue https://forum.netduma.com/topic/55635-new-r3-firmware-40219/

That would make sense as no other devices are connected - if the performance is the same and on the R3 that's with QoS & forcing the closest server it sounds like a game side issue

It's the exact same as the one in Early Access so if you're already on it there is no need to upgrade - unless you want to get rid of the remote logging

We just released it publicly: https://forum.netduma.com/topic/55635-new-r3-firmware-40219/

Are you able to access using the mobile app at all?

We do need to spend more time getting better compatibility for the game as they're using proxies/relays which make filtering quite difficult and this will require time so we can't 100% guarantee filtering will work all the time. Try this though: Quit the application/game/client completely Remove device from the Geo-Filter Give PC PlayStation Device Type in the Device Manager (if on PC) Resync from the Geo-Filter Map menu Re-add the device to the Geo-Filter with the manual option Set up the Geo-Filter how you like Wait 2 minutes Boot up application/game/client Then see if it works any better.

Could you clarify precisely what is happening with the WiFi?

Right click the page, then go to Inspect (Element), on the window that appears click on the Network tab. Then click the checkbox to disable cache. Then click and hold the browser refresh button, and click Empty Cache and Hard Reload. Then see if it loads correctly please. If not, clear your browser cache/cookies and see if it correctly loads then please.