Is it activity-specific? What are you doing when the socket closes?

Is it activity-specific? What are you doing when the socket closes?

Dont worry about it,

ISD will be around in a minute to lock your thread and continue to bury the issue. They will tell you to submit a petition and then CCP will tell you their logs show nothing.

Is it activity-specific? What are you doing when the socket closes?

The problem with this is I've done the petition thing, as have many others and it still gets ignored.

If, somewhere between you and CCP's servers in London, there's a breakdown in routing, you'll get a socket closed. (and all the logs would show, on CCPs side, is that you stopped sending them anything.)

GǪbut that is not what's happening because then it would happen equally across all my computers and OSes and all at the same time. It doesn't.

Hell, I've had TQ and Sisi clients running side-by-side and suddenly gotten a closed socket to TQ with nothing else being affected. The fact that it started appearing immediately after one particular patch and the way that it affects only specific installs and not the entire GÇ£parkGÇ¥ rather speaks to it being EVE than something else.

There has previously been reported issues with different flavours of traffic shaping software used by many providers.

The idea behind such software is to allow providers to get better performance from any given bandwidth by identifying different types of traffic created by their customers and altering the prio or transmission sequnce of the different kinds of traffic.

In the best of worlds such software provides quick response for time critical interactive applications while delaying and/or slowing down bulk transfers. (And in some more evil cases more or less kill certain traffic, like torrents).

The problem (for the customers) is that there's no perfect way to identify all kinds of different traffic which leads to loads of packets getting mangled, delayed or dropped for no obvious reason.

The only thing CCP or any other application provider can do is to try to find out which software (and version) that is used by the providers that cause those issues amd contact the creators and ask them to adjust their (broken) rules.

But since it's often the customers' providers that are running this type of software (and in some cases even a 3:rd party selling access in bulk to smaller/local provders) it's very hard to find out from the server end of things.

It gets worse since many providers doesn't even admit to their own users that they are running any form of shaping software, much less informing anyone of it's brand or version.

What we can do, more than trying to get our local provider to give us the information we want, is the write petition to CCP with as much connection related information as possible (provider information and traceroutes) to give CCP's network dudes a chance to figure out what's going on and who they can contact to sort out the issues.

The reason it often pops up after a patch is that their might be minor changes/upgrades/fixes to Eve's client-server protocol which can cause some of the shaping software to misidentify the stream.

The reason it often pops up after a patch is that their might be minor changes/upgrades/fixes to Eve's client-server protocol which can cause some of the shaping software to misidentify the stream.

Sure, but again, that would rather suggest that it should affect all clients in the same park equally, when in reality it's only specific installs that get hit, with no discernible commonality between them that is also a difference to the unaffected installs.

The reason it often pops up after a patch is that their might be minor changes/upgrades/fixes to Eve's client-server protocol which can cause some of the shaping software to misidentify the stream.

Is there a specific DEV who deals with the issues and workarounds forum?

It's been weeks and no one will communicate with us on what is being done to fix the Socket Closed issues many are having.

And no, it's not Steam.

It's not on our end. I've been playing for two years and nothing until inferno patch.

No, it's not country specific.

I work for an ISP, specifically the bit that handles traffic management hardware and we've never seen Eve misclassified following a patch. Those patches don't change the traffic signature at all really.

Where they changed something in EvE's header format and some or at least one shaping software decided to classify it as bulk.

Eve is quite resilent to network issues (delays, packet loss, drops and so on) which makes tracking the actual problem even harder.

Probably don't know...can't tell what is going on when you are away from your keyboard...amirite?