Netduma Fraser

That firmware is just for disconnects so you may encounter other issues with it but we're just concerned with that aspect - that firmware won't be used as a basis for next updates and we've already released a later one

I would argue resolving actual issues would be a higher priority, however, if it was as easy as just putting a control option in there then we would. From what I gather it's a kernel level change and not something that can be toggled on the go.

Okay keep us posted, we've had good results so far

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. I'm guessing you may be playing on PC using Game Pass is that right?

The exposed host is the DMZ essentially - check the IP the fritz is giving the R3, is it the same IP you entered?

Remove the port forwarding rules then and DMZ if you've done it. What is the model of the modem/router the XR is connected to and how have you set that to ensure all traffic flows to the XR? E.g. XR in its DMZ, modem/bridge mode

It's very likely because of that reason, we can't ping it properly so we've done a trace and 9ms was the last response received - if you check on the server when connected it should show you the ping method - direct or traced - I suspect it will show traced. If you see that discrepancy again check the ping method, I bet it'll be traced every time.

Most game servers will not respond to traditional pings so it is likely it will timeout on PingPlotter, we also don't give out any IP addresses

In WAN Settings set NAT to Open, does that resolve the issue?

Check the IP on the device itself then check on the device manager for the device you think it is, do the IPs match?

Can you save the logs when it happens please?

That's the purpose of using that specific VPN, there aren't any VPN settings to change necessarily if it is connected and location appears correct, try a different server

You're using a VPN so the ping will generally be high but we don't support getting around SBMM so it's not something we can help with specifically

The Ping Heatmaps are an estimate really, they won't be pin point accurate and you'll get a more accurate ping on the Geo-Filter

In a way it's quite promising as speeds should always increase with SmartBOOST disabled so the fact it's high with it enabled is a good sign that when sorted you'll get good upload speeds disabled.

It seems from your new post that you're using PPPoE also is that correct? If so it's more likely that than the VLAN causing it. It's something the team will be looking to improve but glad to see it has improved somewhat with the new firmware, I'll have them look into it.

Added! https://forum.netduma.com/forum/144-netduma-r2-early-access/

I don't know what your internet requirements are so it's hard for me to advise without that. Do you require PPPoE/VLAN etc for a connection? The easiest thing to do would be to put the R3 WAN IP (found on the WAN page) into the DMZ option on the fritz.

Great thanks, do try the new firmware in Early Access we posted today but otherwise if you click continue anyway can you get past that screen?

Reboot then try again please, I've also given you access to the Early Access version which should help with that issue. If you're using the DMZ you can't port forward as well, it's one or the other. https://forum.netduma.com/forum/151-netduma-r3-early-access/

That's great to hear, thanks for the update! That has been requested before so will likely come in future. It's not necessary to do factory resets after updates now but if you encounter an issue that would be my first suggested step if you haven't done one.

All I'm seeing is a black image?

The new game yes - an update to the existing game no

No other routers at all you could try this with?

No ports specifically, it's just the entirety of the device, you could say 1-65535 TCP/UDP which is the entire port range.