Netduma Fraser

Added

Added

Good to hear! As above you can upgrade and you shouldn't get the issue as long as you don't factory reset but if you just want to be safe then probably best to stay on the firmware you're on.

Please follow @Netduma Frasersuggestions above. I can only speak on the BGW 320-500 ports.  
On the AT&T BGW320-500 gateway, the yellow and blue Ethernet ports are both for connecting your wired devices, but they support different maximum speeds:
Yellow ports (3 ports) – Standard Gigabit Ethernet
Maximum speed: 1 Gbps (1000 Mbps)
Also works with 10 Mbps and 100 Mbps devices.
Blue port (1 port) – Multi-Gig Ethernet
Maximum speed: 5 Gbps
Compatible with 10 Mbps, 100 Mbps, 1 Gbps, 2.5 Gbps, and 5 Gbps devices.
If your internet plan is 1 Gbps or less, there’s usually no performance difference between plugging into a yellow or blue port unless your device has a multi-gig Ethernet adapter.
I have my Netduma pugged into the blue port of the BGW 320-500 and all my other devices plugged into the Netduma R3 ports. 

I don't know what the blue/yellow ports correspond to on the ATT router so I can't answer that. 
You don't need to change those advanced settings options. You can leave the lease time at the default for now.
Are ALL devices connected to the R3? Have you entered your speeds into the router? How have you setup Congestion Control? How have you setup SmartBOOST? What game are you playing? What platform are you playing on and how is it connected, via ethernet or WiFi? How have you setup the Geo-Filter?

Okay, I'll be waiting to hear from you.

Ok, I'll give it a try once I'm home and I'll let you know

Thanks Fraser, I’ll do some testing later today after work and report back what happens.

Good to hear you got it sorted, it was just a security update so it should have no effect on use whatsoever 

Yes you'd put 0. The ISP timeout must be set to 5 then, if they're otherwise unhelpful perhaps they could change the timeout for you just to see if the issue improves

Grazie a te 😊😊😊

Good to hear, thanks for the update!

Ah d'accord merci beaucoup pour vitre aide et votre patience !! ❤️

NAT is not something the Geo-Filter can cause being open or moderate. You either have an Open NAT or you don't. You do have an Open NAT. 
The Geo-Filter blocks the server to test your NAT - it's not causing a moderate NAT. The test because it is unable to reach the server defaults to showing moderate. When it is able to reach the server i.e. with the Geo-Filter disabled then it is able to show you Open. This does not mean you only have an Open NAT with the Geo-Filter disabled and Moderate with it enabled. The NAT is open in both scenarios, it is just the reporting that is different. 
@Krush can you translate what I'm saying please?

NAT is not something the Geo-Filter can cause being open or moderate. You either have an Open NAT or you don't. You do have an Open NAT. 
The Geo-Filter blocks the server to test your NAT - it's not causing a moderate NAT. The test because it is unable to reach the server defaults to showing moderate. When it is able to reach the server i.e. with the Geo-Filter disabled then it is able to show you Open. This does not mean you only have an Open NAT with the Geo-Filter disabled and Moderate with it enabled. The NAT is open in both scenarios, it is just the reporting that is different. 
@Krush can you translate what I'm saying please?

I tried that a while back...didn't work for some reason. I have no complaints about this router. It performs as advertised and the OS is awesome. 

Port forward 3074 for one device and 3075 for the other and then you should be able to get an Open NAT at the same time.

Good to hear thanks for the update!

Download the latest firmware from the NTGR site and then go to 192.168.1.1/adv_index.htm and that should take you to the NTGR settings where you can then re-upgrade the firmware. Close the tab, wait 4 minutes then access normally and see if it loads.

Added

I figured it out, i had my network selector in Fortnite to na east, once i put it in auto it went back to normal 

Do the same process but use this command instead please:
duma.RPCHandler.PromiseAsync("com.netdumasoftware.settings", "remote_access","true")
I'll have someone monitor the topic so they can try to upgrade you when you say you're accessible.

Thank you Fraser 

That's fine then. No that's not true, you're not going to stress the system too much by lowering the percentage lower than 90%.

https://test.libreqos.com/advanced/