It’s been a while since I’ve played any games online with my Nintendo switch, and I quickly remembered the issues with NAT types on the Switch.

When I checked, I had a NAT type of F, which will not allow online gaming. I found the guides on setting up the Hybrid NAT rules in Pfsense, but my type was still F. I then loosened up my outgoing port rules for that VLAN, and got a NAT type of B.

After tightening them back up a bit and looking online, it looks like the UDP range 1024 through 65535 is expected for outgoing UDP traffic. Is that right? That is a ton of ports, and possibly no better than just enabling uPnP.

Do I really need such a wide range to be able to maintain this NAT type B?

  • UnverifiedAPK@lemmy.ml
    121·
    1 year ago

    Yeah, that’s just basically every unregistered UDP port… Not much you can do about it since Nintendo has struggled to understand the internet and its uses since the Famicom.

    And no, for the love of God don’t enable uPnP. It’s still pretty much the worst thing you can do.

      • UnverifiedAPK@lemmy.ml
        11·
        1 year ago

        While you’re opening most outbound UDP ports for just the switch, a uPnP vulnerability has the possibility of letting an attacker open ports, especially inbound registered ports (SSH, RDP, etc), for all devices.

        If you do everything right (wifi client isolation, if your WAP has that option) opening the port for the switch is “essentially” as safe as it can be. The safest being Nintendo listing their public IPs but I think switch games use P2P which is why they don’t.

  • Sophia@lemmy.vonbergcompany.de
    5·
    1 year ago

    As far as I remember the Switch doesn’t actually use uPnP. The only thing that I had to do to achieve NAT Type B was an outgoing NAT with static port enabled. If I understood right, NAT Type A can only be achieved if your device literally had a WAN address.

  • Damoun@lemm.ee
    3·
    1 year ago

    I put my Nintendo Switch into a DMZ/own vlan. It was simpler and so I can get a NAT type A on it.

  • Gray@lemmy.world
    41·
    1 year ago

    My best advice would be to make sure you enable static port mapping on your NAT rules. That usually helps a lot of NAT traversal things like games.

    And no, Nintendo doesn’t understand networking in the slightest and asking people to forward every single port is BS.

  • Brownian Motion@lemmy.world
    3·
    1 year ago

    the biggest issue with N.switch is that it requires static outgoing ports.

    i have not used pf in years (opnsense here so should be same) but what you need to do is set hybrid outgoing NAT, designate a static IP to the switch, and then tell outgoing NAT for that IP to use static ports, outgoing.

    by default pf\opn randomises the outgoing NAT port and that messes up the Nswitch royally. (especially online like MK8deluxe)

    most of what is being posted about uPNP and N.switch is not correct. As long as your firewall rules allow the switch to get out (lock ports if you want to, but its a console, so … why?)

    Nintendo servers simply do not like you joining a game lobby on outgoing 34567, and then starting the game on 23456, and then turning a corner on lap 2 switching to outgoing port 18845.

    • computergeek125@lemmy.worldEnglish
      1·
      1 year ago

      Can confirm that also works on OPN

      Static outbound is a feature I wish more firewalls had because it requires the targeted device to send outbound once before it accepts incoming (or at least that’s my understanding)