San Francisco Weekly finds that Comcast continues to throttle upstream p2p traffic using forged TCP packets. Of course that shouldn't be too surprising, given that Comcast's practices probably don't infringe upon the FCC's intentionally wimpy guidelines covering network neutrality versus "reasonable" network management. Most probably, the only thing Comcast can get in trouble for is for not being honest about the practice with consumers. At most, that means an easily-swallowed fine and some additional fine print in your contract.

Like the AP and our users before them, SFWeekly uses Wireshark to sample the traffic as it makes its way across the Comcast network from San Fran to Melbourne. They also talk briefly with BitTorrent creator (and Comcast customer) Bram Cohen. Cohen says he's creating a "more bandwidth-conscious" version of the now closed-source BitTorrent client this year, and shares his thoughts on the practice:The process used to test for packet forgery, for those interested in testing it with your own ISP, was outlined recently in a tutorial (you'll want a modicum of networking knowledge) created by the EFF. Using it, we discovered that Cox was using a similar technique to thwart eDonkey transfers. The major difference between Cox (now a private company) and Comcast is that Cox is being forthcoming about the practice.