Netduma Fraser

Not long to wait now to find out!

.134 > Intermediary firmware > RC14 If for some reason you can't upgrade to RC14 from the intermediary firmware then update to RC10, then after that upgrade to RC14

I'd say so and it's very unlikely to brick the router. Just download the file, access the interface, go to Settings > Administration > Firmware update and upload the file. You can downgrade back again following the same process just with the older firmware file.

Killcams aren't always an accurate representation of what happened but rather what the server sees but I see your point. It's either the exchange or lag compensation working against you, if you use the Geo-Filter to force further away servers with a higher ping does your experience change?

Cabling is all fine, what is the issue you're having exactly? Have you accessed the interface and completed the Setup Wizard? You will need to do that to get internet

Turn what on? Do you mean how to access using HTTP? Use http://192.168.77.1 or http://dumaos to access as long as you've disabled the browser forcing HTTPS (if applicable)

I haven't heard back, I'll leave a message with them to do it tomorrow and post here once they've done it

It could still be the Geo-Filter causing the misreading perhaps - you may need to reboot the gaming device to double check. Otherwise in theory that could work, first try connecting the R2 directly to the Asus if possible and see if it is open then.

Just to clarify, it's the WAN IP of the R2 (found on the System Information page) that's in the ISP modem/router DMZ? The Geo-Filter can cause a misreading of the NAT status so close down the game/client completely, disable the Geo-Filter, reboot the console/PC then launch the game, does it appear open then?

Right okay so is your Asus router in the DMZ on your ISP modem and R2 in the DMZ on your Asus router? The mesh routers I assume just act like WiFi extenders, they don't give the R2 an IP address, the R2 WAN IP comes from the Asus router is that right?

That's fine, it uses different servers so it won't always show the correct results, it depends on your proximity to the servers and the routing to them. As you can see from speedtest.net the router isn't limiting you to the speeds shown on Benchmark so you can ignore them.

The Geo-Filter isn't enabled so you're just getting servers wherever the game wants to put you so you should enable that. Your Congestion Control percentages are quite high, try with 70% for download and upload

So just to clarify, there is one Asus router upstream that is part of a mesh of Asus routers and an R2 connected to it, is there any other routers/modem such as from the ISP?

Added

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

Most likely but that's what the R2 in the DMZ of the upstream router should resolve, was it the WAN IP you entered in? Unlikely as that would prevent the use of the features which is the point of having the R2 over other routers but it's not a definite no!

Have you ever had an Open NAT with this setup i.e. without the R2?

Where are you checking the NAT type exactly? In the game? If so this could be a misreading, disable the Geo-Filter then launch the game and see if it is open

Check the IP on the PC itself, then check in the Device Manager on the device you think the PC is, does the IP match?

Luego, proporcione capturas de pantalla de todas las demás configuraciones que mencioné y debería poder determinar la causa.

Unfortunately this is only available for the R2 currently but if you haven't done so yet there is a beta firmware available for the XR500 here: https://forum.netduma.com/topic/51611-new-xr500-beta-firmware-33535/

Could you provide a screenshot of a completed Connection Benchmark test as well as a screenshot of your QoS page please?

You may need a modem/router for the XR1000 to be connected to but assuming that isn't the case you can access 192.168.1.1 or routerlogin.net in your web browser to go to the XR1000 interface and enter any PPPoE details you may need to get online

This is most likely due to connecting to the interface with HTTPS instead of HTTP. Your browser may be forcing this, if you turn that on and force HTTP to the interface it should work without error.

El XR1000 con Armor tiene la capacidad de mostrarle estos ataques, seguirán ocurriendo y es posible que el módem/enrutador del ISP no los muestre. Si tienen registros en el módem, estos deberían aparecer allí. Los escaneos de puertos son bastante comunes, por lo que es posible que el módem del ISP no los marque, pero si cree que están causando problemas de red, el ISP puede bloquear las IP donde se originan los ataques.