JavaScript is required to use Bungie.net

Help

Help us help you.
Edited by Gyrferret: 9/14/2014 11:07:35 PM
57

I think I found the Reason for All the Error Codes

I think I've determined the reason for all these error codes: Destiny's netcode is *very* unforgiving of host disconnections. I have been toying around with my networking all day, and have realized that my ISP is dropping all my packets for about 5 seconds every now and again. When this happens, all my network traffic outbound is shut down, but internal network connectivity is just fine. I understand the reason is not on Bungie's end for the disconnections, however the issue lies in the fact that I believe Destiny's netcode is dropping you if you cannot reach its servers within a couple of seconds (maybe 2-3). This is kinda a small window, as many games I play allow for time outs of up to 20 seconds. If my hypothesis is correct, Bungie just needs to allow the disconnection timer to be a bit longer to prevent a lot of the connection drops that I have been experiencing. The connection drops I've monitored can be seen as all my ICMP traffic to MS server (134.170.179.80) will drop for about 7 ICMP counts, then resume as normal. I have not been able to complete a strike mission because of all these drops, and I feel that the multiplayer netcode is being a lot more forgiving than the single-player netcode right now. Hopefully this helps some of you find out what's going on. I'm glad to see that Bungie updated the verbiage for their "Bee" error code. Suffice to say, the problem still exists, but at least now they are formally acknowledging the reason for the error. I sincerely hope that they are able to address the timeout drops and increase the length with which your console drops your connection due to an inability to connect to their servers. While I understand that it may be a technological impossibility to reduce the timer, I do hope that that is not the case and this can be resolved in a future update. -------------EDIT 9/14/2014------------- This one is a doozy and a bit unrelated to the content I posted before but it chronicles my ordeals in finding out how I determined it was an ISP issue, how I fixed it, and how I hope it will fix everything going forward (for me): So I noticed after just having an endless ICMP session with an IP I control outside of my network that my connection was dropping every 10 minutes on the dot. I would have a CentOS VM just constantly pinging that server and would check it whenever I noticed my entire internet connection dropping. The way that pinging tends to work is that it sends a packet out every second or so, which it how I calculated my packet drop time (5-6 seconds). Someone in this post (another forum) suggested to try a static IP, but they were thinking of a static IP for the console, not necessarily for my entire internet connection. I have the DHCP lease for my devices at a sufficient length that it should not be an issue for any one device to lose connection for any (noticeable) period of time. However, it got me thinking, what if I set a static IP as the IP that my ISP assigns to me. Typically, IPs are given to you via DHCP *unless* your ISP assigns you a static IP, or if you opt in for one. While digging through my router configuration gathering up my current IP and gateway (which was a .33 fortunately which TREMENDOUSLY helped in figuring out the netmask) I noticed something odd. My ISP's DHCP lease time was 20 minutes. That is short; incredible short. And also helpful to know. Due to the way that DHCP works, devices will send a packet to their DHCP server around the halfway mark (50%) of their lease time to determine the next Configuration to use. The halfway mark of 20 minutes is.... 10 minutes..... That's when I put 2 and 2 together and realized that maybe my ISP is having DHCP a issues when it comes to my particular network. So I set a static IP for my public IP (I would not recommend doing this unless you are allocated one by your ISP) and, lo and behold, no more drops every ten minutes. I called my ISP this morning (very small ISP and the owner is basically a network engineer that picked up the phone). He confirmed the DHCP issue and said it was due to network upgrades they are performing. He chided me a bit when I told him I set a static IP, and said he would set a DHCP reservation for my IP to see if that helps. I'm not 100% sure it will, as I believe my router still has to send out a DHCP request at the halfway mark to verify which IP/Configuration to use, but here's to hoping. Anyway, that's how I fixed my issue with my ISP. To anyone who wants to determine where they might be experiencing issues, you can try running a "tracert 134.170.179.80" within a command prompt, and looking to see if some packets are being dropped wholesale or partially at a particular router. If they are being dropped at a router outside of you ISPs network, find out what it is and contact your ISP about it. I'm sure with some digging I can find the IP that the XBOX One is connecting to for Destiny's Servers, but I would rather not post that if I found it.
English
#Help

