JavaScript is required to use Bungie.net

Forums

originally posted in: BUNGIE FIX YOUR SAME LAN PROBLEMS
Edited by RAIST5150: 10/8/2016 5:18:59 AM
15
Have you tried disabling the NAT Acceleration option they posted about a few days ago? Was added to the sticky in the help section. 10/4 I think, and was in the News post on 10/6. The option may be labeled differently like Hardware Acceleration. Should be nested in the LAN sections, possibly with switching control options like Jumbo Frames. Your router's documentation about the setting should caution that enabling it may negatively impact routing functions like port forwarding or QoS features.
English

Posting in language:

 

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

  • Not all routers have hardware acceleration. But lets say all do. Why was everyone's working fine before bungie released that patch? They need to start working on the real issue with this game instead of focusing on what new animal error codes to add to the game.

    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 RAIST5150: 10/10/2016 2:14:06 PM
    Could have been changes at the infrastructure level. Who knows. Could have installed new network hardware and the firmwares are knackering things up. Could have been just firmware updates, or OS updates, security updates/upgrades. May not have been something they actively changed themselves. We have seen similar things happen in the past. Windows updates that knocked network printers offline, or nixed certain media types from playing across the web. The big Belkin firmware update system that botched internet access for home users for nearly a week or so before they took it down and patched it up. Anti DDoS measures that made things unstable for people whose PathMTU wasn't properly detecting the change (about a year or so back...people had to manually set MTU to stay connected to PSN). Such things may be rare...but they do happen. And there are fixes that can be applied at the user end to protect against them. For some it may be as simple as toggling a feature to a different setting. Others it may just mean a firmware update or a switch to an open source firmware. The more dramatic change may require new hardware...like buying their own router and getting their ISP to change the bridge mode of their combo router/modem, or upgrade to a more robust router in general.

    Posting in language:

     

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

  • I can understand that but when they say the issue was caused by the beaver error fix then whats so hard about rolling that back.

    Posting in language:

     

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

  • That was in regards to one vector. So far we've seen three potential issues in play. Their own internal change, CTF and/or FA knackering packet delivery (NAT/Hardware Acceleration), and UPnP management protocols used by the routers (IGD vs SSDP). Two of those can be addressed from the user end...either directly by the user or assisted by their ISP.

    Posting in language:

     

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

  • And some people have done these and it works perfectly fine until bungie releases a patch for hotfix.

    Posting in language:

     

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

  • And some people haven't had to do anything at all. As stated before...they may not know exactly what changed. They may still be chasing symptoms. Until they know exactly what the root cause is, they can't formulate a plan to address it permanently. They've tried to get specific feedback from the players via a sticky...but the participation has been pretty low in contrast to the spamming of complaints over here. Perhaps they just haven't gotten the clues needed to point them to the true root of the problem just yet.

    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 YFZ451: 10/10/2016 2:35:48 PM
    Then for the love of god roll back the patch that they said started the issue. I mean its just like your computer. If you install something that causes your computer to blue screen you don't sit they and wait for it to correct itself or try to find a fix. You remove the culprit or restore your computer back then look for a possible fix.

    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 RAIST5150: 10/10/2016 2:54:33 PM
    And that is the point...it may not be that simple. It may not even be their game code at fault but something somewhere else in their environment. When Windows update knackers something up it may not be the entire list of patches that caused the issue. It may be one specific DLL that doesn't play right with specific environments. They have to step through it all one by one to find the culprit before they can find a fix. And even then that fix may not need to be applied globally but only the people that have the specific conflict. Could be a certain soundcard line of drivers, or network card, or just the 900 series of nVidia graphics cards that have an issue. The fix may actually be something that has to be kicked back to the respective vendors of those devices or software to patch their software so they are compliant with the latest API changes...as in it may not be that DirectX needs to change, but the drivers managing the hardware/software needs to be patched. Until the true root of the problem is found and they can find a real fix, we will be in the cycle of work arounds. At the moment two of those workarounds appear to be tied directly to features in network hardware that may be changed from the user end.

    Posting in language:

     

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

  • The point is we wouldn't have to change things on our end if they wouldn't break shit. Was working perfectly fine until that update.

    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 RAIST5150: 10/10/2016 4:03:20 PM
    Not necessarily. If they had infrastructure changes at the same time, we would still have the issue. It isn't always as simple as rolling back a simple patch. What if they upgraded devices at the perimeter of their network to improve throughput and the change in hardware/firmware in play is to blame. Can't necessarily just undo that change... So we have to find a way to comply with the new communication protocols in play. A Windows example was used earlier. Let us look at a familiar PC gaming scenario. Say your favorite game went through a big version upgrade that results in a change in requirements and your hardware/software is no longer cutting it. Would you suffer the lower framerates and/or lower textures/resolution, or look for an upgrade of some sort to get back in spec? The same thing could be in play here. We may ultimately need to change our environments to gain full functionality as the game service continues to evolve.

    Posting in language:

     

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

  • Continues to evolve? If anything this game is going backwards. Been the worst its ever been.

    Posting in language:

     

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

  • I have a net gear router, I looked for a Nat acceleration option but could not find one. R u families with net gear?

    Posting in language:

     

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

  • Haven't used their products in a long time. May be called Hardware Acceleration or something else. Likely nested in the LAN section where other switch control options are listed lime Jumbo Frames. The setting is a flag for whether things like Cut-Through Forwarding (CTF) and Flow Acceleration may be used depending on other settings. Might see those terms mentioned in your documentation along with a caution about using them. On my Asus the Auto setting is supposed to disable CTF if you run something like QoS because (as stated in the documentation) it can cause issues with things like port forwarding and QoS. Can toggle it off completely to be sure.

    Posting in language:

     

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

  • Thanks

    Posting in language:

     

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

  • Haven't used their products in a long time. May be called Hardware Acceleration or something else. Likely nested in the LAN section where other switch control options are listed lime Jumbo Frames. The setting is a flag for whether things like Cut-Through Forwarding (CTF) and Flow Acceleration may be used depending on other settings. Might see those terms mentioned in your documentation along with a caution about using them. On my Asus the Auto setting is supposed to disable CTF if you run something like QoS because (as stated in the documentation) it can cause issues with things like port forwarding and QoS. Can toggle it off completely to be sure.

    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