Magnet to BitTorrent, where does the file.torrent?

Are the holder of a simple retracker in a small local network. There is a desire to transform a dull info_hash list to something more informative. But I can't find information(Google is hard) about how the system works receiving structure of the torrent file when we only have the name of the tracker and info_hash. I understand there is a way and getting this structure of the sources themselves, but did not find the description of this process in the Protocol description =\

Please those who knows where to find the info himself or was faced with this question, don't scrimp on the answer :)

PS. as I am not a programmer in C/C++, tweaking in the source torrent clients, much success has not brought.
October 8th 19 at 03:50
1 answer
October 8th 19 at 03:52

>Without going into to much detail, the hash of the magnet link is used to find peers using DHT.

All that is found. It turns out, info_hash just simply looked up in the DHT, not on the tracker. Even though it is logical — in magnet uri's not the address of the tracker. In fact, there is only the info_hash of the torrent.
No, is another question. DHT helps us to seek the source, it is 100% return and announced retracker. The question of how knowing the IP:PORT of the source and the info_hash to the structure of the torrent. - miguel commented on October 8th 19 at 03:55
Oh, so you want to become a member and DHT to give torrents on your tracker Magnet URI chtol? Or what? The idea is what? - Brandi_Ritchie59 commented on October 8th 19 at 03:58
Generally that's a speck of this whole business seems to be: - Brandi_Ritchie59 commented on October 8th 19 at 04:01
All these specs read, and this more than once. But I do not understand how to work with it, stupidly don't even know where there is a request for a specific info_hash, and in what format the answer will come.

I basically need to know the file tree and secure it by info_hash. - miguel commented on October 8th 19 at 04:04

In accordance with this message, info_hash transmitted to the handshake stage. So relatively speaking the second party already knows, and sends packets according to it.
And is transmitted in this format (packet data):
And then appendixa binary itself metadata of the torrent. In particular the info section. Like is only transmitted it.

1. Do handshake (as when downloading a simple torrent)
2. Transfer request (d8:msg_typei0e5:piecei0ee)
3. Received data (packet data) or failure (reject the packet: d8:msg_typei1e5:piecei0ee) - Brandi_Ritchie59 commented on October 8th 19 at 04:07

Find more questions by tags MagnetBitTorrent