Cannot get an Open NAT

[Backpack]

So per a previous issue (seen below), I am not able to consistently use the 2.4ghz wifi network of the duma. Because of this, I took my comcast modem out of bridge mode and enabled DMZ, placing the WAN IP found in system info into the DMZ of my ISP modem. This is allowing me to use both wifi's of my ISP modem/duma which is necessary. However now, I am unable to get an open NAT while using the duma for gaming. At first I had a strict NAT, but after enabling DMZ on the duma and placing my PC's IP in there it moved to moderate, but that's the best I can get. I am trying to set up port forwarding for the PC but through other posts, the UPnP should be doing this automatically (which I believe it actually is as it shows "DemonwarePortMapping" under UPnP with my PC's IP and the port info. So beyond this I am not sure what to do. Is it even possible to have open ports when using DMZ on my ISP modem? I simply cannot use bridge mode anymore though, as my devices are constantly disconnecting multiple times a day as the duma drops internet. Also also, the speeds of the duma are immensely less than my ISP modem (300mbps on the duma, over 1gb via ISP). This is with a brand new, and multipe cat8 ethernet cables, in bridge mode, and in DMZ. Soo not sure what to do here. I want to keep using the duma as I LOVE the geofilter tool, but I might just move back to my ISP modem/router at this point.

[Netduma Liam]

I'd suggest removing the PC from the R2s DMZ, this could be a bit of a security risk.

Realistically you should have an Open NAT with just the R2 in the DMZ of the ISP router. Make sure the WAN IP is also reserved for the R2 otherwise the WAN IP may change and you will no longer have the R2 DMZ'd.

Please also make sure you disable any port forwarding rules you've created on the ISP router in trying to resolve this issue, that may cause confusing with the DMZ enabled.

When testing if this has worked, I'd also suggest disabling filtering mode in Geo-filter just to be sure.

[Backpack]

Nice. Disabling the port forward I had set up on the ISP modem fixed the issue. Thank you!