AT&T Denies Resetting P2P Connections 112
betaville points out comments AT&T filed with the FCC in which they denied throttling traffic by resetting P2P file-sharing connections. Earlier this week, a study published by the Vuze team found AT&T to have the 25th highest (13th highest if extra Comcast networks are excluded) median reset rate among the sampled networks. In the past, AT&T has defended Comcast's throttling practices, and said it wants to monitor its network traffic for IP violations.
"AT&T vice president of Internet and network systems research Charles Kalmanek, in a letter addressed to Vuze CEO Gilles BianRosa, said that peer-to-peer resets can arise from numerous local network events, including outages, attacks, reconfigurations or overall trends in Internet usage. 'AT&T does not use "false reset messages" to manage its network,' Kalmanek said in the letter. Kalmanek noted that Vuze's analysis said the test 'cannot conclude definitively that any particular network operator is engaging in artificial or false [reset] packet behavior.'"
Comment removed (Score:5, Informative)
Re:Confirmed? (Score:5, Informative)
For example,
37 users on Telecom Italia France using ASN 12876 experienced a median of 2.53% RST messages;
27 users on AT&T WorldNet Services using ASN 6478 experienced 13.97% RST messages;
24 users on AT&T WorldNet Services using ASN 7018 experienced 5.35% RST measages;
40 users on Comcast Cable using ASN 33668 experienced 23.72% RST messages.
One thing you have to remember is the forged RST packets is a man-in-the-middle-attack, the Vuze plugin connected on a AT&T connection doesn' know if the RST came from AT&T at ASN 6478 , AT&T at ASN 7018, Comcast or Telecom Italia France.
AT&T Lying like a Rug (Score:3, Informative)
Coincidence? I think not.
Steven
Chuck's right (Score:5, Informative)
Vuze's test only counted reset rates, so it can't prove anything about what's going on. At most, it could suggest areas where it might be productive to do more investigation.
Re:Confirmed? (Score:2, Informative)
Comcast has admitted to sending false resets, so, no surprise, they are on top of the list. In fact, they are not only on top of the list, they're nowhere else. This is to be expected with a systematic interference with traffic.
HOWEVER, if you look down the list, and I mean, WAYYY down the list, you'll find that ranked at #101 (out of 108)... is AT&T! If AT&T has been systematically producing false resets, they wouldn't just have one network high on the list, but all of them.. (see: Comcast).
No one ever got a good rep defending AT&T, but stories like this just make
Re:We'll They've Reset Mine (Score:3, Informative)
Re:no reset for me (Score:5, Informative)
Unless you run a business class router and have configured it to log incoming RST packets, you haven't seen any resets in your router log because they are not logged.
The typical Linksys/Netgear/D-Link/whatever NAT "router" found in most homes most certainly won't log incoming RST packets.
Regards,
--
*Art
Re:Someone, please write a decent test (Score:3, Informative)
Like Comcast they can forge packets on BOTH sides of the router if they were doing it and therefore you'd get RST packets on both sides. Therefore merely comparing the output on both sides is not enough to determine if forging RST packets is occurring.
You need to log, at each end, what each end is both sending and receiving. Then compare the results. Unless you installed a stateful firewall or a proxy server, there shouldn't be anything in the middle changing the packets. If there is, it's useful to know that.