[tolien]

> Hosting a website behind a NAT isn’t as trivial as it used to be, and for many it’s now impossible without IPv6.

The example I keep coming back to is multiplayer games like Mario Kart, where Nintendo tell you to put the Switch in the DMZ or forward a huge range of ports (1024-65535!) to it [1].

If you’ve got more than one Switch in the household, though, then I guess it sucks to be you.

1: https://www.nintendo.com/en-gb/Support/Troubleshooting/How-t...

[DrewADesign]

To require that, the person would have needed to disable upnp on their router. I’ve played tons of multiplayer games on the switch and upnp handled it seamlessly on the 7 or 8 home networks I connected it to over its life. Never once even had to think about it.

So yes, if you disable the requisite, standard, built-in feature on your router, you may need a pretty annoying workaround. Weird!

What percentage of users do you imagine disable upnp? Let’s be real. This is a problem that your average user will never, ever experience a problem with.

[tolien]

No they wouldn't. UPnP is not requisite, certainly not standard, or necessarily built-in. For example, the router I've got doesn't implement UPnP. It's not unusual for it to be disabled, because it's a security issue that something with no authentication can punch enduring holes out through NAT. It's also irrelevant in a scenario where the ISP's using CGNAT.

I'm sure the Switch deals with conflict resolution with multiple consoles on the same network too but shrug it's another example of how NAT is a pain and also contradicts your assertion that incoming connections would be a breach of ISP ToS [1].

Edit: A quick Google suggests the Switch originally didn't support UPnP, and the Switch 2 now supports IPv6.

1: https://news.ycombinator.com/item?id=46484604