With "Reduced Exit Policy" that allows connections only on some ports, so dynamic ports are the reason why it works https://trac.torproject.org/projects/tor/wiki/doc/ReducedExitPolicy Cathal Garvey:

Hey all, I'm aware that (for pretty good reasons) bittorrent is "blocked" by most exits on Tor. However, I'm unsure how this blockage is implemented, and it just emerged as a relevant item in my thought-process: the Bittorrent "Mainline" DHT is not necessarily useful to Bittorrent alone, but is frequently used as an experimental platform for other P2P applications.

Is the bittorrent DHT blocked by Tor exits, or just the Bittorrent file-transfer protocol? If the latter, how is that block enacted when most bittorrent apps support protocol obfuscation and dynamic ports?

-- https://nesterov.pw GPG key: 0CE8 65F1 9043 2B11 25A5 74A7 1187 6869 67AA 56E4 https://keybase.io/komachi/key.asc

The DHT uses UDP(not TCP) as its transport, which Tor does not support. Some references: DHT spec: http://bittorrent.org/beps/bep_0005.html Tor and other transports: https://www.torproject.org/docs/faq#TransportIPnotTCP On 2015-01-13 20:46, Cathal Garvey wrote:

Hey all, I'm aware that (for pretty good reasons) bittorrent is "blocked" by most exits on Tor. However, I'm unsure how this blockage is implemented, and it just emerged as a relevant item in my thought-process: the Bittorrent "Mainline" DHT is not necessarily useful to Bittorrent alone, but is frequently used as an experimental platform for other P2P applications.

Is the bittorrent DHT blocked by Tor exits, or just the Bittorrent file-transfer protocol? If the latter, how is that block enacted when most bittorrent apps support protocol obfuscation and dynamic ports?