When I had it running in parallel accidentally it sometimes was Open and sometimes was Strict, that's when I noticed it still making UPnP rules after I had the static setup running. ![]() Make sure to remove any previous UPnP config specific to this, or disable it. Although some of the fortunate Warzone players may easily change the NAT Type by performing a factory reset their Wi-Fi router as well as the gaming device, that’s not useful for everyone. "The STUN-based networking that PS4/Destiny want to use cannot work with PFSense's default behavoir of randomizing source ports."Īgain I opted not to use UPnP and went with manual port forwards. Now, if in case, your NAT Type isn’t set to 1 or 2 then it’ll be hard enough to change your Wi-Fi router from a Moderate or Strict NAT Type to Open mode. ![]() This post is what ultimately helped me out, the static port option being the missing link for me: I have Hybrid NAT selected for my Outbound NAT mode. Outbound NAT rule with source of Destiny 2 PC, source port UDP 30 with Static Port option checked.Inbound firewall rule on WAN interface (may vary) with IP of Destiny 2 PC as the destination and ports 3074/3097 (this should be auto-created assuming you went with the "Add associated filter rule" option when making the inbound NAT above).Inbound NAT Port Forward rule for ports 30 to IP of Destiny 2 PC. ![]() ![]() I was just able to get to "Open" without using UPnP:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |