Netduma Fraser

Device Manager on the router - not on the PC

You click the PC you're playing on, the click the device type dropdown on the window that appears

Added

Double NAT indicates that the DMZ you set isn't currently correct - if you rebooted the R3 for example the IP may have changed - double check they are in fact matching. Console speed tests aren't always accurate - if a PC is getting full speeds the router won't be limiting you - I suspect if you do a download on the console it will go at your expected speeds.

Take the PPPoE credentials you would have put in the XR, remove them, access your ISP modem/router - switch it back to router mode and enter the credentials into its PPPoE setting. Reboot the modem, wait 2 minutes, reboot the XR, wait 2 minutes and you should have internet through the XR and QoS should work.

I was passing it on to the developers to have a look as they'd have a better idea. Most likely it's a bug that needs fixing rather than anything you can do specifically but do try the latest firmware.

In theory it shouldn't matter but as we've all seen gaming networking seems to be a different breed. QoS is traffic management so in theory if there isn't much traffic at the time to be managed that could be why

If the DMZ IP definitely matches the R3 WAN IP then try port forwarding and see if you can get an Open NAT that way.

That's not entirely true, there have been 4 updates in the last month alone in Early Access which you do have access to, as above I'd suggest trying the latest one posted.

I can't answer that at the moment but yes I expect it will go to R2 Early Access

It's actually already on the Geo-Filter it's marked as The Division 2/XDefiant?

Can you provide screenshots of how you've set them up in Adblocker/Traffic Controller please?

I'll check in with the team to see when we can expect it

Added

That'll be due to PPPoE unfortunately and I think that'll be fixed in the next version. In the meantime if you want to use QoS you'll have to have the ISP modem/router handle PPPoE instead of the XR.

Exactly as mentioned above, let us know if you have any trouble

As above it's available to be selected on the Geo-Filter, we're working on getting it added to Ping Heatmap currently, shouldn't be long

As mentioned above, NAT Type 2 is open but means you're behind a router. NAT Type 1 is also open but means you're behind a modem. It is not possible to get a NAT Type 1 through the R3 therefore and also would make 0 difference to gameplay quality.

The above setup mentioned is what we would advise in this situation, the R3 can control everything and you get that extra WiFi speed/range from the AP.

Remove the device from the Geo-Filter first, then go to the Device Manager, click on your device then change the device type to a PS etc then go back to the Geo-Filter and add the PC with the manual option. Also the way Fortnite works, you will only see a server being blocked on the map when you're actually loading into the pre-game lobby once matchmaking has succeeded.

What router/firmware version is this on? Are you typing your address in? If so manually click the location on the map instead - it doesn't need to be pin point accurate.

Are you actually able to access the R2 interface? If so, if you check the Device Manager table view, do the LAN ports show connected when you connect the console to them?

Is that the LAN IP you've changed it to? Does routerlogin.net work?

The Ping Optimizer servers may not always be available and so can fail sometimes, we're rewriting the feature as well currently. So would recommend changing Congestion Control manually for the moment. However, I've given you Early Access so you can see if it is more consistent on that firmware: https://forum.netduma.com/forum/151-netduma-r3-early-access/

It's not necessarily a thing we can add - do you see it working for normal CS2? Have you ever seen it work for Faceit servers?