Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Nintendo Switches (2) - Getting NAT type D and connection issues

    Gaming
    2
    3
    113
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      BMD
      last edited by

      Have two Nintendo Switches, have been running pfsense for a few months now after my home router was acting up, and mostly things have been running well. Did notice that Splatoon would often get a lot more connection errors, but that was about it (and about the bulk of the online gaming for the switch, mostly everything else is single player gaming). Recently tried firing up MarioKart for the first time in awhile and we can't get any connection in that game at all online, error 2618-0516, which led me down the NAT error route. My troubleshooting thus far:
      Set reserved IP's for these devices in DHCP (PiHole runs my DHCP server)
      Under Firewall -> NAT -> Outbound
      set to HybridNAT with the following rule for StaticPort (Believe this should take effect for the range of IP's needed)
      16708d7d-de0d-43e1-b590-4e098fc3eab5-image.png

      and also enabled upnp (though saw post saying this may no apply for Switch anyway) which the following for approval
      b5d4f71b-3424-4838-be01-7703333f573c-image.png

      Always end up getting NAT D and connection errors. For a test I pulled out my 10 year old backup wifi router. Instantly got NAT B, and was able to get right into a MarioKart race online. Anyone have any suggestions on what I might have gone wrong or be missing?

      1 Reply Last reply Reply Quote 0
      • U
        Uglybrian
        last edited by

        Have you read through this yet? https://forum.netgate.com/topic/112631/nintendo-switch-needs-static-port-on-its-outbound-nat

        Try changing your CIDR from a 29 to a 32

        Using the settings, the home Nintendo switch is able to get to NAT 2. No universal plug-in play is necessary, at least for me.

        B 1 Reply Last reply Reply Quote 0
        • B
          BMD @Uglybrian
          last edited by

          @Uglybrian The /29 was to try and get the range of IP's for both of the systems and their docks (2 Docks hardwired, and then the WiFi of each unit).

          I think I actually managed to track this down to an issue with the WireGuard instance I had running for my phone to VPN back with, as once I disabled that my connections were fixed, getting NAT B and was able to play online for quite awhile without incident.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.