Slashdot Mirror


EFF Releases Software to Spot Net NonNeutrality

DanielBoz writes in with word of the EFF's new initiative to help consumers detect if their ISP is spoofing packets. From the press release: "In the wake of the detection and reporting of Comcast Corporation's controversial interference with Internet traffic, the Electronic Frontier Foundation has published a comprehensive account of Comcast's packet-forging activities and has released software and documentation instructing Internet users on how to test for packet forgery or other forms of interference by their own ISPs."

3 of 73 comments (clear)

  1. Not tesing is not science by l2718 · · Score: 4, Insightful

    First of all, the EFF may has not tested your ISP. You may trust them that in general ISPs are sending spoofed packets, but still want to know whether your ISP is using the tactic. Beyond that, however, just because you trust them doesn't mean independent verification has no value. Results mean something different if you obtained them yourself. Also, as in regular science, independent confirmation of results gives more than that: more people conducting tests will also give better data.

  2. Stop misusing "Network Neutrality" by bconway · · Score: 5, Insightful

    Network Neutrality refers to ISPs double dipping on charging/extorting fees for both users paying for their connections and web sites paying for prioritization of traffic according to origination and destination. It does not refer to protocol-based QoS. It does not mean a flat, unmanaged, unQoS-ed Internet. By repeatedly and deliberately misusing this phrase, its importance is being weakened.

    --
    Interested in open source engine management for your Subaru?
    1. Re:Stop misusing "Network Neutrality" by porpnorber · · Score: 3, Insightful

      I think how consumers are supposed to select their QoS strategy is with QoS labels. The question is not 'should we have QoS' (I don't know about you, but I would rather have my videoconference packets queued ahead of my ftp packets), it's should the ISP be overriding our choices to satisfy their own policies. This is the same issue as randomly dropped connections: a mechanism to drop connections should exist because the endpoints need it. The carrier should not be invoking it 'on your behalf' and in the face of your desires, or it simply isn't doing what it was paid to do.

      There's a secondary issue of whether your operating system provides a good mechanism for QoS policy management at the endpoints (hint: no, it doesn't). But that's something to take up with the O/S vendor, or perhaps—an easier nut to crack—the router in your home. But in any case, it seems reasonably clear that QoS should be honoured or ignored end-to-end, and not randomly messed with in transit to the benefit of third parties.

      ...Unless I've misunderstood the technical situation completely....