I am refering to this problem
https://www.bungie.net/en/Forums/Post/223866092?sort=0&page=0
Over one month and nothing changed. This is such a nuisance.
And yeah, when I use my mobile with portable hotspot I got connected in under 10 seconds.
My provider is Unitymedia Germany, and that's their normal consumer product, native IPv6 connection with DSLite for the IPv4 connectivity. Before the Age of Triump (2.6.0.1) patch everything was peachy, so there has to be some new network code in the patch which creates this bug.
Can Bungie please comment on this!?
-
Hey Headhuntr, diese ganze bullshit peer to peer multiplayer Geschichte kannst du einfach vergessen bei destiny bei destiny2 bei Call of Duty immer das gleiche nur weil diese Juden Firmen wie Activision den Hals nicht voll genug bekommen und die ganze Kohle Ihren Aktinären in den Arsch geschoben wird. Und das Beste ist Sie versuchen den Spielern einzureden es liegt Ihnen weil angeblich Nat closed Port nicht offen anstatt zuzugeben das peer to peer nicht funktionieren kann. Die Verbindung ist immer nur so gut wie das schwächste Glied. Oder glaubst bei Counterstrike oder WOW hat man auch NAT Probleme? : D Wegen deinem DSLite prop melde dich bei mir kann helfen. Zauberwort Bridge Mode Gruß Krieg
-
Edited by RAIST5150: 5/16/2017 4:37:38 PMGame is using IPv4. Don't recall if the Bungie Inc subnet even puts v6 addresses out there...been almost a year since I did the dig. Your console may be stalling on failed v6 lookups and such before it goes back to run v4 addresses. May be able to resolve it yourself by disabling v6 on the router. Most of the U.S. is seriously lagging behind on v6 support these days. [B][i]Edit:[/b] Bungie's ASN doesn't announce any v6 prefixes. The subnets with Zayo may have them in reverse lookup and all, but the Bungie ASN itself doesn't appear to have any registered... so you'll need to get around the v6 timeout from your end[/i]