Sorry for crossposting into another subforum, but I think this needs to be seen!
I did some analysis regarding permament network-issues when playing Destiny 2.
Even if Destination NAT (aka Port Forwarding) and Firewall Settings (L3,4, IPS) were done properly, I was facing a lot of disconnects, lags and some general weird network related issues.
Yesterday evening I found the root cause of this problem.
Bungie Servers are not only talking with their public IP, but also with private IP´s with the PS4.
I guess there´s some unencrypted Tunnel established, therefore the private IP´s are visible.
Bungie Hosts belong to Network-Ranges like 192.168.0.x, 192.168.2.x.
The problem is, that a lot of home-networks are using these networks - so we are facing routing issues due to overlapping networks.
In my case I added a policy route to always use the WAN gateway for outgoing connections from PS4, but users with 'normal' equipment can´t workaround that easily.
They would have to change the internal network-range in order to get Destiny to work correctly.
Bungie, please change the network communication behaviour.
Either use public IP´s, or in case of tunneled traffic, use uncommon private network-ranges so that users won´t experience such issues.
-
-
Edited by F8L ERROR: 8/24/2018 9:56:07 PMI'm having a similar issue on XB1, I keep getting disconnected at random times saying "I have no internet connection" and sometimes it won't let me log back in still saying I have no Internet connected. My connection is solid with open NAT and port forwarding but it got worse after the maintenance yesterday. Edit: well that last part could be due to XBL gaming and social issues even though all the other games work fine online. Also no error codes were shown.
-
Bumping this one as well. I hope they see it. This is the kind of bug that can be maddening to find. Having a diagnostic like that drop from the sky is a free win no dev should dismiss.