It does, these docs are for people for whom upnp has failed.
The wide port range I think is Nintendo throwing their hands in the air and not actually knowing what ports third party switch software uses
The wide port range I think is Nintendo throwing their hands in the air and not actually knowing what ports third party switch software uses
Most readers of HN will understand (or at least understand the goal of) the checklist for debugging network issues.
Skipping straight to Port Forwarding eliminates any issues on whether UPnP is actually working correctly. Growing up, some of my friends had routers struggled to handle UPnP correctly. If I knew they were the only one needing port forwarding, I'd simply turn that on for them instead of trying to figure out if UPnP was actually working correctly.
more than likely i'd think this is for enabling inbound responses to outbound ephemeral ports given the port range
Unless you're doing something like active FTP where it's replying to a different port than the one the request originated from. Which would be a interesting choice for a console designed in like 2018.
Stateless firewalls, however, need to have explicit rules for UDP traffic. So that’s what Nintendo are addressing here.