Just recently jumped back into Destiny 2 and for the most part things work well, but I have had a few odd disconnects and the occasional moment where someone seems to have desynced with me and then teleports to their actual location. Could be latency, could be many things. One thing I've noticed though is that my router is set up for UPnP yet Destiny 2 doesn't seem to be properly utilizing it and I'm left with a moderate NAT. Fortunately I'm the only person at my house that is a gamer so manually forwarding my ports isn't a problem for NOW, but I'll be moving in with a few friends soon enough so this current workaround won't be sustainable.
I've got a pretty high end router, running OpenWRT. I'm able to run detailed logs, wireshark, all kinds of advanced troubleshooting things, so I can supply whatever logs necessary to help troubleshoot this in the event that UPnP actually works on PC for others. I'm pretty solid at tech, but I'm not a software dev nor am I some infallible expert. It SEEMS to me that Destiny 2 simply does not ever make the request to open a port via UPnP. I have UPnP and NAT-PMP both enabled in my routers software. Any other program that uses UPnP simply shows up in the list on the UPnP section. It shows the device, the port, the software or software type, etc. My firewall is set up to be as minimal as possible while still being effective. Although this custom router software is significantly better than what comes with most routers, I've even tried an older router I had on hand with stock official firmware. Same issue, other UPnP apps work, but not Destiny 2.
I've been able to find a few other posts with similar problems and the only workaround was "yeah just manually port forward" but again, this doesn't work when more than one person needs ports open so it would be great to get to the bottom of this because presumably, this should be a very simple thing to fix when the functionality is all there and *supposed* to be working.
I am on Windows 10 x64 1903. No additional AV or firewall software is running and Destiny 2 is allowed in the windows firewall for both private and public networks.
tl;dr UPnP seems to be doing nothing, if anyone also on PC is getting open NAT with UPnP, it would be great to know more information about your network and pc configuration to see if we can figure out where the problem lies. Anyone else in the same boat with UPnP seeming to be broken, also share your information so we can make this more aware to the devs. Cheers.
-
Edited by pgwipeout: 6/7/2020 12:22:00 AMSo I just spent the time to figure out what is going on with Destiny 2 and UPnP. Destiny 2 is extremely strict with its UPnP implementation, as such the default OpenWRT miniupnpd configuration does not work. On the main configuration page, the importation options are below: Start UPnP and NAT-PMP service = enabled Enable UPnP functionality = enabled Enable NAT-PMP functionality = enabled Enable IGDv1 mode = enabled (The important option, Destiny 2 does not like IGDv2) Port = 0 (Allows automatic port selection) On the Advanced Configuration page, you must add the following options: Announced Serial Number : <Any integer you want> Announced Model Number : <Any integer you want> Presentation URL : http://<ip-address-of-router> Save and apply. Go to System -> Startup and restart miniupnpd, some options do not take effect until you do this. The ports that are needed are opened as they are needed, and OpenWRT automatically tears them down when Destiny 2 is shut down.
-
I'm also using OpenWRT and Destiny 2 does not seem to request UPnP leases. My Xbox does happily for Destiny 2. In any case, I only enabled UPnP temporarily to see if it would help with super slow zone transitions that started on Friday. There's a buffer overflow attack against miniupnpd, so you should probably avoid UPnP if you don't need it to support multiple game clients behind your NAT.
-
What is the name and brand of said router