JavaScript is required to use Bungie.net

#feedback

Edited by Spawn: 8/23/2018 11:38:02 AM
16

Network Issues causing disconnects and lags analysed - Bungie please address

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, issues with friendlist, and some general weird network related issues. Yesterday evening I found the root cause of those problems. 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 interface as 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. [spoiler]Moderator edit: This thread has been moved to #Feedback forum so that other Destiny players can weigh in.  [url=https://www.bungie.net/en/Forum/Post/139533839/0/0] See Cozmo's thread here[/url] for more information about the #Feedback tag and its uses. Feel free to private message the moderator who moved your post, link to topic for further clarification about why this topic was moved.[/spoiler]

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

View Entire Topic
  • I still haven't had time (or motivation) to investigate further, but there are a lot of thoughts in my mind I didn't write in the first post, as its not editable anymore. The question is why the PS4 tries to connect to those private IP's, which are not my hosts. udp/3074 is definitely destiny related traffic. I cant see the source traffic incoming on my edge device, only oitgoing from PS4 to private IPs. It could be a bug related to bad GRE encapsulation on the PS4 side, or related to incorrectly defined headers somewhere in the trafficflow. I will continue to investigate.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon