JavaScript is required to use Bungie.net

Help

Help us help you.
Edited by PGC Psych0Dog: 4/5/2016 7:58:01 PM
2

Constant marionberry error, cant login anymore at all since months (Help articles dont help)

Im getting only marionberry since several months now, i have a rather uncommon network setup since about the same time. all other games i own (even on several other consoles) are not showing any networking problems. it is just destiny that cant get a grip on my network and i have no clue as of why. My setup in detail: Public Internet -> Cable FritzBox (Internal IP 192.168.178.1) -> network ROUTE -> 192.168.178.100[EXT] OpenWRT Router 192.168.1.0/24[INT]-> Internal Network (PS4, xbone, ps3, xbox360 etc) PS4 sits on wired gbit connection, internet line is 200Mbits down and 20Mbits upstream. Internal LAN network is all Gbit compatible. upnp port mappings work fine, ps4 shows me nat type2 in connection test analysis screen. All destiny needed ports are forwarded by upnp port mapping in my router (OpenWRT Router) Cable FritzBox does not need to forward individual ports since it forwards EVERYTHING to my OpenWRT box via the default route ive added Could any technican of bungie shed some more light on the internal network requirements of destiny so i can fix this issue once and for all? i have decent linux skills and enough time at hand to supply tcpdumps, wireshark traffic pcap files etc. And please dont tell me to clear my console cache, as you bet i tried that aswell... It works fine when i hook up my ps4 directly to the cable fritzbox, but that goes against my security precautions i implemented which are the case for the second router. There is defenetely something wrong with destiny's netcode that does not work well with dual routers between the PS4 and the Internet. Please also note, i dont have dual NAT just because i run two routers. The fritzbox routes everything for the 192.168.1.0/24 subnet to my openwrt due to a custom default route i set in the fritz software that targets the second router. A quick wireshark dump reveals that my ps4 is communicating just fine with the demonware servers on port 3074 up until a certain point where it starts talking to itself: 195 18.355765 192.168.1.230 192.168.1.230 UDP 45 1035 → 3074 Len=3 this does not seem right to me. Please message me when you want the full dump @bungie as i dont want to get in trouble by posting the network trace in a publically accessable place like this forum. Please help me as my life is without purposes right now, my shiny destiny limited ps4 is collecting dust, as are the destiny vanilla collectors edition and the taken king collectors edition aswell. I gave you a shitload of my hard earned money, please help me to be able to enjoy this game again!

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
You are not allowed to view this content.
;
preload icon
preload icon
preload icon