Posting in language:

 

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

  • We are aware there are some players that are not having a quality experience getting or staying connected to Destiny, even after following the troubleshooting steps. We will be updating the CATTLE/CATERPILLAR, CENTIPEDE, BEE/FLY/LION and BEAVER/FLATWORM/LEOPARD help articles with updates as we investigate. Here are some links for those that want more info (scroll to the bottom of each article for updates): http://www.bungie.net/7_Error-Code-CENTIPEDE/en/Help/Article/11875 http://www.bungie.net/7_Error-Code-CATERPILLAR--CATTLE/en/Help/Article/11873 http://www.bungie.net/7_Error-Code-BEE--FLY--LION/en/Help/Article/11791 http://www.bungie.net/7_Error-Code-BEAVER--FLATWORM--LEOPARD/en/Help/Article/11790

    Posting in language:

     

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

    14 Replies
    • It can't be fixed . If they add more tolerance for packet loss or latency(lagg) then people will exploit it This is a very old issue with pvp games. If you can lagg just right. Drop incoming packets just right you will dominate pvp That's why I retired . Us older players who pioneered pvp became experts at MIPS and throttling internet connections Send hit packet ffff

      Posting in language:

       

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

    • Idk if this is relavent to this page but i was upgrading my lucky rasberry to its final stage and my chest piece reset its self and now i lost a exotic shard :( someone plzz help i domt want to start over 😒😭😭😫

      Posting in language:

       

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

    • Bungie listen to him!

      Posting in language:

       

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

    • I didn't read all of this and frankly don't care, what it is is Bungie's servers for Destiny and that's it.

      Posting in language:

       

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

    • Bungee just doesn't care about its players that's it they don't want to help fix anything as long as your paying they -blam!- you every chance they get and if our don't like -blam!- off there or thousands of people willing to accept their terms up until they get fed up enough and realize what's going on as far as I'm concerned from this point bungees just a parasite that should be eradicated

      Posting in language:

       

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

    • Now to get bungie to even pay attention to posts like this all would be well. Terrible developing team for such a fun game

      Posting in language:

       

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

      1 Reply
      • That's not entirely true because it all depends on where you live, and the location of their servers in relation to the players gaming in your area. I can't do missions at all in the daytime, have to wait until most people are sleep. Then still get plenty of caterpillar error codes, along with bee, beaver, weasel. The codes come from them not being to handle the gamer play load percentage. Like most xbox user's this is the only game with these problems, never get this while playing Call of Duty, Gears of War, or any other multi player game. Port forwarding don't work, neither does changing Ip, address, changing from mortem to router, or anything else they suggest. It's those idiots and they have very poor customer service!!!!!!!!!!!!!!!

        Posting in language:

         

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

      • I'M NOT EVEN GETTING D/C'D OR ERROR CODES. THE CRUCIBLE IS NOTHING SHORT OF A CLUSTER FUGGED LAGZILLAFEST... SOMETHING HAS TO BE DONE BECAUSE IT'S IMPOSSIBLE TO PLAY AT THIS POINT.

        Posting in language:

         

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

      • I believe everything started with the new update, cause I have Destiny since the beginning and never have a problem until today. I hope they fix this problem.

        Posting in language:

         

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

        1 Reply
        • Open the TCP/UDP ports as per the instructions in the following link, this will fix the issues for 90% of people (it has for everyone I know) http://www.bungie.net/en/Help/Article/11930

          Posting in language:

           

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

          2 Replies
          • Bump. Everyone needs to read this.

            Posting in language:

             

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

          • Had very few issues now cattle on login attempt can't play at all, all my friends are playing just fine, I hope this is fixed ASAP . Very frustrating

            Posting in language:

             

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

          • Edited by Flutternips: 9/21/2014 4:14:26 AM
            I've been able to play destiny fine up until yesterday with only a minute amount of disconnects. Now I'm getting constant bee DC's that range between every 5-30 minutes. This seems to happen more often when I'm farming on earth. Here is a traceroute to the IP you provided. ----- Tracing route to 134.170.179.80 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.0.1 2 * * * Request timed out. 3 25 ms 25 ms 26 ms rd1ht-tge1-2-28.ok.shawcable.net [64.59.170.33] 4 25 ms 24 ms 25 ms rd2ht-tge2-1.ok.shawcable.net [66.163.72.162] 5 30 ms 31 ms 31 ms 66.163.66.210 6 32 ms 31 ms 33 ms 66.163.67.233 7 37 ms 39 ms 40 ms 66.163.70.146 8 37 ms 38 ms 40 ms rc6wt-tge0-1-1-0.wa.shawcable.net [66.163.76.150] 9 38 ms 37 ms 36 ms rx0wt-microsoft.wa.shawcable.net [66.163.68.10] 10 42 ms 38 ms 42 ms ae13-0.co1-96c-1b.ntwk.msn.net [207.46.44.3] 11 49 ms 46 ms 40 ms 134.170.176.167 12 * * 40 ms 134.170.176.167 13 * * * Request timed out. 14 43 ms * 43 ms 134.170.179.80 Trace complete. ----- As we can see, the timeouts occur at the very end of our little packets' adventure. This is definitely outside of my ISP's influence...

            Posting in language:

             

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

          • Can't even get logged into game.. Home network.. Even opened all ports, turned off firewall, hard wired... Nothing.. Still get centipede when logging into game. Frustrating as hell.

            Posting in language:

             

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

          • This is seems to be really good information for people that know what you are talking about. I don't. I'm useless when it come to tech. This is why I bought a console and not a PC. It is also why Bungie needs to set up a real customer support. It looks like you spent quit a bit of time with this post to help others. Thanks for that.

            Posting in language:

             

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

          • Its funny that this post has given me more information as to what may be going on than anything Bungie has released... Thanks, mate.

            Posting in language:

             

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

            5 Replies
            • Edited by TJ Bow: 9/14/2014 5:31:59 PM
              I hope Bungie can sort this soon I wanna play with friends on missions & strikes. It spoils the game so much which is a shame because the game is awesome.

              Posting in language:

               

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

              2 Replies
              • Everything that I just read was way above my IQ. :-D

                Posting in language:

                 

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

                1 Reply
                • Hi, from another thread I started. Hi, so I too was receiving the BEE error, however, setup logging on my TP-Link Router, which is running OpenWRT/Gargoyle and captured the following error at the time I was booted from the game. [quote]Sep 14 20:50:19 Gargoyle daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disconnected due to excessive missing ACKs[/quote] The fix, which appears to be working for me, was to disable ANI (Adaptive Noise Immunity) by performing the following. [quote]root@Gargoyle:~# cat /sys/kernel/debug/ieee80211/phy0/ath9k/ani ANI: ENABLED ANI RESET: 7 SPUR UP: 6315 SPUR DOWN: 6315 OFDM WS-DET ON: 0 OFDM WS-DET OFF: 0 MRC-CCK ON: 0 MRC-CCK OFF: 0 FIR-STEP UP: 6317 FIR-STEP DOWN: 6321 INV LISTENTIME: 0 OFDM ERRORS: 13966856 CCK ERRORS: 181888 root@Gargoyle:~# echo 0 >/sys/kernel/debug/ieee80211/phy0/ath9k/ani root@Gargoyle:~# cat /sys/kernel/debug/ieee80211/phy0/ath9k/ani ANI: DISABLED[/quote] And add [quote]option disassoc_low_ack 0[/quote] to the /etc/config/wireless file. I suspect other router configurations would be dropping the PS4 connection due to excessive missed ACK's as bungies servers get overloaded. Hopefully helps others to investigate. I've had 3 games in a row now without being kicked. Not definitive whether it's fixed, but certainly lines up with missing packets.

                  Posting in language:

                   

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

                  1 Reply
                  • That is an good one Gyrferret But what about the following? This weekend I was able to play 1.5 hours constantly, in the morning without interruptions, but around 12 ~ 13 o'clock. I get disconnected, and then the errors reappear every 5 to 10 minutes. During the week after work in the evening, I'm not able to play normally without interruptions. So with other words, I only get disconnected when (probably) a lot of users are also playing Destiny. If I think this through, I would conclude that the servers or the internet lines to the servers of Destiny are over their capacity and then people with the highest latency are dropped from the server, because the server cannot react in time. [i](Or the people without XBox gold / PS+ subscription are dropped first, to give the paying users higher priority, but I don't know if only non-paying users have this issue).[/i]

                    Posting in language:

                     

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

                    9 Replies
                    • I also find this absolutely stupid that bungie changed their code from the beta. Because I had absolutely zero issues in the beta or alpha. They really need to explain themselves.

                      Posting in language:

                       

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

                    • Edited by z Smittyy: 9/15/2014 1:46:21 AM
                      After reading this. It sounds like this is not a bungie related problem but an individual ISP problem. Terrific. So now what? All the big name ISP's like At&t comcast and maybe verizon all have to be notified of this or is bungie gonna do this for the customers? Either way, sounds like this wont be fixed for a couple of months

                      Posting in language:

                       

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

                      3 Replies
                      • Bumping this. I actually had a feeling that this was exactly the reason why Destiny was the [i]only[/i] game that disconnects me so often and without warning. Every other game I've played, whether on Xbox or on PC, has always been far more forgiving about packet loss. The game shouldn't just let your connection go on a whim like this. Bungie, please increase the resync window for us with less than stable connections to your servers. Honestly, I'm able to play the game just fine when it's not dropping me every five minutes. PvP plays fairly well, and PvE isn't much of a problem either when it's working. Either that or your servers need improvement. I'm pretty sure it's not on our end.

                        Posting in language:

                         

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

                      • Just downloaded the patch that was supposed to fix Centipede hoping the other errors would get fixed at well. Alas, still getting bee stings...

                        Posting in language:

                         

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

                      • Yes, the problem is that the game is unforgiving with data loss. I was one of the ones who suffered disconnects all week (mind you I play many other games online with no disconnect issues). I had ComCast tech rewire my entire house all the way to the cable box! Guess what? Problem solved! Haven't had a single disconnect in Destiny. There can, of course, be many reasons for data loss that Destiny should be more forgiving about, but my situation proves that Destiny has no grace period when failing to send/received data.

                        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