PC NAT Type Moderate to Open
In System / Advanced / Firewall& NAT I have "NAT Reflection mode for port forwards" set to Pure NAT and "Enable automatic outbound NAT for Reflection" checked.
In Firewall / NAT / Outbound I have "Hybrid Outbound NAT rule generated" selected with the following mapping:
- Interface WAN, address family IPv4+IPv6, protocol any, source is set to Windows 10 PC alias / 32, static port checked.
I keep getting NAT type moderate and I'm trying to get it to NAT type open. Windows sometimes would say Teredo could not be qualified, so I used CLI to change the type and various settings:
Teredo Parameters --------------------------------------------- Type : natawareclient Server Name : win1910.ipv6.microsoft.com. Client Refresh Interval : 30 seconds Client Port : unspecified State : qualified Client Type : teredo client Network : unmanaged NAT : restricted (port) NAT Special Behaviour : UPNP: No, PortPreserving: Yes Local Mapping : XX.XX.XX.XX:60086 External NAT Mapping : XX.XX.XX.XX:60086
My ISP does not use IPv6 natively (WAN IP is IPv4 only). I also tested using a fresh Windows 10 VM connected directly to modem and got an open NAT type. UPnP is disabled and would prefer not to enable it.
Tried to see if enabling UPnP would work and I'm still getting moderate NAT type.
Disabled the port forwarding and outgoing mappings. Turned on UPnP and NAT-PMP port mapping, default deny is enabled, and used ACL for ports 1024-65535 on my Win10 device. Even 53-65535 does not work.
After rebooting my device shows in the UPnP status but still results in moderate NAT. Packet captures shows communication on port 3074. Firewall logs show 3544 was being blocked, but port forwarding that opened it up but still results in moderate NAT.
Can someone please provide insight? I've followed all the guides on this forum.
@fox-hound For me it's been COD MW2/3 that have always been the most difficult to handle. Before I upgraded to 22.05 (2.7.0) I never got more than Moderate NAT without using UPnP AND port forward of 3074. If I'm not mistaken I also had to use static ports in Outgoing NAT.
Now after the upgrade, UPnP handles everything as it should...