Well, as soon as I revert to current firmware it all works. Will check again once an update is available weather it's fixed. Maybe somebody else on Windows 10 and steam or bnet games can check if they get the same moderate Nat. Thanks
Try again using the updated command (
-d) in post #17. It should provide more information.
I'm sticking with the previous fw so I can have open Nat in games.
It's possible, but that does not help me in figuring out what is going on. I know that IGD2 was enabled in this new build, and I'm specifically looking for info as to whether the miniupnpd author resolved the Windows compatibility issues that were previously present or not.
Mar 20 12:46:29 miniupnpd[29564]: version 2.3.3 starting NAT-PMP/PCP UPnP-IGD ext if eth0 BOOTID=1710899189
Nothing has changed there, it's still the same NAT implementation that has been there for years.
Upnp just doesn't work for gaming hence the moderate Nat type on Windows. Anything else I can try? Basically upnp is not working on this build for games. So it should probably be noted on the front page.
UPNP merely forwards a port in the firewall. It has nothing to do with NAT type.
Basically what's happening is that upnp isn't working correctly with Windows for games. A moderate Nat type message appears in games when the ports needed for said games isn't open or being forwarded. You mentioned that the router received no request from Windows in my previous log which tells me that upnp is just broken on the router in this alpha. Maybe you can test it yourself by downloading a game on steam which required ports to be opened to play. I will revert back to the previous firmware as it seems I can't be of anymore help. Thanks
"Moderate NAT" can refer to a wide range of "issues", some of which are trivial and don't affect online gameplay. The problem is Microsoft does not specify if their complain is whether a port isn't forwarded, or whether you are using Symmetric NAT rather than Fullcone NAT and are running multiple consoles.
I don't own any online game, and all of my machines are also under Windows 11. And Microsoft discontinued their XBox companion app that allowed to report the NAT type for Xbox-based gaming, so I have no way of testing it.
Moderate or strict Nat types only mean 1 thing, ports aren't forwarded. Its got nothing to do with xbox. It's quite complexing as this could be checked quite easily on your end with a very small free game on steam. This affects Windows 10 and 11 on my testing.
Can you specify one? I have no idea which specific games there actually requires to locally open ports.
Upnp works with my son's PS5 specifically Call of Duty, I know it's not windows 10 but you can not generalize that it's not working with games. Although the usual IPv4 port forwrds/mapping doesn't show in the port forwarding system log in this build. Maybe now it's using IPv6 port mappings/forwards since @RMerlin enabled that feature.
That's because playstion consoles use a fork of freebsd. The issue is with Windows systems. Call of duty has never used ipv6 for game servers, all of them are ipv4 and fully dedicated.
You said it works with windows 11 and not windows 10? So there must be different upnp implimentation between the two.
I tested w11 yesterday also and it doesn't work.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!