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

    UPnP Weirdness: Destiny2... A little help please.

    Scheduled Pinned Locked Moved
    NAT
    2
    2
    544
    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.
    • M
      mcraven
      last edited by

      I'm sure I'm missing something.

      UPnP is enabled and (for now) allowing access by default. Destiny2 keeps reporting "strict" NAT type with port 3097 as Router Internal Port.

      When I look at the UPnP Status in pfSense, there is no rule listed (expecting port ~3097) and another higher port never opens up for the actual gameplay.

      Grrrr... any suggestions as to what I might be missing?

      H 1 Reply Last reply Reply Quote 0
      • H
        hellegaard1 @mcraven
        last edited by hellegaard1

        @mcraven Most likely that your ISP is using a private address to serve your system a CG-Nat IP. There is a known problem with the implemented version of miniupnp, that disallows the use of private ip's for upnp on the wan side. If you check your system logs, you should be able to find the error.

        Port forward manually or 1:1 Nat is a work around for now.

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