Netduma Fraser

No basically the DMZ passes all traffic through to the device you place there so on the VM it'll pass all traffic through to the XR which is what you want and then from the XR to the console. You may be thinking that may then negatively affect devices on the XR with the console in the DMZ but I haven't seen that be the case in reality.

They're mislocated on the map that's all, we'll retest it and move them, I'll let Alex know

What is your issue exactly as I'm still not sure on that? No that's not the case, they will be mislocated on the map, if you provide the IDs of them we can get them correctly located.

Without the Geo-Filter you say you're seeing 22ms, is that to the server you suspect is to the Spanish server or to another server? If you can provide the IDs for the mislocated servers we can get those correct which will make them easier to connect to.

That's not a Geo-Filter issue, there are multiple servers clustered in the same location, auto ping will ping whatever server you connect to

Try this: 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 better.

Could you provide a screenshot of a completed Connection Benchmark test please? Have you experimented with the Congestion Control percentages? 70% is the recommended starting point but may not be the best value for you. You can leave Bandwidth Allocation at their defaults, just reset the allocation. Would suggest setting the VM to router mode with the XR in its' DMZ, I found with my VM hub that modem mode was a little unreliable.

That's probably because you're using Ping Assist exclusively which it wasn't designed for, it's very restricted doing it that way, it was meant as an assist to traditional filtering. The way Ping Assist works is it takes the first ping response from a server and determines if it should be allowed or blocked so you could have a server that is allowed that ping at or under your limit 26ms in this case but then subsequent pings are higher. Likewise you could have it the other way where you miss out on a server as the first ping is higher than your limit but then settles below it but it would already be blocked. I would suggest using your radius exclusively with PA set to 0 if you're wanting to force specific servers.

You do already have access so you can find it and download it from here: https://forum.netduma.com/forum/144-netduma-r2-early-access/ You don't have to factory reset but in a scenario where the firmware changes a lot such as going from the official release to this beta release I would recommend it. As it is a beta there is always the chance you will encounter issues and this beta is no different, you could wait for the next version to release as in theory it should then be more stable as we fix bugs that have been reported.

The Geo-Filter doesn't go down, it shows connections that are available to you, what exactly is the issue?

He's really busy at the moment with an internal deadline so it is a bit delayed, I will remind him

Ping Heatmap just pings servers, it doesn't determine what you can/can't connect to which is why you're still able to play on them. We'll get an update done.

I think you'll need to hold the reset button for 30 seconds, then wait 4 minutes before accessing the interface and it should load then

When did the issue start to occur, was it after configuring HVPN?

Go to the System Information page and then in the Rapp panel menu ≡ change the retries to 5, reboot from the interface, wait 2 minutes before accessing and see if it works then please.

You don't need to adjust MTU or DNS, they will not have a significant effect on gaming, best to focus on the Geo-Filter and QoS for the best experience

Could you provide a screenshot of a completed Connection Benchmark now you've fine tuned QoS and also of Ping Heatmap once you've pinged the servers for the game please?

Sounds like the DHCP issue, 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 the disconnects.

Unfortunately not but the 450 version will be coming

It's not currently possible to block YT ads using the Adblocker, it's not as easy as other ads but it's something we hope we can workaround

How much packet loss is it showing? What are your Congestion Control settings? What is the model of the modem/router the XR is connected to and are ALL devices connected to the XR?

The log is primarily for the developers to help diagnose any issues that require further investigation, as such it shows a lot of normal background processes which can look like issues but this is a common one, no need to be concerned. You can largely ignore the log.

WiFi won't be the best way to play but try these suggestions, they may help make it more stable. Disable Mirror Mode, give 2.4/5GHz different names and apply - you'll want to connect to 5GHz specifically for speeds Use a WiFi analyzer to find the least congested channel and change to that Experiment with the widths to see what gives better results Ensure it's in an elevated position - not on a metal surface Ensure there aren't any electrical / wireless devices e.g headphones etc within close proximity ~3 feet if possible Set the antennae to this position _ | | _

When did this issue first start to appear exactly? Was it by any chance after deleting a device from the Device Manager or adjusting a setting for a device? Most likely you'll need to factory reset in order to clear that error

The way Fortnite works is that it only tries to connect to a server when you're actually loading into the game and so that is the only time it can be blocked so you are kicked back to the lobby. For Fortnite it's best to disable filtering mode but still use it to find out what server you're on, if it's too far away then you could quit and re-search until you find the server you want. This would actually be quicker than letting the Geo-Filter kick you.