{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
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]
-
4 RepliesThe network vlan IPs should only be valid in so far as the host network is concerned; as soon as it leaves that home net (Bungie systems), it will encounter additional layer 1 / 2 items, and the IP address will be managed by them instead. Additionally, the outgoing IP will be determined by the lan / wan interface and management of the host switch / router / modem. Even in a tunnel connection, which I don't believe we are seeing in the capacity you originally suggested (as that would imply a VPN connection), you are connecting to a domain most of the time, not an IP. The reason for this is IP addresses don't have to be unique by their nature. Ask anyone ever accused of pirating, the primary defense is always that an IP address is not a concrete indicator of any one computer). Are you 100% certain that what you are seeing isn't either an IP conflict between your modem and routting equipment (which is a common issue, typified by failed connections, constant resets on lease renew attempts, etc.), or that you aren't seeing the ISPs hardware as the incoming connection IP? I'm not saying you're wrong, please don't misunderstand me, but I am applying the knowledge I use in my work every day to further analyze the issue.
