[bittorrent] 8-bytes transaction id

Stas Khirman staskh at comcast.net
Wed Apr 4 23:08:22 EDT 2007

Quite often , I see some of the DHT nodes are responding with 8-bytes
transaction ID despite the fact that queries have only 2-bytes ID.
Apparently,  all responses in question a pretty similar format : two first
bytes are correct transaction ID, then 4 bytes of 0x000018FF and then two
more bytes (often similar between different peers). For example:

It seems to be a behavior of some "not-so-standard" implementation - does
anyone know what client have such behavior? What is a meaning of the last 6
bytes? Version?


More information about the BitTorrent mailing list