3 ms·
How was this measured? From my perspective, from knowing and chatting with semi-professional sharers daily, most bitorrrent traffic is encrypted. Torrent clie
by sandworm101 11y ago
How was this measured? From my perspective, from knowing and chatting with semi-professional sharers daily, most bitorrrent traffic is encrypted. Torrent clients can all encrypt and are generally set to use only encrypted connections. And serious sharers have switched to VPNs en mass. So how was all this bittorrent traffic identified?
Fyi, there are some tricks for overcoming bittorent encryption. I've used them to identify what was is shared across private networks (schools) but the techniques involve some trickery that is probably illegal on the public internet.
- nitrogen 11y agoMy guess: metadata. Any outgoing packets to IPs that don't reverse resolve to a non-ISP with high source and destination ports could be BT. Add a flow-based heuristic and measure packet entropy and maybe you can be quite accurate.
- exelius 11y agoThat's basically how you do it. Torrent packets have a certain "signature" (you can usually even determine the client from this, even if all traffic is encrypted). That, and torrent traffic is pretty leaky... even if you are encrypting, not all of your peers are.
- david_shaw 11y agoEven if the traffic is encrypted, it's still identifiable as BitTorrent. As another example, I can also see and measure HTTPS traffic, even though I'm unable to read the data itself. Assuming the traffic's being analyzed at a backbone level, it shouldn't matter that it's over VPNs, either -- it's still going to be BitTorrent traffic from some address, even if the "actual" source is unknown.
- sandworm101 11y agoNot really. Https traffic is easily identifiable via port numbers. Bittorrent does have its preferences but isn't tied to a particular port. Encryption was specifically designed to prevent torrent traffic from being identified as such by ISPs, to prevent throttling efforts. So any successful identification of bittorrent traffic by at the ISP level is an issue to be addressed. My usual client (transmission) actually picks a random port every time it starts. That does seem the norm for serious filesharers, which I also assume are responsible for a large percentage of torrent traffic.