3 ms·
Even 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
by david_shaw 11y ago
Even 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.