Slashdot Mirror
Google Caught in Comcast Traffic Filtering?
marcan writes "Comcast users are reporting 'connection reset' errors while loading Google. The problem seems to have been coming and going over the past few days, and often disappears only to return a few minutes later. Apparently the problem only affects some of Google's IPs and services. Analysis of the PCAP packet dumps reveals several injected fake RSTs, which are very similar to the ones seen coming from the Great Firewall of China [PDF]. Did Google somehow get caught up in one of Comcast's blacklists, or are the heuristics flagging Google as a file-sharer due to the heavy traffic?"
So I take it any comment that doesn't boil down to "Comcast sucks!" will be met by you with contempt and little else. Could it be that the fact that not all Comcast customers seem to be effected could be important to this story? I think you are the one adding "noise" here.
I don't give a damn for a man that can only spell a word one way.
Mark Twain
How do you report spamming? It's odd that I've never seen it before on slashdot.
At least he wasn't scared to be an Anonymous Coward. I don't see how your grammar corrections add anything to the discussion at hand. The fact remains if Comcast is doing some kind of traffic control and google is caught in it why are not all customers effected/affected? The answer might be that not everyone is on the same routing switch and that the traffic is handled different for each section. I know in Canada with Shaw the people in Vancouver are treated differently then the people in Edmonton because they have different hardware running their connection.
Maybe he likes to use mispellings of words on purpose, as some kind of homage to his sig.
which is totally what she said
You know, everyone gripes about the mod system, but it works pretty well. However, this is getting off topic, so I'll just add that my service with Comcast still blows less than my service with SBC did.
I like my beverages with warning labels!